Text Transform

The 'Scope' property determines the level of data to export from each Batch Folder.

• If set to a Data Model, one record is generated for the entire document.
• If set to a Data Section, one record is generated for each section instance.
• If set to a Data Table, one record is generated for each row.

The selected scope controls how many records are written and which data fields are available for use in the 'Record', 'Header', and 'Footer' properties.

> Tip: Choose a scope that matches the structure of your data and the requirements of your export format.

The 'Filename' property sets the name of the output text file created by the Text Transform activity.
You may use a static filename (e.g., export.txt) or include expressions to generate dynamic filenames based on batch or folder data.

> Example:
$"{Document_Number}.txt"
This will create a separate file for each document, using the value of the 'Document Number' field.

Ensure the filename is valid for your operating system and does not contain prohibited characters.

The 'Header' property allows you to specify content that will appear at the very beginning of the output file, before any data records. This is useful for including column headings, file metadata, or other introductory information.

You may use expressions and field references to dynamically generate header content.

> Example:
"Service Date|Revenue Code|Description|Quantity|Amount"

If left blank, no header will be included.

The 'Record' property is the core template for each exported record.
Use string interpolation and field references to define the layout and formatting of each line.

> Example:
$"{Service_Date:d}|{Revenue_Code:0000}|{Description}|{Quantity}|{Amount:N2}"

This will generate a pipe-delimited record with formatted values for each field.

You can use any valid C# string interpolation syntax, including formatting specifiers and expressions.

For more information on string interpolation, see the Microsoft documentation.

The 'Footer' property allows you to append content at the end of the output file, after all data records have been written. This can be used for file summaries, totals, or closing markers.

You may use expressions and field references to generate dynamic footer content.

If left blank, no footer will be included.

The 'Record Delimiter' property controls how individual records are separated in the output file. By default, this is set to a carriage return and line feed (\r\n), producing a standard line-based text file.

You may specify any string as the delimiter, including custom characters or control sequences.

> Example:
"," (comma)
"|" (pipe)
"\n" (line feed only)

Use escape sequences (e.g., \r, \n, \t) as needed for your format.

A combination of the following flags:

The Error Disposition property determines the system's response to errors that occur while executing the activity.

• Flag: The affected Batch Folder or Batch Page will be flagged for review.
• Log: The error will be written to the Grooper event log.
• Stop: Processing will halt, the Batch will be set to an error state, and all pending tasks will be deleted.

You can combine multiple options using the IssueDisposition flags.
Adjust this property to match your organization's error handling and escalation policies.

If the number of consecutive errors reaches this value, a critical stop will occur and the Activity Processing service will halt further processing.

• Use this property to prevent runaway failures and to ensure that persistent errors are escalated for review.
• Set to a higher value to allow more retries before stopping, or to a lower value for stricter error control.

Can be one of the following values:

The Concurrency Mode property determines whether the activity can be executed in parallel across multiple Batch Objects, or if it must run sequentially.

• This setting affects which Processing Queue the activity is submitted to and how tasks are distributed.
• Choose the appropriate mode based on the activity's thread safety and resource requirements.