Building and Using Converter Flows
  • 21 Jul 2022
  • 3 Minutes to read
  • Dark

Building and Using Converter Flows

  • Dark


A Converter Flow is a Flow Behavior that can convert Input Data from one Data Type into another. Using a Converter Flow can be used to clean up data that can be handled more elegantly within a process or displayed as desired.

Default Converter Flows

The default Converter Flows are displayed in the table below. These options can be found by navigating to System > Designers > Catalog > System Defaults > Converter Flows

It is highly recommended to not edit the default converter Flows, for additional assistance and questions, please contact
Converter FlowFunction
Convert String to BoolConverts String input to Boolean output
Convert String to Byte ArrayConverts String input to ByteArray output

Convert String to Date

Converts String input to Date output

Convert String to Decimal

Converts String input to Decimal output
Convert String to Int32Converts String input to Int32 output

Convert String to Int64

Converts String input to Int64 output

Get Unique Strings from List

Searches List input for duplicate String inputs

Merge String List to Single String

Converts a list of Strings into a single String

Set Decimal Places on Number

Collects number values in a String input and then adds a specified number of decimal places

Trim String Flow

Shortens the String input to a specified length

Optimizing Converter Flows

Converter Flows can be optimized by caching their outcomes. This can be done by navigating to the Properties panel for the Flow and expanding the Outcomes header. 

From here, users can configure the Cache Outcomes for the Flow, though there are some limitations:

  • If the Converter Flow fetches from a database, the values must match the input values to the Flow.
  • If the Converter Flow fetches data through an API call, the values must match the input values to the Flow.

For example, if the Converter Flow fetches a string input and its value matches the input to the Flow, then caching can be used. The only major change can be the data types between the two values. 

Building a Converter Flow

The following example will demonstrate how to use a Converter Flow to convert a String into a DateTime value. 

Sample Project 
The following sample project can be importedand serve as a visual guide.
  1. From a Designer Project, select the CREATE FLOW button. Then, CREATE a new Converter Flow by selecting Converter Flow under the Converters category. 
  2. In the Flow Designer, attach a Parse Date step from the Toolbox panel by navigating to DATA > DATES to the Start and End steps.
  3. Select the Start step. Under the FLOW INPUTS category, click SHOW EDITOR under the Flow Input Data field.
  4. From the Flow Inputs window, enter "DateAsString" and select String [Text] from TYPE. Click Save and close the window.
  5. Select the Parse Date step and on the Properties panel, map DateAsString to the Date field.
  6. Select the End step. Click SHOW EDITOR under Output.
  7. From the Output Data window, enter "ParsedDate" under NAME and select Date Time as the TYPE. Click the pencil icon under INPUT and map it to ParseDate1_Output. Click Save and close the window.
  8. Click Save and close the Flow Designer.

Running a Converter Flow

  1. In a Designer Project, CREATE a new Flow.
  2. From the Flow Designer, attach a Show Form step from the FAVORITE STEPS category to the Start step. Select PICK OR CREATE FORM from its Properties and create a new Form.
  3. Configure the Form with a Date Time Picker (StringDataPicker) and a Button. Click Save and close the Form.
  4. Back in the Flow Designer, from the Properties of the Show Form step, under INPUTS, configure the mapping for the String Data Picker field to the previously created Converter Flow by clicking Unknown >Converters > [Name of the Converter Flow] from the mapping options.
  5. After the Converter is applied to the Input, locate the Converter Flow's Input under EDIT CONVERTER and enter "10/11/2022".  Acceptable DateTime formatsare formats that can be utlized in C#.

  6. Connect the Done path to the End step. Click Save to save changes to the Flow.
  7. Click Debug on the top action bar. Click START DEBUGGING.
  8. When the Flow reaches the Form, either use the previously defined String value or select a new one via the Date Time Picker, then click Done.  
  9. After the debugger runs, select the Form step, select Execution 1, and click View Input/Output Data.

For further information on Flows, visit the Decisions Forum.

Was this article helpful?