Process Studio - Workflows - WHEN Conditional

  • Updated

Overview

A WHEN conditional evaluates criteria to determine the execution path within a workflow template. It is utilized in the Starting Rule node, Rule node, and Schedule node. When the condition evaluates to true, the execution continues through the corresponding path. When the condition evaluates to false, the system evaluates the subsequent path condition.

 

Prerequisites 

  • A Workflow template must be created.
  • A Starting rule must be configured on the canvas.

 

Required Permissions

  • Admin permissions with Workflow configuration access.

 

Key Components

A WHEN condition consists of three primary components:

  • Context: Conditions always start from the execution context (formerly referred to as the target object). From the context, the condition can traverse any related object.
  • Operator: The logical comparator that defines the condition.
  • Value: The target data used to compare against the selected field.

Operators

Neostella provides two operator families to evaluate data: Status and Event.

Status Operators
Status operators check whether:

  • =: the field exactly matches the given value.
  • !=: the field does not match the given value.
  • >: a numeric or date field is greater than the specified value.
  • <: a numeric or date field is less than the specified value.
  • >=: a numeric or date field is greater than or equal to the value.
  • <=: a numeric or date field is less than or equal to the value.
  • contains: the field includes the specified value anywhere within it.
  • not contain: the field does not include the specified value.
  • start with: the field begins with the specified value.
  • ends with: the field ends with the specified value.
  • in: the field matches any value within a specified list.
  • not in: the field does not match any value within a specified list.
  • is empty: the field has no value.
  • is not empty: the field contains any value.


Event Operators
Event operators test what a value did during an update. These operators are only available where the rule listens to an event, such as the conditions of the starting rule or within a rule where Event Triggered is enabled.

  • old: evaluates the previous value of the field before the event occurred.
  • new: evaluates the new value of the field after the event occurred.
  • changed: evaluates whether the specified field was modified during the event.


 

 

Configuration Steps

  1. Open the workflow template in Process Studio.
  2. Select the Starting node, Rule node or Schedule node.
  3. Toggle Conditions to enable it.
  4. Define the Context field, the Operator, and the Value.
  5. Use the rule builder to add AND, OR, or parentheses logic if required.
  6. Click + PATH to add additional mutually exclusive outcomes.
  7. Click SAVE.



 

 

Technical Considerations

Event Filtering

All data narrowing must occur within the WHEN conditions. Admins must use Event Operators to isolate the specific field that changed and the value it changed to.

 

Complex Logic and Grouping

Admins can combine multiple WHEN conditions to create advanced logic tailored to business requirements.

  • AND: all conditions connected with AND must evaluate to true.
  • OR: at least one condition connected with OR must evaluate to true.
  • Parentheses are supported to group conditions into complex expressions, extending beyond flat AND and OR chains.


 

Path Exclusivity

Path evaluation follows a defined order. The system evaluates paths in sequence, and the first path that meets the condition is triggered. Conditions should be written to be mutually exclusive to prevent unintended routing based on creation order.

 

Validation

  • Executions can be monitored from the global list at Control Center -> Process Studio -> Workflows -> Running tab or from the contextual Workflows view of a specific Project or Lead record.

Troubleshooting

Symptom: The workflow generates an execution on every saved record.

  • Cause: The event listener catches all updates, and the conditions do not effectively isolate the specific change.
  • Resolution: Use event operators such as changed or new to narrow the condition to the specific field modification required.

Symptom: An execution is stalled at an intermediate rule.

  • Cause: The execution is waiting on an event that has not occurred, or an upstream branch dead-ended.
  • Resolution: Click the rule to open the rule sidebar. Review the Conditionals Evaluation stage to verify which paths are evaluated as true or false.

 

Use Cases

  • Status Evaluation: WHEN Case Status = Closed. The execution follows the path only when the field exactly matches the specified value.   
  • Multiple Conditions (AND): WHEN Case Status = Closed AND Judgment Date is not empty. Both conditions must evaluate to true to proceed.   
  • Multiple Conditions (OR): WHEN Judge Assignment is empty OR Hearing Date is empty. The execution proceeds if either condition evaluates to true.