Details
-
Feature Request
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Done
-
None
-
None
Description
Currently, a processInstanceId variable is required to be passed back-and-forth with the DroolsBPMExchangeHandler so that we know which process instance should be interacted with (signaling and aborting, for example). It would be useful for a developer to be able to specify their own correlation id (perhaps a pre-existing application-specific one) instead of having to use the process instance id that we key off of internally.
Attachments
Issue Links
- is blocked by
-
JBPM-3512 Allow developer-defined correlationId in addition to processInstanceId
-
- Resolved
-
-
SWITCHYARD-421 Generalized mechanism for context property handling
-
- Closed
-
- relates to
-
SWITCHYARD-1579 BPM Component correlationKey issues
-
- Closed
-