Add an optional condition expression attribute to all Business Process activities so they execute only when the condition evaluates to true, minimizing the need for wrapping <if> blocks.

Currently, in Business Processes , if a developer wants to execute a single activity-such as an <assign>, <call>, or <transform>-conditionally, they must explicitly wrap that activity inside an <if> block or manage complex transition conditions. For simple conditional checks, this approach adds unnecessary nested layers to the BPL visual designer.

My suggestion
Introduce an optional condition property (or attribute) to all core BPL activities.

If the condition field is left empty/blank, the activity executes normally as it does today.

If a logical expression or ObjectScript expression is provided, the Business Process engine evaluates this expression immediately before reaching the activity. The activity only activates if the condition evaluates to true; otherwise, it is skipped entirely, routing directly to the next step.

ADMIN RESPONSE

Jun 11, 2026

Thank you for submitting the idea. The status has been changed to "Needs review".
Stay tuned!

Post comment

Please enter your email address

RELATED IDEAS

Add an optional condition expression attribute to all Business Process activities so they execute only when the condition evaluates to true, minimizing the need for wrapping <if> blocks.