Description:

The Base64Decode step is used to decode Base64-encoded text within a FlowWright workflow.

This step is useful when workflow data is received or stored in Base64-encoded form and subsequent workflow processing requires the decoded string.

Usage:

Use the Base64Decode step whenever a workflow receives or maintains text in Base64-encoded form and needs the decoded string for subsequent processing.

A typical workflow pattern is:

Receive Base64 Text → Decode Base64 → Store Result → Process Decoded Value

You can supply the encoded value directly or through workflow data, and the decoded result is stored in the specified Variable/Global.

For example, a workflow may receive an encoded text value from an integration, decode it, and then pass the resulting text to another workflow step.

Typical Workflow Suggestions:

Decode an Encoded Integration Value

Use Base64Decode when an external integration provides a text value in Base64-encoded form.

For example:

Receive Integration Data → Base64Decode → Process Decoded Text

The decoded value can be stored in a Variable/Global and passed to subsequent workflow processing.

Decode Text Before Business Processing

Use the step when business logic requires the original text rather than its encoded representation.

For example:

Retrieve Encoded Value → Base64Decode → Evaluate/Process Text

This allows downstream workflow steps to operate on the decoded string.

Decode Data Received from an API

Use Base64Decode when an API response or integration payload contains a Base64-encoded text value.

For example:

REST/API Call → Extract Encoded Value → Base64Decode → Store Result

The resulting decoded string can then be used by subsequent workflow steps.

Decode a Value Before Storing or Comparing It

Use the step when a workflow needs to decode a value before performing a comparison, validation, or other processing operation.

For example:

Retrieve Encoded Value → Base64Decode → Compare/Validate → Continue

The Variable/Global containing the decoded value can be used by later workflow logic.

Decode Text as Part of an Automated Transformation

Use Base64Decode as one stage of a workflow that transforms data between different representations.

For example:

Receive Data → Decode Base64 → Transform Data → Generate Output

This can be useful when encoded text needs to be converted into a usable string before the workflow performs additional transformations.

Example:

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

• Create a new process definition named “Base64decodeDef” and open it in designer mode. 
• Drag a “base64Encode” and “base64Decode” step to the canvas.
• Connect the dots between the “Start”, “base64Encode”, and “base64Decode” 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.
• Define a variable or a global to store the encoded and decoded value. 
• Click the “base64Encode” step to configure its “Required” properties. Enter a name for the step. Enter a text string to encode. Enter a variable or global reference to store the value. Click the Save button. Note: Click the "AI Predict" button to have Copilot add new process steps that match your process description. 
   

• Click the “base64Decode” step to configure its “Required” properties. Provide a variable or global reference for the text to decode, and another variable or global reference to store the decoded value. Click the Save button.  Note: Click the "AI Predict" button to have 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 below. Configure the “Logging” using the following properties.

• Save the process definition, create a new instance, and execute it. Render the process instance. When the workflow reaches the Base64Decode step, FlowWright uses the value supplied to Text to decode and performs the decoding operation. The resulting decoded value is stored in the Variable/Global specified in Variable/Global. The workflow then follows the True or False return path based on the result of the operation. Click the process step to view its properties. The step should encode and decode the text, storing the result in a variable or a global, as shown below. 

Tips:

• Provide a Base64-encoded value: The Text to decode input should contain the value intended for Base64 decoding.
• Use Variables/Globals for dynamic values: This allows encoded values obtained during workflow execution to be decoded without hard-coding them.
• Store the result in a dedicated Variable/Global: This makes the decoded value available to subsequent workflow steps.
• Use the True and False paths: Connect both outputs to appropriate workflow logic so the workflow can respond to the result.
• Validate upstream data when appropriate: If the encoded value originates from an external system, consider validating or handling unexpected input before relying on the decoded result.
• Use the decoded value downstream: Subsequent steps can use the Variable/Global configured in the output property.

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. 

Note: After the import, verify and complete any missing configurations, such as file path references and database connections. Then, save the definition to confirm the changes. 

Click here to download the sample file.