The runtime config service provides methods for managing metadata used in the task service runtime environment. It principally supports the management of task payload mapped attribute mappings and the URIs used for displaying task details.

The task object used by the task service contains many mapped attributes, which can be populated with information from the task payload. This allows the task payload information to be queried, displayed in task listings, and used in human workflow rules.

The runtime config service provides methods for querying and updating the URI used for displaying the task details of instances of a particular task definition in a client application. For any given task definition, multiple display URIs can be supported, with different URIs being used for different applications. The method getTaskDisplayInfo can query the URIs for a particular task definition. The method setTaskDisplayInfo can define new URIs or update existing ones. Only users with the workflow.admin privilege can call setTaskDisplayInfo, but any authenticated user can call getTaskDisplayInfo.

The runtime config service allows administrators to create mappings between simple task payload attributes and these mapped attributes.

Only a user with the workflow.mapping.publicFlexField or workflow.mapping.protectedFlexField privilege can make updates to payload mappings for public mapped attributes. Only a user with the workflow.mapping.protectedFlexField privilege can make updates to payload mappings for protected mapped attributes. Any authenticated user can use the query methods in this service.

An administrator can create attribute labels for the various mapped attributes. These attribute labels provide a meaningful label for the attribute (for example, a label Location may be created for the mapped attribute TextAttribute1). A given mapped attribute may have multiple labels associated with it. This attribute label is what is displayed to users when displaying lists of attributes for a specific task in Oracle BPM Worklist. The attribute labels for a specific task type can be determined by calling the getTaskAttributesForTaskDefinition method on the task metadata service.

When defining attribute labels, the following fields are automatically populated by the service. You do not need to specify values for these attributes when creating or updating attribute labels:

• Id

• CreatedDate

• WorkflowType

• Active

Valid values for the task attribute field for public mapped attributes are as follows:

• TextAttribute1 through TextAttribute20

• FormAttribute1 through FormAttribute10

• UrlAttribute1 through UrlAttribute10

• DateAttribute1 through DateAttribute10

• NumberAttribute1 through NumberAttribute10

Mappings can then be created between task payload fields and the attribute labels. For example, the payload field customerLocation can be mapped to the attribute label Location. Different task types can share the same attribute label. This allows payload attributes from different task types that have the same semantic meaning to be mapped to the same attribute label.

The runtime config service also provides the following:

• Methods for querying the dynamic assignment functions supported by the server

• Methods for maintaining the task display URLs used for displaying the task details in Oracle BPM Worklist and other applications

• Methods for getting the server HTTP and JNDI URLs

Table 34-9 describes some of the common operations of the runtime config service. Package oracle.bpel.services.workflow.runtimeconfig corresponds to the runtime config service.

For more information about runtime config service, see Workflow Services Java API Reference for Oracle SOA Suite.

For more information, see the following:

• Dynamic Assignment and Task Escalation Patterns

• Using Oracle BPM Worklist for details about mapped attribute mappings

• Workflow Services Java API Reference for Oracle SOA Suite