The following global resource bundle is used by human workflow service APIs to look up resource strings:

oracle.bpel.services.workflow.resource.WorkflowLabels.properties

You can customize this bundle to provide alternatives for existing display strings or to add additional strings (for example, for mapped attribute labels, standard views, or custom dynamic assignment functions).

The global resource bundle provides resource strings for the following:

• Task attributes:

  Labels for the various task attributes displayed in Oracle BPM Worklist (or other clients). Resource string values are returned from the following TaskMetadataService methods:

  • getTaskAttributes

  • getTaskAttributesForTaskDefinition

  • getTaskAttributesForTaskDefinitions

• Mapped attribute labels:

  Mapped attribute labels created through the runtime config service. These strings are used in Oracle BPM Worklist when displaying mapped attributes. Resource string values are returned from the TaskMetadataService methods:

  • getTaskAttributesForTaskDefinition

  • getTaskAttributesForTaskDefinitions

  If translated resource strings are required for mapped attribute mappings, then customize the WorkflowLabels.properties bundle to include the appropriate strings.

• Task outcomes:

  Default resource strings for common task outcomes. These can be overridden by the task resource bundle, as described above. The resource strings are returned by the TaskMetadataService method getTaskDefinitionOutcomes, if no task-specific resource bundle has been specified. As shipped, the global resource bundle contains resource strings for the following outcomes:

  • Approve

  • Reject

  • Yes

  • No

  • OK

  • Defer

  • Accept

  • Acknowledge

• Dynamic assignment function names:

  Labels for dynamic assignment functions. These strings are returned from the runtime config service methods getUserDynamicAssignmentFunctions and getGroupDynamicAssignmentFunctions. The shipped resource bundle contains labels for the standard dynamic assignment functions (ROUND_ROBIN, LEAST_BUSY, and MOST_PRODUCTIVE). If additional custom dynamic assignment functions have been created, then modify the WorkflowLabels.properties resource bundle to provide resource strings for the new functions.

• Standard view names:

  Labels for standard views. If you want translated resource strings for any standard views you create, then add them here. Standard view resource strings are looked up from the resource bundle, and are returned as the standard view name from the UserMetadataService methods getStandardTaskViewList and getStandardTaskViewDetails. The key for the resource string should be the name given to the standard view when it is created. If no resource string is added for a particular standard view, then the name as entered is used instead.

• Notification messages:

  Resource strings used when the task service sends automatic notifications. These can be customized to suit user requirements.

• Task routing error comments:

  When an error is encountered in the routing of a task, the task service automatically appends comments to the task to describe the error. The various strings used for the comments are defined in this resource bundle.

You can customize the WorkflowLabels.properties resource bundle.

To customize the file:

1. Edit the properties file.

2. Add the customized class to the class-path used for workflow services. Ensure that customized file is located before the default class in the class-path.

3. Save the customized file to the following directory:

   directory_path/oracle/bpel/services/workflow/resource/WorkflowLabels.properties
   

4. Update the worklfowCustomClasspathURL configuration parameter to point to directory_path. As this is a URL, it is possible to host the resource bundles on a web server, or to store them in the MDS repository for the SOA server, and use the 'oramds' URL protocol, and make them accessible to multiple Oracle WebLogic Servers.