NF13 Multiple Variable on Workflow Node

NOTE: This is not yet integrated into core

Goal: Technical

Developer: Deepak Pansheriya Logilite Tchnologies

Feature Ticket: IDEMPIERE-6460

Multi-Variable Support in User Choice, User Task and Set Variable Nodes

This enhancement addresses the limitation of User Choice,User Task and Set Variable workflow nodes, which currently allow setting only a single column value. The inability to update multiple values within the same node requires the use of multiple Set Variable nodes, leading to inefficiencies and execution performance.

Existing Limitations

• Single Column Restriction – User Choice and Set Variable nodes only allow updating one column at a time.
• Complexity in Multi-Value Updates – Multiple Set Variable nodes are needed, making workflows cumbersome and less user-friendly.
• Independent Execution Issues – If multiple set variable nodes are added for value updates, the workflow execution does not ensure successful completion of user task. This can lead to situations where a User choice node failed due to validation, but related variable settings already committed show wrong value set on record.

Solution: Introducing the Variable Sub-Tab

To resolve these challenges, a Variable sub-tab is added under Node tab which is visible when the workflow action type is either:

1. User Choice
2. Set Variable
3. User Task

Design & Implementation

• New Variable Sub-Tab
  • Displays relevant configurations when a workflow node action is User Choice, Set Variable, or User Task.
• Fields in the Variable Tab:

1. Column Name – Specifies the target column name on the record where the variable should be set.
2. Attribute Value – Allows defining a constant value or context variable for assignment.

Impact on iDempiere Workflow Execution

• Enhanced Multi-Variable Support – Allows updating multiple columns within a single workflow node.
• Improved User Experience – Eliminates the need for multiple Set Variable nodes, streamlining workflow design.
• Consistency in Execution – Ensures all variable assignments complete successfully only if node execution successful.