Developer Blog |
A new Appway patch release with version 5.3.2 is available. It is a bugfix release with 18 bugfixes, 3 features and 7 changes. The risk of upgrading from 5.3.1 to 5.3.2 is minimal to zero.
Release notes 5.3.2 (PDF)
Appway 5.3.2 comes with an (optional) extended strategy for the assignment of participants to process tokens on tasks and sub-processes. Up to Appway 5.3.1, the assignment was made based on the participant selected on the swimlane or the return value of the swimlane expression. This is still the default strategy in Appway 5.3.2.
What is new is that, if the configuration property "nm.workflowengine.assignmentstrategy" is set to "Extended", Appway 5.3.2 will use an extended assignment strategy:
The extended assignment strategy allows users to "override" the default assignment rules based on swimlanes by setting a participant in an attribute or property of the process token.
The advantage of using a property is that it exists only for as long as the token is on the current process element ("override once"). If an attribute is used instead, it moves together with the token through the process ("sticky override").
Release notes 5.3.2 (PDF)
Appway 5.3.2 comes with an (optional) extended strategy for the assignment of participants to process tokens on tasks and sub-processes. Up to Appway 5.3.1, the assignment was made based on the participant selected on the swimlane or the return value of the swimlane expression. This is still the default strategy in Appway 5.3.2.
What is new is that, if the configuration property "nm.workflowengine.assignmentstrategy" is set to "Extended", Appway 5.3.2 will use an extended assignment strategy:
- If the process token already has an assigned participant, it is not reassigned.
- If the process token has a property "Appway.QueueName", the value of this property is used as participant.
- If the process token has an attribute "Appway.QueueName", the value of this attribute is used as participant.
- Otherwise, the default assignment strategy is used.
The extended assignment strategy allows users to "override" the default assignment rules based on swimlanes by setting a participant in an attribute or property of the process token.
The advantage of using a property is that it exists only for as long as the token is on the current process element ("override once"). If an attribute is used instead, it moves together with the token through the process ("sticky override").
Comments (0)
Developer is transitioning to Appway Community
The next step in the transition to community.appway.com is here! As of April 2017, the Community Blog is exclusively available via community.appway.com. The Blog joins the Forum and our Support system, which already moved to their new home in 2016.
Our written material (recipes and documentation) is currently being migrated, and is available in beta on community.appway.com at Support > Knowledge Base.
All information for Appway 6.3 and below is still available here on developer.appway.com while this migration takes place.
Note: Material relevant for Appway 7 will only be available in the Knowledge Base on community.appway.com
Any questions or feedback? Please contact community@appway.com
Our written material (recipes and documentation) is currently being migrated, and is available in beta on community.appway.com at Support > Knowledge Base.
All information for Appway 6.3 and below is still available here on developer.appway.com while this migration takes place.
Note: Material relevant for Appway 7 will only be available in the Knowledge Base on community.appway.comAny questions or feedback? Please contact community@appway.com