Add correlation information into the process tab.

copied from Gary's comment.
------------
Currently when listing the process instances, it only displays the process id, which gives no indication of the business context of the process instance.

From the activity events, it should be possible to extract correlation key name/value pairs, which should help. An example of the events generated when receiving a correlated message are:

09:53:20,395 INFO [STDOUT] RiftSaw BPEL event:
ActivityExecStartEvent:
Type = activityLifecycle
ActivityId = 3
ActivityName = start
ActivityType = OPickReceive
ActivityDeclarationId = 24
ScopeId = 13
ScopeDeclarationId = 17
ScopeName = __PROCESS_SCOPE:HelloGoodbye
ParentScopesNames = [__PROCESS_SCOPE:HelloGoodbye]
ProcessInstanceId = 4
ProcessId =

{http://www.jboss.org/bpel/examples}

HelloGoodbye-1
ProcessName =

{http://www.jboss.org/bpel/examples}

HelloGoodbye
Timestamp = Wed Jan 26 09:53:20 GMT 2011
LineNo = 56
Class = class org.apache.ode.bpel.evt.ActivityExecStartEvent
09:53:20,408 INFO [STDOUT] RiftSaw BPEL event:
ProcessInstanceStateChangeEvent:
OldState = 0
NewState = 10
Type = instanceLifecycle
ProcessInstanceId = 4
ProcessId =

{http://www.jboss.org/bpel/examples}

HelloGoodbye-1
ProcessName =

{http://www.jboss.org/bpel/examples}

HelloGoodbye
Timestamp = Wed Jan 26 09:53:20 GMT 2011
LineNo = -1
Class = class org.apache.ode.bpel.evt.ProcessInstanceStateChangeEvent
09:53:20,422 INFO [STDOUT] RiftSaw BPEL event:
ProcessInstanceStateChangeEvent:
OldState = 10
NewState = 20
Type = instanceLifecycle
ProcessInstanceId = 4
ProcessId =

{http://www.jboss.org/bpel/examples}

HelloGoodbye-1
ProcessName =

{http://www.jboss.org/bpel/examples}

HelloGoodbye
Timestamp = Wed Jan 26 09:53:20 GMT 2011
LineNo = -1
Class = class org.apache.ode.bpel.evt.ProcessInstanceStateChangeEvent
09:53:20,471 INFO [STDOUT] RiftSaw BPEL event:
VariableModificationEvent:
NewValue = [message: null]
Type = dataHandling
VarName = myHelloVar
ScopeId = 13
ScopeDeclarationId = 17
ScopeName = __PROCESS_SCOPE:HelloGoodbye
ParentScopesNames = [__PROCESS_SCOPE:HelloGoodbye]
ProcessInstanceId = 4
ProcessId =

{http://www.jboss.org/bpel/examples}

HelloGoodbye-1
ProcessName =

{http://www.jboss.org/bpel/examples}

HelloGoodbye
Timestamp = Wed Jan 26 09:53:20 GMT 2011
LineNo = 56
Class = class org.apache.ode.bpel.evt.VariableModificationEvent
09:53:20,480 INFO [STDOUT] RiftSaw BPEL event:
CorrelationSetWriteEvent:
Key =

{CorrelationKey setId=Session, values=[1]}

Type = dataHandling
CorrelationSetName = Session
ScopeId = 13
ScopeDeclarationId = 0
ProcessInstanceId = 4
ProcessId =

{http://www.jboss.org/bpel/examples}

HelloGoodbye-1
ProcessName =

{http://www.jboss.org/bpel/examples}

HelloGoodbye
Timestamp = Wed Jan 26 09:53:20 GMT 2011
LineNo = -1
Class = class org.apache.ode.bpel.evt.CorrelationSetWriteEvent

The 'Key' property could be used to display "Session=[1]" along side the process number. 'Session' is not necessarily meaningful, but in a real business process the correlation ids would be more meaningful, e.g. OrderId.