Description:

The Update Globals workflow step updates global values through the FlowWright global-variable mapping interface.

Unlike Update Variables, which works with workflow variables, Update Globals is specifically intended for updating globals. The step allows multiple globals to be mapped and updated in a single step.

The step also provides a Has Expression option to control how expressions are handled for the configured global values.

The step supports:

• Updating multiple globals
• Mapping global names to their values
• Expression-based value handling
• True and False return paths

Usage:

The Update Globals step is typically used when a workflow needs to change global values during process execution.

It can be used when a value needs to be maintained globally rather than as an individual workflow variable.

For example, a workflow can:

• Update one or more global values after a business activity.
• Change global configuration values as part of a workflow.
• Set multiple globals at the same point in a process.
• Update globals based on information obtained earlier in the workflow.
• Prepare global values for subsequent workflow activities.
• Use expression handling when assigning global values.

The Update multiple globals mapping is the step's central configuration mechanism.

When the workflow reaches the Update Globals step, the configured global mappings are processed, and the specified global values are updated.

Typical Workflow Suggestions

Update Global Configuration

Use the step when a workflow needs to change a global configuration value.

Example:

Start → Process Configuration → Update Globals → Continue

This allows the workflow to update global values during processing.

Update Multiple Globals

Use Update multiple globals when several global values need to be changed together.

Example:

Process Request → Update Globals → Continue Processing

The mapping interface allows multiple global values to be configured in a single step.

Maintain Workflow-Wide State

Use Update Globals when a value needs to be maintained as a global rather than being limited to an individual workflow variable.

Example:

Complete Business Activity → Update Globals → Subsequent Processing

This can be useful when subsequent workflow processing depends on updated global information.

Update Globals After an Approval

Use the step after an approval or review activity when the result needs to modify one or more global values.

Example:

Submit Request → Approval → Update Globals → Continue

Prepare Global Values for Subsequent Processing

Use Update Globals to establish global values before later workflow activities execute.

Example:

Retrieve Information → Update Globals → Business Processing

Expression-Based Global Updates

Use Has Expression when the global values being assigned require expression handling.

Example:

Process Data → Update Globals → Evaluate Result

The XML defines Has Expression as a Yes/No property with a default value of Yes.

Example:

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

• Create a new process definition named “updateGlobalDef” and open it in Designer mode. 
• Drag the “updateGlobals” step to the canvas.
• Connect the dots between the “Start” step and the “updateGlobals” step, as shown above.
• Select the line between the steps to configure the “Connection Properties”. The default property values are “None, True, False, Error, and Evaluate”. Depending on the step’s purpose, additional values are available for configuration. 
• Define a variable or a global to store the result. 
• Click the "updateGlobals" 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 the Copilot add new process steps that match your process description. 

• Click the "updateGlobals" step to configure its "Optional" properties. Click the button to update multiple globals with values. Set “Yes” if the value to be computed is an expression.

• Click the "updateGlobal" step to configure its "Optional" properties. Click the button to configure multiple globals and values. A pop-up window appears for configuration. Click the Add Row (+) button to insert an empty row. Enter the global name and value. You can add multiple globals using the Add Row button. Click the duplicate icon to quickly repeat the last row and overwrite it with a new name and value. Click the Save button. Set “Yes” if the value to be computed is an expression. Note: Use either single global references or multiple ones, not both. 

• Expression Builder Utility. Click inside the text box. Use the keyboard shortcut “ALT + E” to invoke the expression builder. This utility enables the building and validation of expressions, as shown in the image below. Copy the expression to the clipboard, then paste it into the input field.

• Examples of the condition to evaluate

(1) Variable.number + 10 >100  
(2) Global.testNumber + 100 / Variable.colNum >=1000
(3) Variable.data + "test" == “Apptest”
(4) Global.hasData == 1

• Save the process definition, create a process instance, and execute it. The step should update multiple globals with values. Render the process instance. Select Items> Globals> Latest to view the global values. 

Tips:

• Use Update multiple globals to configure the globals that need to be changed.
• Verify each global mapping before executing the workflow.
• Use meaningful global names so their purpose is clear to workflow designers and administrators.
• Configure Has Expression deliberately when expression handling is required.
• Consider grouping related global updates into one Update Globals step where appropriate.
• Use a meaningful step name such as “Update Global Configuration”, “Set Global Status”, or “Update Process Globals”.
• Test the step together with downstream activities that consume the updated global values.
• Remember that the XML does not define separate properties for an individual global name and value; updates are configured through the Update multiple globals mapping. 

Notes:

The UpdateGlobals step is defined in the Engine category with the internal name updateglobals and display name Update Globals.

The workflow step is implemented by the FlowWright.Workflow.UpdateGlobalsStep namespace in FlowWright.Workflow.dll and is defined as a Process step. It supports 2 incoming connections and 2 outgoing connections.

The step contains two configurable properties:

• Update multiple globals
• Has Expression

Both are marked as optional in the XML.

The Update multiple globals property uses the enterGlobals data type, implemented by FlowWright.DataTypes.ClsEnterGlobals, and is described as “Map globals.”

The Has Expression property uses the selectYesNo data type, implemented by FlowWright.DataTypes.ClsYesNo, and is described as “Get Yes, No as list.”

The default value for Has Expression is Yes.

The XML defines two return paths: False and True.

Feature comparison.

Definition Sample:

You may download a sample definition when provided and import it into your FlowWright Process Definition.

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

• Global mappings
• Global values
• Expression setting
• Outgoing workflow connections
• Environment-specific global configuration

After verifying the configuration, save the Process Definition before execution.

Click here to download the sample file.