List Creation Business Rules for Approval

26-16 Modeling and Implementation Guide for Oracle Business Process Management Figure 26–10 Add Task Parameter: Define Collection

5. Set the collection for the stage.

6. Click OK.

The following procedure enables you to accept static XML.

1. Provide the XSD where the schema is defined.

2. Define the task payload parameter as static XML.

3. Define the collection, its XPATH expression, and its keys.

4. Set the collection for the stage.

5. Click OK.

26.3.4.3 How to Define Collections

Collections are references to specific parts of a task message attribute, both static-XML based and entity attributes. After defined, collections can then be associated with stages to identify a stage as acting on a collection. Defining a collection involves defining the name of the collection and the XPath to the collection element. If the collection is defined for an entity attribute, the keys for the collection element have to be specified as well. Each key has to be a direct child of the collection element. Figure 26–11 shows how collections are defined. Using Approval Management 26-17 Figure 26–11 Defining Collections When you define a collection, JDeveloper automatically determines if it should be repeating element or not. This information is used when collections are associated with a stage. A non-repeating collection can be associated with a singular stage. A repeating collection, when associated with a stage, repeats the stage in parallel for each element in the collection at run time. For information about how the collection information is used in a stage, see Section 26.3.6.1, How to Model and Configure Stages.

26.3.5 Specifying Mapped Attributes

Human workflow provides task-message attributes that you can use for storing use-case-specific data, such as data extracted from a tasks payload. These attributes are also known as flexfield attributes or mapped flexfield attributes. Mapped flexfield attributes allow payload values to be displayed as columns in the task listing, rather than being hidden in the task details. These values are stored in the human workflow database schema, and you can use them in queries, view definitions, and assignment rule definitions. There are two types of message attributes: ■ public - Attributes mapped to specific task components at run time. These mappings can be changed at any time, and must be re-created when a task component is redeployed. For more information see the following sections in Oracle Fusion Middleware Developers Guide for Oracle SOA Suite: – How to Map Flex Fields in the chapter Using Oracle BPM Worklist – Introduction to Flex Fields in the chapter Introduction to Human Workflow ■ protected - AMX-specific mappings between a task component and protected flexfield attributes defined at design time. They cannot be changed at run time, and are deployed along with the task component. Table 26–1 summarizes the 60 available protected flexfield attributes.