Bug:
When two processes are deployed which are related through a call activity and both contain an event subprocess which both start through a message start event, then only one event subscription is created inside the database. The result is that only one process (parent) can receive a message.
This is true for all event subscriptions (eg signal, message etc)
Expected behaviour:
An event subscription is generated for each event.
This is the controller panel for Smart Panels app
[CAM-1968] Event subscriptions are missing in subprocess
Description |
Original:
Bug: When two processes are deployed which are related through a call activity and both contain an event subprocess which both start through a message start event, then only one event subscription is created inside the database. The result is that only one process (parent) can receive a message. Expected behaviour: For each message start event an event subscription is generated. |
New:
Bug: When two processes are deployed which are related through a call activity and both contain an event subprocess which both start through a message start event, then only one event subscription is created inside the database. The result is that only one process (parent) can receive a message. This is true for all event subscriptions (eg signal, message etc) Expected behaviour: For each message start event an event subscription is generated. |
Summary | Original: Message event subscriptions are missing | New: Event subscriptions are missing in subprocess |
Description |
Original:
Bug: When two processes are deployed which are related through a call activity and both contain an event subprocess which both start through a message start event, then only one event subscription is created inside the database. The result is that only one process (parent) can receive a message. This is true for all event subscriptions (eg signal, message etc) Expected behaviour: For each message start event an event subscription is generated. |
New:
Bug: When two processes are deployed which are related through a call activity and both contain an event subprocess which both start through a message start event, then only one event subscription is created inside the database. The result is that only one process (parent) can receive a message. This is true for all event subscriptions (eg signal, message etc) Expected behaviour: An event subscription is generated for each event. |
Link | New: This issue is related to SUPPORT-925 [ SUPPORT-925 ] |
Fix Version/s | New: 7.1.0 [ 12891 ] |
Assignee | Original: Robert Gimbel [ gimbel ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Remaining Estimate | New: 0 minutes [ 0 ] | |
Original Estimate | New: 0 minutes [ 0 ] |
Assignee | New: Roman Smirnov [ smirnov ] |
Rank | New: Ranked higher |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Workflow | Original: camunda BPM [ 26303 ] | New: Backup_camunda BPM [ 58443 ] |