Description:

The Split String workflow step splits a supplied string using a specified delimiter.

The step accepts a string to split, identifies the delimiter to use, and stores the resulting split XML in a Variable or Global variable. The XML defines the step in the Engine category with the internal name splitstring, label “Splits a string using a delimiter”, and display name “Split String.” It is implemented by FlowWright.Workflow.SplitString in FlowWright.Workflow.dll and is a Process step with two incoming and two outgoing connections.

The step supports:

• Splitting a string using a delimiter
• Supplying the string dynamically
• Supplying the delimiter dynamically
• Storing the resulting split XML in a Variable or Global variable
• Using the split result in subsequent workflow activities

This step can be used for:

• Processing comma-separated values
• Parsing delimited lists
• Separating user-provided values
• Breaking imported text into individual values
• Preparing data for subsequent workflow processing
• Parsing values returned by external systems
• Converting a delimited string into structured workflow data
• Supporting dynamic workflow routing or processing

Usage:

The Split String step is typically placed after a string has been collected, generated, or retrieved within a workflow.

The input can be dynamically constructed using Variables, Global variables, form values, previous workflow outputs, or information retrieved from external systems.

The resulting split XML can then be used by subsequent workflow activities for additional processing.

This follows the same general workflow pattern as the FlowWright documentation example: a processing step receives information from an earlier activity, performs its operation, stores the result, and passes control to subsequent activities.

Typical downstream uses include:

• Processing individual values
• Making workflow decisions
• Routing workflow instances
• Populating Variables
• Building dynamic requests
• Generating reports
• Processing imported data
• Passing structured results to other workflow steps

Typical Workflow Suggestions:

Process a Delimited List

Use Split String when a workflow receives several values in a single delimited string.

Example:

Receive List → Split String → Process Values

This is useful for lists of customers, departments, categories, identifiers, or other values.

Process Form Input

Split a form field containing multiple values.

Example:

Form Submission → Split String → Validate / Process Values

For example, a user could provide:

North,South,East,West

and the workflow can split the value for subsequent processing.

Parse External System Data

Use the step after retrieving a delimited value from an external application.

Example:

Get External Data → Split String → Process Result

This can help convert a simple delimited response into data that subsequent workflow activities can work with.

Process Email or Text Data

Split text obtained from an email, document, or other text-processing activity.

Example:

Receive Text → Extract Value → Split String → Process Values

Dynamic Workflow Routing

Use the split result as part of a workflow that determines how subsequent information should be processed.

Example:

Get Routing List → Split String → Evaluate Values → Route

Generate Multiple Processing Inputs

Use Split String to prepare a list of values for subsequent workflow operations.

Example:

Receive Product List → Split String → Process Products

Parse Configuration Values

Split a configuration value containing multiple entries.

Example:

Read Configuration → Split String → Apply Configuration

Prepare Structured Data

Use the split XML output when downstream processing benefits from a structured representation of the individual values.

Example:

Receive Delimited String → Split String → Process Structured Result

The step explicitly stores its output as split XML, although the XML definition does not document the precise structure of that XML.

Variable-Based Processing

Use Variables or Global variables to supply the input string and delimiter dynamically.

Example:

Get Variables → Split String → Process Dynamic Values

This allows the same Process Definition to handle different input values at runtime.

Failure Handling

Use the False return path to handle an unsuccessful split operation.

Example:

Split String → True → Continue Processing

↳ False → Log Failure / Retry / Notify Administrator

The XML explicitly defines True and False return paths.

Example:

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

• Create a new definition called “splitStringDef" and open the definition in designer mode.
• Drag a “splitString” step to the canvas.
• Connect the dots between the “Start” and “splitString” 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, additional values are available for configuration. 
• Define a variable or a global to store the result. 
• Click the "splitString" step to configure its "Required" properties. Provide a name for the step. Provide a string value or variable reference. Provide a delimiter to split the string. Provide a variable or a global reference to store the split XML result. 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. This is achieved by configuring 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 a new instance, and execute it. Render the process instance. Click the process step. When the workflow reaches the Split String step, the supplied string is split according to the configured delimiter, and the resulting split XML is stored in the configured Variable or Global variable. The workflow then follows the True or False return path based on the execution result.

Tips:

• Make sure the input string uses the delimiter expected by the workflow.
• Verify that the Delimiter matches the input data format.
• Use Variables or Global variables when the string is determined dynamically.
• Use a clearly named Variable or Global variable for the split XML result.
• Keep the delimiter consistent when generating delimited strings in earlier workflow steps.
• Test strings containing empty values or consecutive delimiters if those cases are possible in your workflow.
• Test strings containing leading or trailing delimiters if those cases are possible.
• Test representative input data before deploying the workflow.
• Verify the resulting split XML during testing before building downstream processing around its structure.
• Do not assume a particular XML structure unless it has been confirmed in the target FlowWright environment.
• Test the step with delimiters that occur multiple times in the input.
• Consider the possibility that the delimiter may appear inside a value when choosing the input format.
• Use the True path for normal processing and the False path for error handling.
• Add logging or notification to the False path when split failures require investigation.
• Keep the input format consistent across workflow instances.
• If the input originates from an external system, validate the received format before splitting it.

Notes:

The Split String step is defined in the Engine category with the internal name splitstring, label “Splits a string using a delimiter”, and display name “Split String.”

The step is implemented by FlowWright.Workflow.SplitString in FlowWright.Workflow.dll and is defined as a Process step with 2 incoming connections and 2 outgoing connections.

The XML defines three configurable properties, and all three are required:

• stringVal – String to split
• delimiter – Delimiter
• valueVariable – Variable/Global to store the split XML 

All three properties use the standard string data type, implemented by FlowWright.DataTypes.ClsTextBox.

The step provides two predefined return values: False and True.

Definition Sample:

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

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

• String to split
• Delimiter
• Variable/Global mapping for the split XML
• Environment-specific Variable or Global configuration
• Downstream processing of the split result

The Classify AI documentation follows the same approach, instructing users to verify variable mappings and other environment-specific configurations after importing a definition.

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

Click here to download the sample file.