Description:

The Base64Encode step converts text into a Base64-encoded string within a FlowWright workflow.

Use this step when workflow data needs to be represented in Base64 format before being passed to another workflow step or integration.

Usage:

Use the Base64Encode step whenever a workflow needs to convert a text string into Base64.

A typical workflow pattern is:

Prepare Text → Encode Base64 → Store Result → Send/Process Encoded Value

You can supply the text directly or through workflow data, and store the encoded result in the specified Variable/Global.

For example, a workflow may prepare a text value, encode it using Base64Encode, and then pass the encoded value to a subsequent integration or processing step.

Typical Workflow Suggestions:

Encode Text Before an Integration

Use Base64Encode when an integration requires a text value to be represented in Base64 format.

For example:

Prepare Integration Data → Base64Encode → REST/API Call

The encoded value stored in the Variable/Global can then be supplied to the integration step.

Encode Workflow Data for Transmission

Use the step when workflow data needs to be converted into an encoded string before being passed to another system.

For example:

Collect Workflow Data → Base64Encode → Send Data

This allows the workflow to use the encoded representation in subsequent processing.

Encode Text Before Storing It

Use Base64Encode when a workflow needs to transform a text value into a Base64 representation before storing it or passing it elsewhere.

For example:

Retrieve Text → Base64Encode → Store Encoded Value

The resulting value is placed in the Variable/Global specified by the step.

Encode Data as Part of a Transformation

Use the step as part of a workflow that transforms data from one representation to another.

For example:

Retrieve Data → Format Text → Base64Encode → Generate Output

The encoded value can then be used by subsequent workflow steps.

Encode a Value Before Passing It to Another Process

Use Base64Encode when a workflow needs to prepare a text value before passing it to another process or workflow operation.

For example:

Generate Value → Base64Encode → Pass Encoded Value → Continue Processing

This keeps the encoding operation as a dedicated transformation step within the workflow.

Example:

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

• Create a new definition named “base64EncodeDef” 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 variable to store the encoded and decoded values. 
• Click the “base64Encode” step to configure its “Required” properties. Provide a name for the step. Enter a text string to encode. Specify a variable or global reference to store the value. 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 “base64Decode” step to configure its “Required” properties. Provide a variable or global reference to store the encoded value, then 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 Base64Encode step, FlowWright uses the value supplied to Text to encode and performs the Base64 encoding operation. The resulting encoded string 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 the text and store the result in a variable or global, as shown below. 

Tips:

• Provide the text to encode: Ensure Text to encode contains the value you want to convert.
• Use Variables/Globals for dynamic values: This allows workflow-generated or previously retrieved text to be encoded.
• Store the result in a dedicated Variable/Global: This makes the encoded value available to subsequent workflow steps.
• Use the encoded value downstream: The Variable/Global configured in the second input can be referenced by later processing or integration steps.
• Use both return paths: Connect the True and False outputs to appropriate workflow logic.
• Keep encoding as a dedicated transformation: Separating encoding from subsequent integration or processing makes the workflow easier to understand and maintain.

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.