Add Mapped Attribute Dialog

Human Task Editor then choose DataMapped Attributes sectionAdd Mapped Attributes

Use to define 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.

To define attribute-label mappings:

In the Application Server field, do one of the following:
- From the dropdown list, select the application server that contains the protected-attribute labels.

Click Create a new connection....
Click Edit the connection... to modify the definition of a selected application server.

The Attribute dropdown list populates with the available attribute labels from the specified server.

From the dropdown list, select an attribute.

Note: The list does not include any labels for flexfield attributes to which this task component is being mapped.

At the Value field, do one of the following:
- Enter an XPath expression that determines the value to be stored in the attribute.
- Click the icon to create a value in the Expression Builder.
- Leave the field blank to allow the value to be determined at run time.
Usually, this XPath expression selects a value from the tasks's payload, but you can specify any valid expression that evaluates to a simple type, i.e., a string, date, or number.

Be aware that specifying an XPath expression is not mandatory. You may prefer to set the value of the underlying flexfield-attribute value yourself. For example, you can add a custom assign activity to the BPEL process that initiates the task, or manipulate the Task object through the workflow service APIs.

Optionally, enter a description.
Click OK.