L3 - Default As a user, I want to recalculate the priority of an existing task using a REST call, so that the highest priority tasks will be executed first at all times.
Problem
Today, when the variables used to prioritize tasks have been updated by a backend service, users cannot trigger the engine to recalculate the priority of a task with a simple REST call - without duplicating the existing behavior of priority evaluation. **
Scenario:
Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}.
Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}.
Acceptance criteria:
As a User, when I update the variables of an existing task, I can recalculate the priority of a task using a REST call.
This is the controller panel for Smart Panels app
[CAM-11807] As a user, I want to recalculate the priority of an existing task using an API call
This ticket was migrated to github: https://github.com/camunda/camunda-bpm-platform/issues/2350. Please use this link for any future references and continue any discussion there.
Hi!
I think this feature will be of great importance to us.
But thinking more deeply, I see that it would be even better if we could configure the recalculation to be automatic like what happens in a spreadsheet, for example.
This is the description of the evolution:
Description
As a user, I want to configure (to me, I think this could be the default, but I put this "configuration" step otherwise it could break the other clients) my activities priorities to be always up to date with the variables.
Problem
Today, when the variables used to prioritize tasks have been updated, I need to know which tasks would be affected by this change and actively hit the engine to recalculate those priorities.
Scenario:
Process X is calculating the priority of a task directly with a variable i.e. ${taskXPriority}.
Process Y is evaluating the priority of a task with an expression like ${someValue + bonus}.
Acceptance criteria:
As a User, when I update a variable, all activities priorities that depends on this variable and are configured to stay up to date should be updated automatically.
I know this is a great increase in scope of this feature but I think we can see it as an evolution of the original request that can be prioritized separately. I just put my ideas here because this possible evolution description could help you to develop the original request in a way that we can use later to possible evolve to the idea described above.
Thanks!