Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify the target execution of a message correlation payload #2288

Open
ThorbenLindhauer opened this issue Apr 15, 2019 · 0 comments
Open
Labels
scope:documentation Changes to the product documentation. type:task Issues that are a change to the project that is neither a feature nor a bug fix.

Comments

@ThorbenLindhauer
Copy link
Member

ThorbenLindhauer commented Apr 15, 2019

This issue was imported from JIRA:

Field Value
JIRA Link CAM-10166
Reporter @tmetzke
Has restricted visibility comments true

What is the problem?
In the message correlation documentation we state at the end of the paragraph that {quote}In case of successful correlation, the correlated or newly created process instance is updated with the variables from the processVariables map.{quote}

In case of event subprocesses with message a start event and messages that are supposed to be correlated to and hand over their payload to the event subprocess scope, it is not clear enough that the recipient of those variables will rather be the parent execution than the event subprocess scope.

This occurred in SUPPORT-5580 as well as in the forum already.

What would be the expected behavior:
Have a clarifying notice or paragraph on event subprocesses in the message correlation documentation.

Hints (optional):
The event subprocess' message start event is treated as an intermediate message catch event of the parent process instance and not as a message start event, therefore no new process instance will be created for the event subprocess.

Links:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
scope:documentation Changes to the product documentation. type:task Issues that are a change to the project that is neither a feature nor a bug fix.
Projects
None yet
Development

No branches or pull requests

1 participant