Reset Variables

Use this step to reset variables to its initial values.

Last published at: March 30th, 2026

ResetVariablesToInitial Step

Description:

The clsResetVariablesToInitial workflow step resets variables back to their initial values during workflow execution. The step has no configurable input properties; its primary purpose is to perform the reset operation and provide True or False return paths for subsequent workflow processing.

 

Inputs

  • None - The clsResetVariablesToInitial step does not define any input properties.
 

 

Returns

  • True – The True return path can be connected to the next workflow activity after the reset operation.
  • False – The False return path can be connected to an alternative or error-handling workflow path.
 

 

Usage:

The Reset Variables step is typically placed in a workflow when variables need to be returned to their initial values before subsequent workflow processing.

A typical workflow pattern is:

Update Variables → Reset Variables → Continue Process

The step can be useful when a workflow reaches a point where previously modified variable values should no longer be used for subsequent processing.

For example:

Process Data → Modify Variables → Reset Variables → Continue Processing

Since the step has no configurable inputs, it requires no mapping or value configuration on the step itself.

The True and False return paths can be connected to subsequent workflow activities according to the desired process flow.

 

 

Typical Workflow Suggestions:

Reset Variables After Temporary Processing

Use the step after a section of workflow processing that temporarily changes variable values.

Example:

Process Data → Update Variables → Reset Variables → Continue Process

The reset step provides a point where variables can be returned to their initial values before the workflow continues.

 

Reset Variables Before Reusing a Workflow Path

Use the step before a workflow section that should begin with the variables in their initial state.

Example:

Previous Processing → Reset Variables → Start Next Processing Section

This provides a reset point between different stages of workflow processing.

 

Reset Variables After an Alternative Processing Path

Use the step after an alternate processing branch when modified variable values should be reset before the workflow rejoins the main process.

Example:

Evaluate Request → Alternate Processing → Reset Variables → Continue Process

You can place the reset operation at the end of the alternate processing path.

 

Reset Variables Before Repeating Processing

Use the step when workflow processing is repeated and variables need to be reset before another processing cycle.

Example:

Process Data → Reset Variables → Repeat Processing

This provides a reset activity between processing cycles.

 

Reset Variables Before Completing a Workflow Section

Use the step as the final variable-reset activity before moving to another workflow stage.

Example:

Complete Current Processing → Reset Variables → Next Workflow Activity

This can help establish a defined transition point before subsequent workflow processing.

 

Example:

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

  • Create a new process definition named “clsResetVariablesToInitialDef" and open it in designer mode. 
  • Define a variable or a global to store the result.
  • Drag an “UpdateVariables, and clsResetVariablesToInitial" step to the canvas.
  • Connect the dots between the “Start” and other steps, 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, you can configure additional values.
  • 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 the Copilot add new process steps that match your process description. 

 

  • Click the "updateVariable" step to configure its “Optional” properties. Click the Update Multiple Variables button. Click the Add Row button to insert an empty row. Enter the variable name and value as shown below. Click the Save button. You may configure multiple variables and values by using the Add Row button.   

 

  • Click the "clsResetVariablesToInitial" step to configure its “Settings” 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. 

 

  • The “Logging” configuration is necessary for documentation and also measures workflow progress and percent complete. Configure 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 an instance, and execute it. The process step should reset the variable values to the configured values. 

 

  • Render the process instance. Click each process step and verify its properties. The "clsRestvariablesToInitial" step should return the variable's initial value.

 

Tips:

  • Use the Reset Variables step at a clearly defined point in the workflow where variables need to return to their initial values.
  • Remember that the step does not provide configurable input properties.
  • Place the step after processing that intentionally changes variable values when those changes should no longer be carried forward.
  • Consider using the step before a subsequent processing section when that section should start with variables in their initial state.
  • Connect the True path to the next workflow activity as appropriate.
  • Connect the False path when alternative or error-handling processing is required.
  • Test the workflow with representative variable values before deploying it to production.
  • Verify the values of relevant variables before and after the step when validating the workflow.
  • Avoid assuming that the step provides selective variable reset configuration because no input properties are defined in the XML.
  • When using the step in a larger workflow, document why the reset point is required so that later workflow changes do not unintentionally remove it.
  • Test workflows that contain repeated or alternative processing paths to verify the expected variable state at each stage.
  • Do not assume specific behavior for variables that are outside the scope of the FlowWright implementation defined by this step.
  • The XML does not define whether individual variables can be excluded from the reset operation.
  • The XML does not define the exact conditions that cause the step to return True or False.

 

Definition Sample:

You may download the sample definition(s) from the link provided and later import them (drag-and-drop) into your FlowWright Process Definition (XML file) or Form Definition (HTML file) page.

After adding this step to a process definition, verify the workflow configuration, including:

  • The location of the Reset Variables step in the workflow.
  • The workflow activities that precede the reset.
  • The workflow activities connected to the True path.
  • The workflow activities connected to the False path, when required.
  • The expected variable values before and after the reset operation.
  • Any downstream workflow logic that depends on variable values.

Click here to download the sample file.