Innovation Management

Innovation Management helps you capture ideas from any source for new products, services, markets, or customer experiences. Each proposal is evaluated for value, cost, and constraints.

Innovation Management documents, prioritizes, and agrees on requirements that can be leveraged in developing innovation concepts. Reuse existing items, trace requirements through design, and validate that each has been met to reduce new product introduction risks.

Use Application Composer to extend ideas, concepts, proposals, and requirements. Use Application Composer to develop attributes for each requested idea.

You can use Application Composer to extend Innovation Management objects in the following ways:

• Add standard and configured attributes to the pages.

• Leverage logical expressions to control the visibility of the configured page layouts.

• Use Groovy scripting to validate either a field or an object, automatically execute an action when a specific event is triggered and write object functions that can be reused in multiple contexts.

• Further, use Groovy scripting to update attributes between standard and configured objects; between two configured objects; and between two standard objects.

• Use Groovy scripting to validate through either a field or an object rule, and automatically execute an action when a specific event is triggered. These Server Scripts can be defined for both standard and configured objects.

• Provide separate Create, View, and Manage access with granular privileges.

What You Can Configure for Innovation Management Objects

Here are the configurations that are applicable for Innovation Management objects.

• Additional Attribute Types, which include:
  • Dynamic Choice List: A dynamic choice list is a field that contains a list of values, which are populated from the actual data of another object.
    Note: From a cross-application perspective, you can create a dynamic choice list field for an object in one web application that's populated by the records from a supported object in another web application.
  • Fixed Choice List: A fixed choice list is a field that contains a list of static values that are populated from the lookup types. At run time, you can select one or more values from this field, depending on the field's definition.

    You can create cascading lists of values that are narrowed down based on user selection. For example, you can create a list of countries, states, or counties, with each list displaying values based on the value selected in the parent field. If the state selected is Oregon, the list of counties displayed can be limited to the counties within that state.

• Check box: A check box field is a field where, in the runtime application you can select a check box, indicating a true or false attribute of a record. The available operators are Equal to, Greater than, Greater than or equal to, Is blank, Is not blank, Less than, Less than or equal to, and Not equal to.
• Text: A text field is a field where, in the runtime application, you can enter a combination of letters, numbers, or symbols.
• Number: A number field is a field where you can enter a number during runtime.
• Currency: A currency field is a field where you can enter a currency amount.
• Percentage: A percentage field is a field where you can enter a percentage. The Application Composer automatically adds the percent sign to the number.
• Datetime: A datetime field is a field where you can enter a date, or select a date from a calendar, and enter a time of day. You can show the date or time, or both.
• Date: A date field is a field where you can enter a date, or select a date from a calendar. This type of field has no time component.
• Long Text: A long text field is a field where, in the runtime application, you can enter a combination of letters, numbers, or symbols. This field type supports 32,000 characters. Long text isn’t supported by Audit History.
  Note: Don't use more than five long text fields in an object for performance reasons.
• Formula: A formula field is a field that's calculated in the runtime application using the Groovy-based expression included in the formula field's definition.
• Record Type: A record type field contains a list of static values that are populated from lookup types. Associating a choice list value with a role means that only users with that role can see the choice list value. Associating a choice list value with a page layout means that after that value is selected at runtime, the associated page layout is displayed.
• Page Layout: Modify the pages on which an object appears.
• Subtabs that include context links and relationships: Add subtabs to the standard or configured object's details page to display details that are related to the current object but derived from another object, or from another source. You can specify the source of subtab data.
• Buttons or Actions: Add buttons or links to desktop pages.
• Related Objects: Related objects are connected in a foreign key-based relationship between two objects.
• Custom Objects: Custom Objects are objects that are created using Application Composer. You can create either top-level objects (objects without a parent) or child objects (objects created in the context of a parent).
  Note: If you create a subtab using Application Composer, and expose the configured objects:

  • The Save As functionality won't save these objects.
  • The configured child objects aren't supported.