* New for 9.5 *
For event catches, receives, and
start points, you can select data from an event and store it in
process variables for use for a later step in the process. A process data map specifies
the data that is stored when an event is acted on. You can store
event data and event message data.
Note: For event start points, any data being mapped
from an event to a process variable requires that the variable is
configured as an input variable. (See
Process input and output data.)
Process data maps consist of expressions in the following form:
expression1 operator expression2
expression1 is an XPath expression that
evaluates to a value in the process data tree.
operation is always the equal sign (=).
expression2 is an XPath expression that
evaluates to a value in the event’s source data set or a value in
the process data tree.
In the following example process data map, the expression stores
a credit score from an application form in the creditscore variable.
/process_data/@creditscore = /data/applicants/Applicant/creditscore
A process data map can have multiple expressions. Each expression
can map a different piece of data as required. If you do not specify
any process data map expressions, no data is saved for later use
in the process.
In addition to event data, you can send addition event message
data for an event receive. The data that you receive is not typically
altered during process execution because it is a document of record.
The data can also be used by the process to validate the XML document
structure.