Description:

The ExcelOrTxtToXML workflow step converts an Excel or text file into an XML file.

The step supports:

• Providing the path to an Excel or text file.
• Specifying whether the first row of the source file is a header.
• Storing the generated XML file path in a Variable or Global variable.
• Using the generated XML file in subsequent workflow activities.
• Converting file-based data into an XML representation for downstream processing.
• Returning a True or False result for subsequent workflow processing.

This step converts content from Excel (.XLS, .XLSX, .CSV) or Text (.TXT) files into an XML file.

Usage:

The ExcelOrTxtToXML step is typically placed after a workflow has obtained or generated an Excel or text file that needs to be converted into XML.

The workflow supplies the source file path, configures whether the first row contains headers, and specifies the Variable or Global that will store the resulting XML file path.

A typical workflow pattern is:

Get/Create Excel or Text File → ExcelOrTxtToXML → Process XML

The generated XML file can then be used by later workflow activities to:

• Process structured data.
• Transform or analyze the converted data.
• Pass the XML file to another workflow activity.
• Prepare data for integration.
• Store or archive the converted file.
• Perform additional file processing.
• Use the XML as an intermediate representation.

Typical Workflow Suggestions:

Convert an Excel File to XML

Use this step when an Excel file needs to be converted into an XML file for subsequent workflow processing.

Example:

Get Excel File → ExcelOrTxtToXML → Process XML

The source Excel file path is supplied to the step, and the resulting XML file path is stored for subsequent use.

Convert a Text File to XML

Use the step to convert a text file into XML as part of a file-processing workflow.

Example:

Get Text File → ExcelOrTxtToXML → Process XML

The resulting XML file can then be passed to subsequent workflow activities.

Process a File with a Header Row

Enable the First Row is Header property when the source file's first row represents column/header information.

Example:

Receive Data File → ExcelOrTxtToXML → XML Processing

The XML defines this option as a checkbox property named isFirstRowHeader.

Note: The XML confirms the existence of the header option but does not document exactly how header values are represented in the resulting XML. Verify the generated XML structure with representative input files.

Convert Imported Data Before Integration

Use the step as a preparation activity before passing file data to another integration process.

Example:

Receive File → ExcelOrTxtToXML → Transform XML → External Integration

This pattern can be useful when a downstream activity expects data in XML form.

Prepare XML for Data Transformation

Use ExcelOrTxtToXML as an intermediate file-conversion step.

Example:

Source File → ExcelOrTxtToXML → XML Transformation → Output

The generated XML file path can be stored in a Variable or Global and supplied to the next processing activity.

Convert Files Received from an External System

Use the step after receiving a file from an external system.

Example:

Receive File → ExcelOrTxtToXML → Validate/Process XML → Complete

This can provide a common XML-based representation for subsequent workflow processing.

Convert a Batch Input File

Use ExcelOrTxtToXML when a workflow receives a batch file containing multiple records.

Example:

Get Batch File → ExcelOrTxtToXML → Process Records

Subsequent activities can then use the XML file to process the converted data.

The XML definition confirms file conversion and output-path storage, but it does not define record-looping or batch-processing behavior within this step itself.

Store the Generated XML Path for Reuse

Use the required xmlFilePath property to make the generated XML file location available to subsequent workflow activities.

Example:

ExcelOrTxtToXML → Store XML Path → Multiple Subsequent Steps

The step explicitly provides a Variable/Global destination for the generated XML file path.

Archive the Converted XML

Use the generated XML file as an intermediate artifact before archiving it.

Example:

ExcelOrTxtToXML → Validate XML → Archive XML

The workflow can use the stored XML file path in subsequent file-management activities.

Prepare XML for External Processing

Use the step when another application or workflow activity requires the converted data in XML file form.

Example:

Get Source File → ExcelOrTxtToXML → External Processing

The generated XML path can be supplied to the downstream activity.

Handle Conversion Failures

Connect the False return path to an appropriate error-handling activity.

Example:

ExcelOrTxtToXML

True → Continue Processing

False → Log Error → Notify Administrator

This allows the workflow to distinguish between successful and unsuccessful file conversion.

Process Files with Different Header Configurations

The optional First Row is Header setting allows the workflow configuration to account for source files that do or do not contain header information.

Example:

Receive File → Determine File Format → ExcelOrTxtToXML → Process XML

Configure the checkbox according to the expected source-file structure.

The XML does not define automatic header detection; it exposes a configurable checkbox property.

Example:

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

• Create a new process definition named “ExcelOrTxtToXMLDef” and open it in designer mode. 
• Drag an “ExcelOrTxtToXML” step to the canvas.
• Connect the dots between the “Start” step and “ExcelOrTxtToXML” 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.
• Configure a variable or a global to store the result after execution.
• Click the "ExcelOrTxtToXML" step to configure its "Required" properties. Provide a name for the step. Provide a variable or global reference to the file path of the application server's XLS or TXT file. Provide a variable or global reference to store the XML file path. 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 "ExcelOrTxtToXML" step to configure its "Optional" properties, then click the Save button. 

• 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 and click the process step to view its properties. When the workflow reaches the ExcelOrTxtToXML step, FlowWright uses the configured source file path and header setting to perform the conversion. The generated XML file path is stored in the configured Variable or Global. The workflow then follows the True or False return path according to the operation result.

Tips:

• Verify that the source Excel or text file exists before the step executes.
• Verify that the configured source file path points to the intended file.
• Use a meaningful Variable or Global name for the source file path.
• Use a meaningful Variable or Global name for the generated XML file path.
• Enable First Row is Header only when the first row represents header information.
• Test the workflow with representative Excel files.
• Test the workflow with representative text files.
• Test files both with and without header rows where applicable.
• Verify the generated XML after conversion.
• Confirm that the generated XML contains the expected data.
• Verify that downstream activities reference the correct XML file path.
• Test the workflow with empty or incomplete source files.
• Test the False return path for conversion failures.
• Connect the False path to appropriate error handling when conversion is required for downstream processing.
• Log source and output paths when file traceability is important.
• Verify that the generated XML file is accessible before passing it to another activity.
• Avoid moving or deleting the generated XML before downstream activities have finished using it.
• Test the workflow after changes to the source-file structure.
• Keep source-file formats consistent when the workflow expects a specific structure.
• Do not assume that all Excel formats, worksheets, delimiters, encodings, or text-file structures are supported unless confirmed by the FlowWright implementation.
• Do not assume a particular XML schema or element naming convention without examining generated output.
• Do not assume automatic header detection; the XML defines an explicit header checkbox. 
• Verify the generated XML against representative source data before using it in an external integration.
• Test both the True and False workflow paths independently.

Definition Sample:

You may download the sample definition from the link provided and later import it 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:

• Source Excel or text file path.
• First Row is the header setting.
• XML output path: Variable or Global.
• Workflow Variable references.
• Environment-specific settings.
• Downstream True and False workflow paths.
• Error-handling configuration.

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

Click here to download the sample file.

You may also use the “ExcelOrTxtToXML” process step to loop through all the values in the XML file as shown below. 

Click here to download this sample file.