Description:
This step evaluates a given expression and assigns the result to a variable.
Inputs
- Expression – expression to evaluate
- variableName – name of the variable to store the resulting value from the expression
Returns
- True – expression evaluated successfully
- False – expression failed to evaluate
Usage:

Example:
Let’s build and execute the “evalExpressionDef” example.
- Create a new process definition called “evalExpressionDef” and open the definition in designer mode.
- Drag an “evalExpression” step to the canvas.
- Define a variable or a global to store input and output values.
- Connect the dots between the “Start” and “evalExpression” steps, as shown above.
- Click the "evalExpression" step to configure its "Required" properties. Provide a name for the step. Provide a variable or a global reference to store the expression result. Provide the C# expression to evaluate. 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 Expression to evaluate the field. Press Alt+E on the keyboard to invoke the Expression Builder. This utility enables you to build and validate expressions, as shown in the image below. Send the expression to the clipboard and paste it into the input field.

- In the expression below, the system sets the default calendar for any culture to the Gregorian calendar. Hence, other calendars, such as the Egyptian, Roman, and Thai calendars, will display the current date, month, and year.

- Examples for expression to evaluate:
e.g. Variable.number + 10
e.g. Global.testNumber + 100 / Variable.colNum
e.g. Variable.data + "test"
e.g. Global.hasData == 1
e.g. DateTime.Today.ToString()
e.g. DateTime.Today.AddDays(14).ToString()
- The “Logging” setting configuration is necessary for documentation and also measures the workflow progress and the percent complete. This is achieved by configuring the step state and percent fields individually, as shown below. Configure the “Logging” using the following properties.

- Save the process definition, create a new instance, and then execute it. Render the process instance. Click the process step to view its properties. The step should evaluate the expression and return “True” or “False” to the variable or global, as configured.
Definition Sample:
You may download the sample definition(s) from the link here and later import them (drag-and-drop) to your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.
Note: Please verify and complete the process steps for any missing configurations, such as file path references and database connections, after import. Then, save the definition to confirm the changes.