The Mapping activity allows you to add or manipulate data in a workflow. It evaluates the source expression and saves the result in the target expression of the associated data items. You can use it as a way to combine data from parallel-processed approval forms after their data is moved to flowdata.
For example, in a parallel approval context you might need to collect data from more than one approval form that is dependent on each other or needs to be calculated with each other. To accomplish this, place a Mapping activity after a Merge activity and before any activities that consume the results (for example, Condition, Entity, Provisioning or another Approval activity).
You can also use the Mapping activity to isolate calls to external Java routines that might manipulate data and be resource intensive, thereby not slowing down user-based Approval activities in either their pre-activity or post-activity mapping phase.
The Mapping activity includes the following properties:
Table 10-16 Mapping Activity Properties
|
Property Name |
Description |
|---|---|
|
Identifier |
A unique string value that identifies the activity. Workflow Builder generates this value automatically in the <Activity>_<N> format, where <Activity> represents the name of the activity and <N> represents an alphanumeric value that contains seven characters. |
|
Name |
Provides a name for the activity. |
To bind the data items associated with the Mapping activity, define pre-activity and post-activity mappings. The pre-activity mappings initialize data in flowdata with constants, values retrieved from the flowdata object, system process variables, system activity variables, or data retrieved through expression calls to the directory abstraction layer. The post-activity mappings move data into the flowdata object.
Table 10-17 Mapping Activity Data Item Mappings
|
Setting |
Description |
|---|---|
|
Source Expression |
Specifies a source expression. When you click a cell in the Source Expression column, the ECMA expression builder displays to help you define your expression. For example, function list() { s=new java.lang.String(); if (wi.XPath('count(flow-data/groups)' ) > 0) s="There was a group selected"; return s;}; list(); |
|
Target Expression |
Specifies a target expression. When you click a cell in the Target Expression column, the ECMA expression builder displays to help you define your expressions or you can click the Map All button. An example of a target expression is: flowdata.testexpression |
Email templates are not supported with this activity.
The Problems tab provides details of the errors and warnings associated with the activity in a workflow. For more information about validating workflow activities, see Validating a Workflow.