-
Notifications
You must be signed in to change notification settings - Fork 565
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
8822: Business rule task can define decisionId as expression r=korthout a=korthout ## Description <!-- Please explain the changes you made here. --> A business rule task with a called decision needs to specify a decisionId for the decision that is called. It should be possible to refer to a decision based on the evaluation result of an expression. So, it should be possible to define the decisionId as an expression. See #8779. This adds support to define the `decisionId` of a `zeebe:calledDecision` as an expression (i.e. prefixed with `=`; e.g. `= variableContainingDecisionId`), while maintaining the ability to define it as a static value (i.e. not prefixed by `=`; e.g. `an_actual_decision_id`). For example, if the `decisionId` is an expression `= variableContainingDecisionId`, then the value of the `variableContainingDecisionId` variable should be used as the id of the decision that is called. The `decisionId` expression is evaluated during the activation of the business rule task, just after input mapping and just before the decision is evaluated. This means you can use the result of input mappings in the `decisionId` expression. If the evaluation fails, an incident of type `EXTRACT_VALUE_ERROR` is raised, similar to other expression evaluation failures. Resolving the incident will re-apply input mappings, re-evaluate the `decisionId` expression and then call the decision. ## Related issues <!-- Which issues are closed by this PR or are related --> closes #8779 Co-authored-by: Nico Korthout <nico.korthout@camunda.com>
- Loading branch information
Showing
8 changed files
with
166 additions
and
14 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters