-
Feature Request
-
Resolution: Fixed
-
L3 - Default
-
None
Use Case is along the lines of:
- I have an existing timer event for which the duedate is calculated using an expression
- Something changes in the context of the process (internally or externally) which should lead to a re-calculation of the duedate.
Currently this is not easily possible. I can either
- calculate the new duedate externally and then update the timer via the management service. Disadvantage: the condition is not re-evaluated, instead I need to re-calculate the condition externally
- use process instance modification to cancel the timer and re-enter it. This leads to a re-evaluation of the expression but it has many drawbacks like messing up history, concurrency inside the process instance etc ...
Goal of this issue is to come up with a solution allowing to address the use case in a better way.
This is the controller panel for Smart Panels app
[CAM-9236] For an existing Timer, I can trigger re-calculation of the duedate
| Link | New: This issue is related to SUPPORT-4599 [ SUPPORT-4599 ] |
| Link | New: This issue is depended on by SUPPORT-4701 [ SUPPORT-4701 ] |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 12157 ] |
| Remote Link | New: This issue links to "Page (camunda confluence)" [ 12172 ] |
| Link | New: This issue is related to SUPPORT-5002 [ SUPPORT-5002 ] |
| Fix Version/s | New: 7.11.0 [ 15343 ] |
| Status | Original: Open [ 1 ] | New: In Progress [ 3 ] |
| Assignee | New: Tobias Metzke-Bernstein [ tobias.metzke ] |
| Description |
Original:
Use Case is along the lines of:
- I have an existing timer event for which the dudate is calculated using an expression - Something changes in the context of the process (internally or externally) which should lead to a re-calculation of the duedate. Currently this is not easily possible. I can either - calculate the new duedate externally and then update the timer via the management service. Disadvantage: the condition is not re-evaluated, instead I need to re-calculate the condidion externally - use process instance modification to cancel the timer and re-enter it. This leads to a re-evaluation of the expression but it has many drawbacks like messing up history, concurrency inside the process instance etc ... Goal of this issue is to come up with a solution allowing to address the usecase in a better way. |
New:
Use Case is along the lines of:
- I have an existing timer event for which the duedate is calculated using an expression - Something changes in the context of the process (internally or externally) which should lead to a re-calculation of the duedate. Currently this is not easily possible. I can either - calculate the new duedate externally and then update the timer via the management service. Disadvantage: the condition is not re-evaluated, instead I need to re-calculate the condidion externally - use process instance modification to cancel the timer and re-enter it. This leads to a re-evaluation of the expression but it has many drawbacks like messing up history, concurrency inside the process instance etc ... Goal of this issue is to come up with a solution allowing to address the usecase in a better way. |
| Description |
Original:
Use Case is along the lines of:
- I have an existing timer event for which the duedate is calculated using an expression - Something changes in the context of the process (internally or externally) which should lead to a re-calculation of the duedate. Currently this is not easily possible. I can either - calculate the new duedate externally and then update the timer via the management service. Disadvantage: the condition is not re-evaluated, instead I need to re-calculate the condidion externally - use process instance modification to cancel the timer and re-enter it. This leads to a re-evaluation of the expression but it has many drawbacks like messing up history, concurrency inside the process instance etc ... Goal of this issue is to come up with a solution allowing to address the usecase in a better way. |
New:
Use Case is along the lines of:
- I have an existing timer event for which the duedate is calculated using an expression - Something changes in the context of the process (internally or externally) which should lead to a re-calculation of the duedate. Currently this is not easily possible. I can either - calculate the new duedate externally and then update the timer via the management service. Disadvantage: the condition is not re-evaluated, instead I need to re-calculate the condition externally - use process instance modification to cancel the timer and re-enter it. This leads to a re-evaluation of the expression but it has many drawbacks like messing up history, concurrency inside the process instance etc ... Goal of this issue is to come up with a solution allowing to address the use case in a better way. |