Task Understanding Approval Management Concepts

Using Approval Management 26-11 For more information, see Section 26.3.6.4.3, How to Make List Modifications.

26.3 Designing Approval Management Tasks in Oracle JDeveloper

You design approval management tasks by defining a human task that provides the ability to model multi-stage approvals and determine the appropriate approvers based on approval policies for a business object and the associated HR hierarchy provider. This section describes the overall modeling process and the specifics of the process you use to model approval management tasks in JDeveloper.

26.3.1 Introduction to the Modeling Process

The modeling process for designing approval management tasks includes the following: ■ Creating a human task definition ■ Creating a task display form using the Human Task Editor Creating a human task definition includes the following tasks: ■ Specifying general information, such as task title and task-title globalization, outcomes, priority, owner, and category ■ Defining task parameters, including those with service data object SDO references ■ Specifying mapped attributes ■ Modeling task routing by specifying stages and list builders, and modeling any business rules that define the list builders ■ Defining escalation and renewal policies ■ Specifying notification settings ■ Modeling any advanced settings like callbacks, security access rules, and restricted assignment Some of these procedures are discussed in the sections that follow. For information about those that are not discussed, see Creating the Human Task Definition with the Human Task Editor in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite. You also must create a task display using an ADF task flow to display the details of the approval. ADF task flows are used to model the user interface for the task details page. For more information, see Designing Task Display Forms for Human Tasks in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

26.3.2 Before You Begin

Before designing approval management tasks, you must satisfy the following prerequisites: ■ You must have deployed SDO services. ■ You must have created a human task service component in which to design the approval task. 26-12 Modeling and Implementation Guide for Oracle Business Process Management

26.3.3 Specifying General Information

Some general information, including task title, outcomes, priority, owner, and category, is not specific to AMX. For more information about these, see How to Specify the Task Title, Priority, Outcome, and Owner in the section Creating the Human Task Definition with the Human Task Editor in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite.

26.3.3.1 Task-Title Globalization

The title attribute of the task object contains a user-friendly value that mainly is descriptive in nature. In AMX, the task title can be globalized so that it renders in the user’s preferred language. Title is defined in the .task file for design time and in the WorkflowTask.xsd file for run time. Currently, the definition of these elements in both of these files are simple xsd:string types. For globalization, the structure and usage of these elements change to accommodate a mechanism that provides translatable, formatted strings. The design-time metadata for these elements is enhanced to contain a value element and an optional set of parameters. Messages defined as an XPath expression or static have their information stored in the value element and require no parameters. Messages defined that rely on information in a resource bundle have a key stored in the value element with some parameters also defined. The Human Task Editor provides a mechanism in the Expression Builder to enable the user to specify the resource key and parameters and, at the same time, generate the appropriate design time XML in the taskDefinition. Figure 26–5 shows the globalization icon in the Human Task Editor. Figure 26–5 Title Globalization Icon The following procedure explains how to add translatable strings. It assumes that a resource bundle has been specified.

1. Click the icon to display the Edit Translatable Strings dialog.

2. Select a key from the dropdown list or click the plus sign + to create one. Figure 26–6 shows the Create a New Key dialog, which displays when the plus sign + on the Edit Translatable Strings dialog is clicked. Using Approval Management 26-13 Figure 26–6 Create a New Key Dialog

3. Enter a name, the translatable text, and click OK.

Figure 26–7 shows the Edit Translatable Strings dialog after a new key has been added. Figure 26–7 New Key Added

4. Use the Expression Builder to add values.

Figure 26–8 shows the completed Edit Translatable Strings dialog.