Configuration Scenarios

Let's look at some scenarios where you can tailor the application interface to achieve a specific requirement.

Scenario 1

Your business requires that the description field of all change orders must be automatically updated with the department and location entered by the user.

Solution:

1. In the Setup and Maintenance work area, navigate to:
   • Offering: Product Management
   • Functional Area: Change Orders
   • Task: Manage Change Order and New Item Request Header Descriptive Flexfields
2. Create global descriptive flexfields entitled Department and Location.
3. In Application Composer, create a script that copies the values of the Department and Location fields into the Description field.

Scenario 2

When users create a quality action, you want to make sure that the triage date is automatically set to 3 days after the creation date.

Solution: Within Application Composer, create a new date field called Triage Date. Define the default value of Triage Date using a Groovy script expression that captures the creation date and adds 3 days. Define an expression in a way that doesn't allow the field to be updated.

Scenario 3

Your business process requires that a requirements specification is created for every idea that has an Approved status. Also, the requirements specification must have the same name and description as the original idea.

Solution A: Within Application Composer, you can add a button to an idea that calls a web service. The web service will create a requirements specification and copy the name and description of the idea to the new requirements specification.

Solution B: Within Application Composer, you can create a trigger that calls a web service whenever an idea is set to Approved status, which will create a requirements specification and copy the name and description of the idea to the new requirements specification.

Scenario 4

On a quality issue, your users must select a service type and then a service center. The selection of the service center is dependent upon the selection of the service type.

Solution A: Within Application Composer, create two fixed choice list fields with appropriate values for service type and service center. Designate the service type field as the parent of the service center field and map the values as wanted so that when a user selects a service type, only the applicable service centers are available for selection.

Solution B: Within Application Composer, create two fixed choice list fields with appropriate values for service type and service center. Use Groovy scripting to create a trigger that will automatically select the service center based on the selection of service type.

Note: Refer to the Triggers section in Create Automation with Scripting.