L3 - Default User Story (Required on creation):
Similar to message correlation, users want to know and work with the process instances that are triggered by delivering a BPMN signal. Example: knowing if a signal was received by any process instance (e.g. to work around the problem that signal events can only be triggered when the receiving instance is waiting in the event).
Functional Requirements (Required before implementation):
- The Java and REST API provide the process instance (in case a start event is triggered) or execution (in case an intermediate event or event subprocess is triggered) a signal was delivered to (similar to message correlation with MessageCorrelationBuilder#correlateAllWithResult)
Technical Requirements (Required before implementation):
Limitations of Scope (Optional):
- We can decide if we also want to build the variant that returns variables. This is currently not in the scope of the ticket.
Hints (Optional):
This is the controller panel for Smart Panels app
[CAM-13427] I get a result when I trigger a BPMN signal
| Labels | New: potential_for_7.16 |
| Attachment | New: image-2021-04-23-14-34-37-321.png [ 42043 ] | |
| Description |
Original:
h4. User Story (Required on creation):
Similar to message correlation, users want to know and work with the process instances that are triggered by delivering a BPMN signal. Example: knowing if a signal was received by any process instance (e.g. to work around the problem that signal events can only be triggered when the receiving instance is waiting in the event). h4. Functional Requirements (Required before implementation): * The Java and REST API provide the process instance and/or execution a signal was delivered to (similar to message correlation) h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): * We can decide if we also want to build the variant that returns variables. This is currently not in the scope of the ticket. h4. Hints (Optional): |
New:
h4. User Story (Required on creation):
Similar to message correlation, users want to know and work with the process instances that are triggered by delivering a BPMN signal. Example: knowing if a signal was received by any process instance (e.g. to work around the problem that signal events can only be triggered when the receiving instance is waiting in the event). h4. Functional Requirements (Required before implementation): * The Java and REST API provide the process instance and/or execution a signal was delivered to (similar to message correlation with {{MessageCorrelationBuilder#correlateAllWithResult}}) h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): * We can decide if we also want to build the variant that returns variables. This is currently not in the scope of the ticket. h4. Hints (Optional): |
| Mentioned Roles |
| Mentioned Groups |
| Link | New: This issue is depended on by SUPPORT-10081 [ SUPPORT-10081 ] |
| Description |
Original:
h4. User Story (Required on creation):
Similar to message correlation, users want to know and work with the process instances that are triggered by delivering a BPMN signal. Example: knowing if a signal was received by any process instance (e.g. to work around the problem that signal events can only be triggered when the receiving instance is waiting in the event). h4. Functional Requirements (Required before implementation): * The Java and REST API provide the process instance and/or execution a signal was delivered to (similar to message correlation with {{MessageCorrelationBuilder#correlateAllWithResult}}) h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): * We can decide if we also want to build the variant that returns variables. This is currently not in the scope of the ticket. h4. Hints (Optional): |
New:
h4. User Story (Required on creation):
Similar to message correlation, users want to know and work with the process instances that are triggered by delivering a BPMN signal. Example: knowing if a signal was received by any process instance (e.g. to work around the problem that signal events can only be triggered when the receiving instance is waiting in the event). h4. Functional Requirements (Required before implementation): * The Java and REST API provide the process instance (in case a start event is triggered) or execution (in case an intermediate event or event subprocess is triggered) a signal was delivered to (similar to message correlation with {{MessageCorrelationBuilder#correlateAllWithResult}}) h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): * We can decide if we also want to build the variant that returns variables. This is currently not in the scope of the ticket. h4. Hints (Optional): |
| Mentioned Roles |
| Mentioned Groups |
| Labels | Original: potential_for_7.16 | New: potential_for_7.16 potential_for_7.17 |
| Labels | Original: potential_for_7.16 potential_for_7.17 | New: engine potential_for_7.16 potential_for_7.17 |