-
Feature Request
-
Resolution: Won't Fix
-
L3 - Default
-
None
-
None
-
None
User Story (Required on creation):
I can enable or disable the "Async Before/After" flag dynamically via expression.
Functional Requirements (Required before implementation):
In the BPMN XML, it is possible to define the following properties on flow nodes:
- camunda:asyncBeforeExpression="${asyncBefore}"
- camunda:asyncAfterExpression="${asyncAfter}"
Technical Requirements (Required before implementation):
- The feature is exposed in the Model API
- The BPMN parser can handle the new properties
- Documentation exists BPMN 2.0 reference
Limitations of Scope (Optional):
Hints (Optional):
Original description
I worked on a recent project in Brazil where we had to create your versions of the same process:
my-process-sync
my-process-async
The only difference between them that one had synchronous tasks and the other asynchronous tasks, due to an omnichannel need of the customer's business.
You think it would be useful if we could, instead of selecting the "Asynchronous Before" and "Asynchronous After" checkboxes, set an Expression Language so we could set this property dynamically based on variables.
This is the controller panel for Smart Panels app
[CAM-13606] TaskSync based in Expression Language
| Assignee | New: Tassilo Weidner [ tassilo.weidner ] |
| Mentioned Roles |
| Mentioned Groups |
| Description |
Original:
h4. I worked on a recent project in Brazil where we had to create your versions of the same process:
*my-process-sync* *my-process-async* The only difference between them that one had synchronous tasks and the other asynchronous tasks, due to an omnichannel need of the customer's business. You think it would be useful if we could, instead of selecting the "*Asynchronous Before*" and "*Asynchronous After*" checkboxes, set an Expression Language so we could set this property dynamically based on variables. |
New:
h4. User Story (Required on creation):
I can enable or disable the "Async Before/After" flag dynamically via expression. h4. Functional Requirements (Required before implementation): h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): h4. Hints (Optional): h4. Original description I worked on a recent project in Brazil where we had to create your versions of the same process: *my-process-sync* *my-process-async* The only difference between them that one had synchronous tasks and the other asynchronous tasks, due to an omnichannel need of the customer's business. You think it would be useful if we could, instead of selecting the "*Asynchronous Before*" and "*Asynchronous After*" checkboxes, set an Expression Language so we could set this property dynamically based on variables. |
| Mentioned Roles |
| Mentioned Groups |
| Mentioned Roles |
| Mentioned Groups |
| Description |
Original:
h4. User Story (Required on creation):
I can enable or disable the "Async Before/After" flag dynamically via expression. h4. Functional Requirements (Required before implementation): h4. Technical Requirements (Required before implementation): h4. Limitations of Scope (Optional): h4. Hints (Optional): h4. Original description I worked on a recent project in Brazil where we had to create your versions of the same process: *my-process-sync* *my-process-async* The only difference between them that one had synchronous tasks and the other asynchronous tasks, due to an omnichannel need of the customer's business. You think it would be useful if we could, instead of selecting the "*Asynchronous Before*" and "*Asynchronous After*" checkboxes, set an Expression Language so we could set this property dynamically based on variables. |
New:
h4. User Story (Required on creation):
I can enable or disable the "Async Before/After" flag dynamically via expression. h4. Functional Requirements (Required before implementation): In the BPMN XML, it is possible to define the following properties on flow nodes: * {{camunda:asyncBeforeExpression="${asyncBefore}"}} * {{camunda:asyncAfterExpression="${asyncAfter}"}} h4. Technical Requirements (Required before implementation): * The feature is exposed in the Model API * The BPMN parser can handle the new properties * Documentation exists BPMN 2.0 reference h4. Limitations of Scope (Optional): h4. Hints (Optional): h4. Original description I worked on a recent project in Brazil where we had to create your versions of the same process: *my-process-sync* *my-process-async* The only difference between them that one had synchronous tasks and the other asynchronous tasks, due to an omnichannel need of the customer's business. You think it would be useful if we could, instead of selecting the "*Asynchronous Before*" and "*Asynchronous After*" checkboxes, set an Expression Language so we could set this property dynamically based on variables. |
| Assignee | Original: Tassilo Weidner [ tassilo.weidner ] | New: Tobias Metzke-Bernstein [ tobias.metzke ] |