Writer timer triggered event with process instance key #9519
Assignees
Labels
kind/feature
Categorizes an issue or PR as a feature, i.e. new behavior
scope/broker
Marks an issue or PR to appear in the broker section of the changelog
version:8.1.0-alpha3
Marks an issue as being completely or in parts released in 8.1.0-alpha3
version:8.1.0
Marks an issue as being completely or in parts released in 8.1.0
Comments
saig0
added
kind/feature
This was referenced Jun 8, 2022
A timer of a timer start event links to the created process instance
camunda-community-hub/zeeqs#246
Closed
|
Hi， @saig0 may be the elementInstanceKey shoub be include too? |
|
@skayliu interesting question. But no, the element instance key would not fit in my mind. The timer creates a new process instance but the rest (e.g. activation of the start event) happens later. So what should be the element instance key? The timer is not bound to an element instance. |
|
@saig0 Thank you ,I get it . |
zeebe-bors-camunda bot
added a commit
that referenced
this issue
Jun 9, 2022
9520: Writer timer triggered event with process instance key r=remcowesterhoud a=saig0 ## Description * minimal change in the timer processor to write the timer `triggered` event with the key of the created process instance ## Related issues closes #9519 Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors-camunda bot
added a commit
that referenced
this issue
Jun 9, 2022
9520: Writer timer triggered event with process instance key r=remcowesterhoud a=saig0 ## Description * minimal change in the timer processor to write the timer `triggered` event with the key of the created process instance ## Related issues closes #9519 Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
zeebe-bors-camunda bot
added a commit
that referenced
this issue
Jun 10, 2022
9520: Writer timer triggered event with process instance key r=saig0 a=saig0 ## Description * minimal change in the timer processor to write the timer `triggered` event with the key of the created process instance ## Related issues closes #9519 Co-authored-by: Philipp Ossler <philipp.ossler@gmail.com>
oleschoenburg
added
the
version:8.1.0-alpha3
Zelldon
added
the
version:8.1.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
I deployed a process with a timer start event. If the timer is triggered then a new process instance is created and an event of type
timerwith intenttriggeredis written.As a monitoring application, I want to track which process instance was created by this timer. But currently, the
timer: triggeredevent doesn't contain the key of the created process instance.Describe the solution you'd like
The
timer: triggeredevent contains the key of the created process instance.Describe alternatives you've considered
Add a reference of the timer to the created process instance. But this option seems not practical because a process instance can be created by different triggers, for example, a message.
Additional context
In a monitoring application, I want to track that a process instance was created by a triggered timer start event.
The text was updated successfully, but these errors were encountered: