Approver Substitution List Modification

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. 26-18 Modeling and Implementation Guide for Oracle Business Process Management

26.3.5.1 About Attribute Labels and Attribute-Label Mappings

Attribute labels are user-defined properties that allow a meaningful string to be applied to a particular flexfield attribute. The label should reflect the data to store in the attribute. For example, “CustomerName” for “ProtectedTextAttribute1,” “OrderNumber” for “ProtectedNumberAttribute2,” or “OrderDate” for “ProtectedDateAttribute1.” A flexfield attribute can have multiple attribute labels defined for it. For example, the attribute “ProtectedTextAttribute1” could have the labels “CusomerName,” “PartId” and “EmployeeDepartment”. Attribute-label mappings for protected attributes are defined at design time in the Human Task Editor. They define a mapping between a particular task component and an attribute label, and also specify how the value of the attribute should be populated. The same attribute label can be re-used in multiple mappings. This allows task components to map data having the same semantic meaning into a common attribute identified by a common label. For example, PurchaseOrder, LoanRequest and ServiceRequest tasks all could define mappings to the “CustomerName” label. By sharing the same attribute labels across multiple task components, it is possible to construct worklist queries that query multiple task types and display or filter values from the common attribute labels. For example, it would be possible to construct a query that selected PurchaseOrder, LoanRequest, and ServiceRequest tasks, and then displayed the “CustomerName” as a column in the worklist task listing. For more information, see Section 26.5.2, How to Create Mapped Attribute Labels.

26.3.5.2 How to Define Attribute-Label Mappings

You define attribute-label mappings in the Mapped Attributes section of the Human Task Editor, as shown in Figure 26–12 . Figure 26–12 Mapped Attributes Section Table 26–1 Protected Flexfield Attributes Name Description ProtectedTextAttribute1 - ProtectedTextAttribute20 Stores text data, up to 2000 characters. The content in these fields is checked during keyword searches in the Worklist Application and through the task-query service. ProtectedFormAttribute1 - ProtectedFormAttribute10 Stores text data, up to 2000 characters. The content in these fields is not checked during keyword searches in the Worklist Application. ProtectedURLAttribute1 - ProtectedURLAttribute10 Stores text data, up to 200 characters. The content in these fields is not checked during keyword searches in the Worklist Application. ProtectedDateAttribute1 - ProtectedDateAttribute10 Stores date information. ProtectedNumberAttribute1 - ProtectedNumberAttribute10 Stores number information.