Chapter 8 Building an Executable BPM: Managing Data and Choreography

Correlation Keys (Executable BPM)

A correlation key references an ordered list of variables defined under the model, the package or a composite process. This list is used for process instance identification. The correlation key object can then be associated with a process implemented by an operation.

For example, if a client is approved for a loan he may send a request to actually obtain that loan. Correlation key is used to make sure that the second request goes to the correct process instance.

In BPEL languages, the correlation key is used to define CorrelationSet elements.

In Sybase Integration Orchestrator, the correlation key is used to define Key elements.

You can have two correlation keys for the activity that sends messages implemented by an input-output operation:

One correlation key associated with the input message received by the operation
One correlation key associated with the output message sent by the operation

For more information about input-output operations, see section Type property of the Implementation tab.

The Dependencies tab of the correlation key property sheet displays the list of the processes that use the correlation key for reception and the list of the processes that use the correlation key for emission.

When you move a correlation key between models, a copy of the correlation key stays in the source model, if the correlation key or one of its variables is used by processes in that model, as external shortcut are not allowed.

When you copy a correlation key the list of variables associated with it is also duplicated.

Correlations have no symbol in the diagram, but have the following graphical representation in the Browser:

External shortcuts for a correlation key are not supported.