Description:

The Simple Expression Evaluation step enables a FlowWright workflow to perform a straightforward comparison between two values using a selected evaluation operator.

This step is commonly used to implement basic business rules, validate user input, compare workflow variables, or determine whether specific conditions have been met before continuing workflow execution. Rather than requiring complex expressions or decision tables, this step provides a lightweight mechanism for evaluating a single condition.

The workflow specifies a source value, selects the comparison operator, provides a target value, and specifies a workflow variable or global variable in which to store the evaluation result. The step then evaluates the expression and follows either the True or False execution path based on the outcome.

Typical uses include:

• Comparing workflow variables
• Validating form field values
• Checking approval status
• Evaluating numeric thresholds
• Verifying string values
• Comparing dates or identifiers
• Implementing simple business rules
• Performing conditional workflow branching

This step simplifies workflow design by allowing individual comparison operations without requiring more advanced decision logic.

Usage:

The Simple Expression Evaluation step is typically used before conditional workflow branches where a single business rule determines the next activity.

During execution:

1. Read the configured source value.
2. Read the selected comparison operator.
3. Read the configured target value.
4. Evaluate the expression.
5. Store the evaluation result in the configured workflow variable or global variable.
6. Continue workflow execution through either the True or False return path.

A typical workflow might look like this:

Typical workflow scenarios include:

• Checking whether an order exceeds an approval limit
• Validating employee department values
• Comparing calculated totals
• Verifying document status
• Evaluating workflow variables
• Determining whether optional processing should occur
• Implementing simple conditional routing

Example:

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

• Create a new definition called “simpleExpressionDef” and open the definition in designer mode. 
• Drag a “updateVariables, simpleExpression” step to the canvas. 
• Connect the dots between the “Start” and other steps, as shown above
• Define a variable or a global to store the source value, the target value, and the result value.
• Click the "updateVariables" step to configure its "Required" properties. Provide a name for the step, then click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 

• Click the "updateVariables" step to configure its "Optional" properties. Click the button to configure multiple variables. A pop-up window appears for configuration. Click the Add Row button to insert an empty row. Enter the variable name and value. Click the Save button. You can add multiple variables and values using the Add Row button. 

• Click the "simpleExpression" step to configure its "Required" properties. Provide a name for the step. Provide variable or global references for the source and target values. Provide a variable or global reference to store the result. Click the Save button. Note: Click the "AI Predict" button for the Copilot to add new process steps that match your process description. 

• Click the button to configure the operator. A pop-up window will appear, as shown below. Select the data type (number, string, or date). Then select the operator from the drop-down list. The operator list varies by data type. The expression list for the Number data type is shown below. Click the Save button. 

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

• Save the process definition, create a new instance, and execute it. Render the process instance. Click the process step to view its properties. The step should evaluate the simple expression and store the result in the variable or global as configured. 

Tips:

• Use workflow variables for both the source and target values when comparisons depend on runtime data.
• Select the comparison operator that best matches the required business rule.
• Store the evaluation result in a descriptive workflow variable when the outcome will be reused later in the workflow.
• Validate input values before performing comparisons to avoid unexpected evaluation results.
• Route the False path to alternative processing or user notification when business rules are not satisfied.
• Use this step for simple comparisons instead of more complex decision logic where only one condition needs to be evaluated.
• Combine this step with Evaluates Multiple Expressions, DB Decision Table, Update Variable Values, Send Email, or Create Process Instance steps to build flexible decision-driven workflows.

Notes:

• Both the Source Value and Target Value are required.
• A comparison operator must be selected before the step can execute.
• The evaluation result is stored in the configured workflow variable or global variable.
• The exact comparison behavior depends on the selected evaluation operator and the supplied values.
• Both the True and False return paths should be implemented to provide complete workflow handling.
• Execution details and evaluation results are recorded in the FlowWright workflow execution log.

Simple Expression Evaluation vs. Evaluates Multiple Expressions:

Both workflow steps evaluate business conditions, but they differ in scope and complexity.

As a general guideline:

• Use Simple Expression Evaluation when a workflow requires a single comparison between two values.
• Use Evaluates Multiple Expressions when several business rules must be evaluated together before determining the next workflow action.

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:

• Source value
• Comparison operator
• Target value
• Workflow variable or global variable for storing the evaluation result
• Success and failure workflow branches
• Any required workflow variables or expressions

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

Click here to download the sample file.