Description:

The Evaluates Multiple Expressions step enables a FlowWright workflow to evaluate multiple expressions as part of a single decision point.

This decision step identifies an invalid expression during validation. Note: The expression is validated for its identity, not for its result. For example, 1==1 is an expression, and TODAY() + 5 is not valid. 

Instead of creating numerous individual decision steps, this component allows several business rules or logical conditions to be grouped together and evaluated in sequence. If every configured expression evaluates successfully, the workflow follows the Passed return path. If any expression fails, the workflow immediately follows the Failed return path and stores information about the failed expression in a specified workflow variable or global variable.

This approach simplifies complex decision logic, improves workflow readability, and makes business rule maintenance easier.

Typical uses include:

• Validating workflow input
• Evaluating business rules
• Checking user permissions
• Verifying approval conditions
• Validating document metadata
• Confirming process prerequisites
• Performing pre-execution validation

By consolidating multiple logical checks into one step, workflows become easier to design and maintain while providing meaningful information about validation failures.

Usage:

The Evaluates Multiple Expressions step is typically placed before critical workflow activities that require several conditions to be satisfied.

During execution:

1. Read the configured list of expressions.
2. Evaluate each expression.
3. If every expression passes, continue through the Passed path.
4. If an expression fails, store the failed expression in the configured workflow variable or global variable.
5. Continue through the Failed path for appropriate error handling or corrective action.

A typical workflow might look like this:

Typical workflow scenarios include:

• Validating form submissions
• Checking mandatory workflow variables
• Confirming user role requirements
• Verifying document properties
• Evaluating approval thresholds
• Validating business policy compliance
• Ensuring prerequisite workflow steps have completed

Example:

Let’s build and execute the “validateExpressionsDef” example.          

• Create a new definition called “validateExpressionsDef” and open the definition in designer mode.
• Drag a “validateExpressions” step to the canvas. 
• Connect the “Start” and “validateExpressions” steps, as shown above. 
• Click the "validateExpressions" step to configure its "Settings" properties. Provide a name for the step. Click the button to configure multiple expressions. Specify the variable or global reference to store the invalid expression syntax. Click the Save button. Note: Click the "AI Predict" button to have the Copilot add new process steps that match your process description. 

• A pop-up window opens for configuration. Click the Add Row (+) button to insert an empty row. Enter the expression syntax in the row. Click the Save button. You may add multiple expressions by adding more rows. 

• The “Logging” configuration is necessary for documentation and to measure workflow progress and percent complete. This is done by configuring the step state and percent fields individually, as shown in the images below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance. The step validates the syntax of each expression. The first invalid expression, in top-down order, is stored in the variable or global reference as configured. 

Tips:

• Group related business validations into a single Evaluates Multiple Expressions step to simplify workflow design.
• Use descriptive expression names to make troubleshooting easier.
• Store the failed expression in a workflow variable for logging, reporting, or user notifications.
• Place this step before expensive operations such as database updates or external system integrations.
• Route the Failed path to corrective actions, approval requests, or validation reports.
• Keep business rules modular so they can be maintained as requirements evolve.
• Combine this step with Decision, Business Rule, Send Email, Log Message, Update Variable Values, or Create Process Instance steps to build comprehensive validation workflows.

Notes:

• At least one expression must be configured before the step can execute.
• The failed expression storage variable is required and should reference an existing workflow variable or global variable.
• Expressions are evaluated according to the configured business logic.
• The Passed and Failed return paths should both be implemented to provide complete workflow handling.
• The stored failed expression can be used for diagnostics, auditing, or user feedback.
• Execution details and evaluation results are recorded in the FlowWright workflow execution log.

Evaluates Multiple Expressions vs. Decision:

Both workflow steps evaluate logical conditions, but they are intended for different levels of decision processing.

As a general guideline:

• Use Evaluates Multiple Expressions when several business rules must be validated together before continuing workflow execution.
• Use Decision when workflow branching depends on a single logical condition.

Definition Sample:

You may download the sample workflow definition from the link provided and import it into your FlowWright environment.

Note: Verify and complete any missing configuration after importing the sample, including:

• Validation expressions
• Workflow variable or global variable for storing the failed expression
• Success and failure workflow branches
• Logging or notification steps
• Business rule definitions

After verifying the configuration, save and publish the workflow before execution.

Click here to download the sample file.