validateExpressions step
Description:
This decision step is used to identify 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.
Inputs
- expressions – enter multiple expressions
- varToStoreResult – variable/global to store the first failed expression
Returns
- passed – expression passed validation
- failed – expression failed validation
Usage:
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.
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 import process steps for any missing configurations, including file path references and database connections. Then, save the definition to confirm the changes.