Skip to content

Template Details

Template Details

Templates List View

The Templates list view includes the following fields.

Name
The name for the template.
Description
The description of the template.
RCX Process
The RCX process selected for the template. A template must have one process.
Partner
The partner to which the template belongs. A template must have one partner.
Last Updated By
The user name of the person who last updated the template.
Status
The status of the template: Published or Revision.
Actions

Icons are enabled depending on the privileges of your role:

  • Copy (): Enables you to copy the template.
  • Edit (): Opens the template in edit mode.
  • Delete (): Deletes the template.
  • Export (): Exports the template in JSON format.

Integrations Section

The Integrations section includes the following fields for integrations that use the highlighted template.

Name
The name of the integration using the selected connection.
Description
The description of the integration using the selected connection.
Status

The status of the integration:

  • Paused: The published integration was paused. While paused, any scheduled integrations don't run. The integration can't be edited or deleted.
  • Publish Failed: The publish operation failed. The integration can be copied, edited, deleted or published.
  • Publish Pending: The publication operation is in progress. The integration can't be edited, deleted, or run, but it can be copied.
  • Published: The integration has been published and can be copied, run, or paused.
  • Revision: The integration can be copied, edited, deleted, or published.
Actions
Icons in the Actions column are enabled depending on the integration's
status and the privileges of your role:
  • Copy (): Enables you to copy the integration. 
- **Edit** (:fontawesome-solid-pen-to-square:): Opens the integration in edit mode.

- **Delete** (:material-trash-can:): Deletes the integration.

- **Publish** (:material-check-circle-outline:): Publishes the integration.

- **Run Once** (:material-play-circle-outline:): Runs the integration immediately.

- **Pause** (:material-pause-circle-outline:): Pauses the integration. Any

scheduled integration runs are paused until the integration is resumed.

- **Resume** (:material-clock-time-ten-outline:): Resumes a paused integration.

Scheduled runs continue normally.

- **Unpublish** (:material-cancel:): Unpublishes an integration so you can edit it.

- **Upload File** (:material-tray-arrow-up:): Enables you to upload an input

file to the storage location. You can then click **Run Once** to run the

integration on that file.

Template Details View

The Template Details view includes the following fields. Required fields have an asterisk (*).

Name *
The name for the template. Max length: 100 characters.
RCX Process *

FeedXChange supports the following types of processing within RCX:

Process Name Description
Activity Enables processing of bulk accruals (such as partner accrual feeds) and redemptions (such as point transfers or other expenditures coming from external sources)
Enrollments Enables processing bulk enrollments of new members with optional duplicate matching by combinations of fields
Member Segments Enables bulk assignment of segments to members based on external segmentation sources
Member Preferences Enables bulk setting of member preferences and member-level loyalty feature flags
LoyaltyID Enables adding the loyalty ID to the members.
Profile Update Enables updating member profile data

Note

Any process based on RCX member activity can autoenroll the member with only their loyalty id and receive profile updates as they become available.

Partner *
The partner to which the template belongs.
Description
An optional description of the template. Max length: 255 characters.

Input File Properties

Format *

Fixed or Delimited.

  • Fixed file: Uses a specific width for each field. Every record has the same length, and data is aligned in fixed positions. No delimiters are used.
  • Delimited file: Uses a specific character (like a comma, tab, or pipe) to separate fields. Field lengths can vary, and the delimiter indicates where each field starts and ends.
Delimiter *

Character to use as the field delimiter, such as a comma. Required if Format is Delimited.

Tip

To specify the tab character as the delimiter, use another application, such as Notepad or Word, to press the Tab key. Then, copy and paste the tab character into the Delimiter field.

