Description:
This step evaluates a given expression and assigns the result of the expression 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 definition called “evalExpressionDef”
- Select the definition and click the “design” button
- Drag a “evalExpression” step to the canvas
- Connect the dots between the start and “evalExpression” step
- Click the "evalExpression" step to configure its "Required" properties. Provide a name to the step.
- Click on 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 in the input field.
- In the expression to evaluate below, the system sets the default calendar for any culture as Gregorian. Hence, other calendars, like Egyptian, Roman, and Thai, shall 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 in the images below. Configure the “Logging” using the following properties.
- Save the process definition, create a new instance, and execute. Render the process instance. Click on the process step to view its properties. The step should evaluate the expression and return TRUE or FALSE to the variable configured.
Definition Sample:
You may download the sample definition(s) from the link here and later import it (drag-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.