Variables (BPM)

A variable is a data container, which holds temporary values that can be passed between processes as input and output parameters, and which are important for their correct execution. For example, variables are useful to determine routing decisions or to build the messages a process has to send.

Variables can be created in models targeting the SOA, BPMN, and BPEL languages.

Variables can be used in conjunction with:

Processes – to build the process messages (see Processes (BPM)).
Correlation keys – to identify a process instance using a set of variables (see Correlation Keys (BPM)).
Data transformations – to copy data from one variable to another (see Data Transformations (BPM)).

By default, a variable name or code must be unique within the parent scope (package, composite process, or model) but can be used by any process (activity) defined at the same level. However, two variables can share the same name when they belong to different composite processes contained in the same package.

Note: If you move a variable that is used in its original package to another package in the same model, a shortcut is created in the original package. If you move the variable to another model, a copy of the variable is retained in the original model as external shortcuts are not allowed for variables.

Creating a Variable
You can create a variable from the Browser or Model menu.
Variable Properties
To view or edit a variable's properties, double-click its Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.

Parent topic: Service Oriented Architecture BPM (SOA)