Quote Strings
The character used to indicated quotes. Options are single quote ('), double quote ("), or none.
Header *
Indicates whether the file has a header row. If yes, the Header tab enables you to configure each column of the header row.
Header Regex
The optional regular expression used to identify and validate the entire header row to enforce structure, delimiters, and character rules as needed.
Body *
Indicates whether the file has one or more body rows. If yes, the Body tab enables you to configure each column of the body rows.
Body Regex
The optional regular expression used to identify and validate the body rows to enforce structure, delimiters, and character rules as needed.
Footer *
Indicates whether the file has a footer row. If yes, the Footer tab enables you to configure each column of the footer row.
Footer Regex
The optional regular expression used to identify and validate the entire footer row to enforce structure, delimiters, and character rules as needed.

This tab is visible if Header is Yes in the Input File Properties. For each column in the file's header row, specify the following properties:

Field Name *
The name of the header column. Must be unique within the Header. Max length: 50 characters.
Fixed Length *
For files whose Format is Fixed, the number of characters expected in the field. This value informs FeedXChange where one field ends and the next begins. Refer to Input File Properties.
Data Type *
The data type of the header field. For headers, this is often a string. Options are: Boolean, Date, Number, or String.
Format
An optional regular expression to validate the header text when the data type is string.
Date Format *

The format for a date field.

Date Format Options
  • YYYY-MM-DD HH:mm:ss.SSS (such as 2025-01-31 08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS (such as 2025-01-31T08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS±HH:mm (such as 2025-01-31T08:30:00.250±12:30)
  • YYYY-MM-DDTHH:mm:ss.SSS±HHmm (such as 2025-01-31T08:30:00.250±1230)
  • YYYY-MM-DDTHH:mm:ss.SSSZ (such as 2025-01-31T08:30:00.250Z)
Date Format Variables

To see this list of variables in FeedXChange, click the ⓘ icon.

  • DD - Numeric day of the month (ex. 01, 02, 03, 04)
  • dd - Abbreviated day of the week (ex. Mon, Tue, Wed)
  • EEEEE - Day of the week (ex. Monday, Tuesday, Wednesday)
  • HH - Hour, 2 digits in 24 hour clock (ex. 01, 02, 03)
  • hh - Hour, 2 digits in 12 hour clock (ex. 01, 02, 03)
  • MMM - Abbreviated month (ex. Jan, Feb, Mar)
  • MMMMM - Month (ex. January, February, March )
  • MM - Numeric month(ex. 01,02,03,04)
  • mm - Abbreviated minutes (ex. 01, 02, 03)
  • SS - Second, 2 digits in 24 hours (ex. 01, 02, 03)
  • ss - Second, 2 digits in 12 hours (ex. 01, 02, 03)
  • a - Meridiem indicator (ex. AM, PM)
  • YYYY - Week year, or the year the week falls into (ex. 2023,2024,2025)
  • yyyy - Calendar year (ex. 2023, 2024, 2025)
Number of decimals *
For number fields, indicate the number of decimal places.
Required *

Indicates whether to require the header field in the header row for each file.

Example

For a header row in which the Date field is required but other fields aren't:

A text editor displaying a sample delimited data file for FeedXChange. The file contains a header row with the column name Date followed by several commas, and body rows with date-time values, test IDs, long numeric values, POS, and AddPoints fields. The environment is a dark-themed editor with torn edges at the top and bottom, suggesting a cropped view.
Figure 1. This test file is OK

A dark-themed text editor displays a sample delimited data file for FeedXChange. The primary subject is a body row containing date-time values, test IDs, long numeric values, POS, and AddPoints fields. The file lacks the Date field in the header row, which is required for correct configuration.
Figure 2. This test file results in an error

Default value
The optional default value for the header field. For headers, this is often omitted.
Minimum Length *
The minimum length (in characters) of the header field.
Maximum Length *
The maximum length (in characters) of the header field.
Comments
Any comment that might help users working with the template.

Body

This tab is visible if Body is Yes in the Input File Properties. The properties for the fields in the body of the input file vary depending on the field's data type. For example, strings have a minimum and maximum length, and numbers have a minimum and maximum value. For properties marked with an asterisk, you must supply a value.

Field Name *
The name of the field. Must be unique within the Body. Max length: 50 characters.
Fixed Length *
For files whose Format is Fixed, the number of characters expected in the field. This value informs FeedXChange where one field ends and the next begins. Refer to Input File Properties.
Fixed Array Length *
The number of elements to be parsed from the file. Refer to Configure Array Fields.
RCX Field
The name of the field in ReactorCX that the Field Name maps to. If not provided, the field data isn't imported into RCX.
Data Type *
The data type of the field. Options are:
  • Boolean
  • Date
  • Number
  • String
Format
An optional regular expression to validate the field value in the file when the data type is string.
Date Format *

The format for a date field.

Date Format Options
  • YYYY-MM-DD HH:mm:ss.SSS (such as 2025-01-31 08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS (such as 2025-01-31T08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS±HH:mm (such as 2025-01-31T08:30:00.250±12:30)
  • YYYY-MM-DDTHH:mm:ss.SSS±HHmm (such as 2025-01-31T08:30:00.250±1230)
  • YYYY-MM-DDTHH:mm:ss.SSSZ (such as 2025-01-31T08:30:00.250Z)
Date Format Variables

To see this list of variables in FeedXChange, click the ⓘ icon.

  • DD - Numeric day of the month (ex. 01, 02, 03, 04)
  • dd - Abbreviated day of the week (ex. Mon, Tue, Wed)
  • EEEEE - Day of the week (ex. Monday, Tuesday, Wednesday)
  • HH - Hour, 2 digits in 24 hour clock (ex. 01, 02, 03)
  • hh - Hour, 2 digits in 12 hour clock (ex. 01, 02, 03)
  • MMM - Abbreviated month (ex. Jan, Feb, Mar)
  • MMMMM - Month (ex. January, February, March )
  • MM - Numeric month(ex. 01,02,03,04)
  • mm - Abbreviated minutes (ex. 01, 02, 03)
  • SS - Second, 2 digits in 24 hours (ex. 01, 02, 03)
  • ss - Second, 2 digits in 12 hours (ex. 01, 02, 03)
  • a - Meridiem indicator (ex. AM, PM)
  • YYYY - Week year, or the year the week falls into (ex. 2023,2024,2025)
  • yyyy - Calendar year (ex. 2023, 2024, 2025)
Number of decimals *
For number fields, indicate the number of decimal places.
Required *
Indicates whether the field is required.
From File *
Indicates whether the data for a field is coming from the input file.
Default Value
The default value for the field, if any. If From File is No, the Default Value can't be empty.
Minimum Length *
For strings, the minimum length of the field. This must be less than or equal to the Maximum Length value.
Maximum Length *

For strings, the maximum length of the field. This must be greater than or equal to the Minimum Length value. If the input file format is Fixed, this must be less than or equal to the Fixed Length value.

Note

For Fixed file formats, after trimming spaces, the value is validated against the configured minimum and maximum length.

Minimum Value *
For numbers, the minimum value of the field.
Maximum Value *
For numbers, the maximum value of the field.
Editable *
Not yet implemented.
Auto-Fixable *
Not yet implemented.
UUID *
For string fields, indicates whether this item is a Universally Unique Identifier (UUID).
SysDate
For date fields left blank in the input file, FeedXChange can use the system date while processing the file. The system date is the current date in UTC.
Unique Key Flag *
Not yet implemented.
Transform
Optionally specifies a transform function to be used on that field. The options available depend on the selected Data Type. Refer to Configure Transforms.
Transform Expression
A custom expression or formula to apply transformations to the field value.
Comments
Further description of the field and any additional information.

This tab is visible if Footer is Yes in the Input File Properties. For each column in the file's footer row, specify the following properties:

Field Name *
The name of the footer column. Must be unique within the footer. Max length: 50 characters.
Fixed Length *
For files whose Format is Fixed, the number of characters expected in the field. This value informs FeedXChange where one field ends and the next begins. Refer to Input File Properties.
Data Type *
The data type of the footer field. Options are:
  • Boolean
  • Date
  • Number
  • String
Format
An optional regular expression to validate the footer text when the data type is string.
Date Format *

The format for a date field.

Date Format Options
  • YYYY-MM-DD HH:mm:ss.SSS (such as 2025-01-31 08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS (such as 2025-01-31T08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS±HH:mm (such as 2025-01-31T08:30:00.250±12:30)
  • YYYY-MM-DDTHH:mm:ss.SSS±HHmm (such as 2025-01-31T08:30:00.250±1230)
  • YYYY-MM-DDTHH:mm:ss.SSSZ (such as 2025-01-31T08:30:00.250Z)
Date Format Variables

To see this list of variables in FeedXChange, click the ⓘ icon.

  • DD - Numeric day of the month (ex. 01, 02, 03, 04)
  • dd - Abbreviated day of the week (ex. Mon, Tue, Wed)
  • EEEEE - Day of the week (ex. Monday, Tuesday, Wednesday)
  • HH - Hour, 2 digits in 24 hour clock (ex. 01, 02, 03)
  • hh - Hour, 2 digits in 12 hour clock (ex. 01, 02, 03)
  • MMM - Abbreviated month (ex. Jan, Feb, Mar)
  • MMMMM - Month (ex. January, February, March )
  • MM - Numeric month(ex. 01,02,03,04)
  • mm - Abbreviated minutes (ex. 01, 02, 03)
  • SS - Second, 2 digits in 24 hours (ex. 01, 02, 03)
  • ss - Second, 2 digits in 12 hours (ex. 01, 02, 03)
  • a - Meridiem indicator (ex. AM, PM)
  • YYYY - Week year, or the year the week falls into (ex. 2023,2024,2025)
  • yyyy - Calendar year (ex. 2023, 2024, 2025)
Number of decimals *
For number fields, indicate the number of decimal places.
Required *
Indicates whether the field is required in the footer for each file.
Default value
The default value for the footer field.
Minimum Length *
The minimum length (in characters) of the footer field.
Maximum Length *
The maximum length (in characters) of the footer field.
Comments
Any comment that might help users working with the template.

Response File Properties

Properties for the response file that FeedXChange generates after an integration run and uploads to the source system.

Format

Fixed or Delimited.

  • Fixed file: Uses a consistent width for each field. Every record has the same length, and data is aligned in fixed positions. No delimiters are used.
  • Delimited file: Uses a specific character (like a comma, tab, or pipe) to separate fields. Field lengths can vary, and the delimiter indicates where each field starts and ends.
Delimiter

Character to use as the field delimiter, such as a comma. Required if Format is Delimited.

Tip

To specify the tab character as the delimiter, use another application, such as Notepad or Word, to press the Tab key. Then, copy and paste the tab character into the Delimiter field.

Quote Strings
The character used to indicated quotes.
Generate Header
Indicates whether FeedXChange generates the response file with a header row. If yes, the Header tab enables you to specify the format for each column of the header row.
Generate Body
Indicates whether FeedXChange generates the response file with one or more body rows, usually Yes. If yes, the Body tab enables you to specify the format for each column of the body rows.
Generate Footer
Indicates whether FeedXChange generates the response file with a footer row. If yes, the Footer tab enables you to identify the format for each column of the footer row.

Header

The header row fields identify the column names and must contain the same number of fields that are present in the Body.

Field Name
The name of the header column.
Data Type
The data type of the header field. Options are:
  • Boolean
  • Date
  • Number
  • String
For header rows, this is typically String.
Date Format *

The format for a date field.

Date Format Options
  • YYYY-MM-DD HH:mm:ss.SSS (such as 2025-01-31 08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS (such as 2025-01-31T08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS±HH:mm (such as 2025-01-31T08:30:00.250±12:30)
  • YYYY-MM-DDTHH:mm:ss.SSS±HHmm (such as 2025-01-31T08:30:00.250±1230)
  • YYYY-MM-DDTHH:mm:ss.SSSZ (such as 2025-01-31T08:30:00.250Z)
Date Format Variables

To see this list of variables in FeedXChange, click the ⓘ icon.

  • DD - Numeric day of the month (ex. 01, 02, 03, 04)
  • dd - Abbreviated day of the week (ex. Mon, Tue, Wed)
  • EEEEE - Day of the week (ex. Monday, Tuesday, Wednesday)
  • HH - Hour, 2 digits in 24 hour clock (ex. 01, 02, 03)
  • hh - Hour, 2 digits in 12 hour clock (ex. 01, 02, 03)
  • MMM - Abbreviated month (ex. Jan, Feb, Mar)
  • MMMMM - Month (ex. January, February, March )
  • MM - Numeric month(ex. 01,02,03,04)
  • mm - Abbreviated minutes (ex. 01, 02, 03)
  • SS - Second, 2 digits in 24 hours (ex. 01, 02, 03)
  • ss - Second, 2 digits in 12 hours (ex. 01, 02, 03)
  • a - Meridiem indicator (ex. AM, PM)
  • YYYY - Week year, or the year the week falls into (ex. 2023,2024,2025)
  • yyyy - Calendar year (ex. 2023, 2024, 2025)
Number of decimals *
For number fields, indicate the number of decimal places.
Value
The value for the field. Options are:
  • Constant
  • Error Code
  • Error Message
  • HTTP Status
  • Row Number
Other values are available, depending on the template's RCX Process.

Body

The properties for the fields in the body of the response file vary depending on the field's Data Type. You can customize the fields as needed.

Field Name
The name of the field.
Data Type
The data type of the field. Options are:
  • Boolean
  • Date
  • Number
  • String
Date Format *

The format for a date field.

Date Format Options
  • YYYY-MM-DD HH:mm:ss.SSS (such as 2025-01-31 08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS (such as 2025-01-31T08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS±HH:mm (such as 2025-01-31T08:30:00.250±12:30)
  • YYYY-MM-DDTHH:mm:ss.SSS±HHmm (such as 2025-01-31T08:30:00.250±1230)
  • YYYY-MM-DDTHH:mm:ss.SSSZ (such as 2025-01-31T08:30:00.250Z)
Date Format Variables

To see this list of variables in FeedXChange, click the ⓘ icon.

  • DD - Numeric day of the month (ex. 01, 02, 03, 04)
  • dd - Abbreviated day of the week (ex. Mon, Tue, Wed)
  • EEEEE - Day of the week (ex. Monday, Tuesday, Wednesday)
  • HH - Hour, 2 digits in 24 hour clock (ex. 01, 02, 03)
  • hh - Hour, 2 digits in 12 hour clock (ex. 01, 02, 03)
  • MMM - Abbreviated month (ex. Jan, Feb, Mar)
  • MMMMM - Month (ex. January, February, March )
  • MM - Numeric month(ex. 01,02,03,04)
  • mm - Abbreviated minutes (ex. 01, 02, 03)
  • SS - Second, 2 digits in 24 hours (ex. 01, 02, 03)
  • ss - Second, 2 digits in 12 hours (ex. 01, 02, 03)
  • a - Meridiem indicator (ex. AM, PM)
  • YYYY - Week year, or the year the week falls into (ex. 2023,2024,2025)
  • yyyy - Calendar year (ex. 2023, 2024, 2025)
Number of decimals *
For number fields, indicate the number of decimal places.
Value
The value for the field.
Transform
Specifies a transform function to be used on the Value before output. Refer to Configure Transforms.

The footer row must contain the same number of columns present in the body.

Field Name *
The name of the footer field.
Data Type *
The data type of the footer field. Options are:
  • Boolean
  • Date
  • Number
  • String
This is typically String, but if you select an Aggregate option, the data type is often a Number.
Date Format *

The format for a date field.

Date Format Options
  • YYYY-MM-DD HH:mm:ss.SSS (such as 2025-01-31 08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS (such as 2025-01-31T08:30:00.250)
  • YYYY-MM-DDTHH:mm:ss.SSS±HH:mm (such as 2025-01-31T08:30:00.250±12:30)
  • YYYY-MM-DDTHH:mm:ss.SSS±HHmm (such as 2025-01-31T08:30:00.250±1230)
  • YYYY-MM-DDTHH:mm:ss.SSSZ (such as 2025-01-31T08:30:00.250Z)
Date Format Variables

To see this list of variables in FeedXChange, click the ⓘ icon.

  • DD - Numeric day of the month (ex. 01, 02, 03, 04)
  • dd - Abbreviated day of the week (ex. Mon, Tue, Wed)
  • EEEEE - Day of the week (ex. Monday, Tuesday, Wednesday)
  • HH - Hour, 2 digits in 24 hour clock (ex. 01, 02, 03)
  • hh - Hour, 2 digits in 12 hour clock (ex. 01, 02, 03)
  • MMM - Abbreviated month (ex. Jan, Feb, Mar)
  • MMMMM - Month (ex. January, February, March )
  • MM - Numeric month(ex. 01,02,03,04)
  • mm - Abbreviated minutes (ex. 01, 02, 03)
  • SS - Second, 2 digits in 24 hours (ex. 01, 02, 03)
  • ss - Second, 2 digits in 12 hours (ex. 01, 02, 03)
  • a - Meridiem indicator (ex. AM, PM)
  • YYYY - Week year, or the year the week falls into (ex. 2023,2024,2025)
  • yyyy - Calendar year (ex. 2023, 2024, 2025)
Number of decimals *
For number fields, indicate the number of decimal places.
Value *
A value from the entity that was processed (such as an ActivityId) or a constant that you specify. Options vary by RCX process, but the following are available for all:
  • Constant
  • Error Code
  • Error Message
  • HTTP Status
  • Row Number
Constant *
When the Value field is Constant, type the constant value.
Aggregate *
Not yet implemented.

See also: