Skip to content

Create Template

Create a Template

Before You Begin

You must create a partner before you can create a template.

You can create a template in 3 ways:

  • Create from scratch
  • Copy a template
  • Import a template

Create from Scratch

To create a template:

  1. Click Templates in the left navigation pane.
  2. Click + Create New in the upper-right corner of the screen.

  3. Fill in the fields as needed. Required fields have an asterisk (*).

    Field Definitions
    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 Configuration

  1. Click Input File to expand it. The Input File Properties panel opens. Required fields have an asterisk (*).

    Input File Field Definitions
    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.

    The FeedXChange Template Configuration interface showing Input File Properties. The main panel displays options for file format (Fixed or Delimited), delimiter entry, quote string selection, and toggles for header, body, and footer presence. Optional fields enable entering regular expressions for header, body, and footer. The left sidebar contains a navigation tree with Template Properties, Input File, File Properties, Header, Body, and Response File. The top right shows last updated information, and the bottom left has a Delete Template button.
    Figure 1. Input file configuration

  2. If the file has a header, set Header to Yes.

    • Optionally, add a regular expression1 in the Header Regex field to enforce structure, delimiters, and character rules as needed.

  3. If the file has a body, set Body to Yes.

    • Optionally, add a regular expression1 in the Body Regex field to enforce structure, delimiters, and character rules as needed.

    Note

    It's unlikely that an input file won't have a body, but it commonly lacks a header or footer or both.

  4. If the file has a footer, set Footer to Yes.

    • Optionally, add a regular expression1 in the Footer Regex field to enforce structure, delimiters, and character rules as needed.

  5. Click the Header, Body, and Footer tabs as needed to set the field values. Required fields have an asterisk (*).

    Header Field Definitions
    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 Field Definitions
    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.
    Footer Field Definitions
    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.

    FeedXChange template editor showing a list of fields in the Body section. The Error Code field is highlighted and being dragged using a grip icon. Other fields such as ActivityId are visible above. The interface includes icons for copying and deleting fields, and a button labeled Add for inserting new fields.

    • To add a field, click + Add at the bottom of the list.
    • To configure a field, click the field to make it active. You can then edit the field properties in the detail pane.
    • To remove a field, click the delete icon ().
    • To copy a field, click the copy icon ().

    • To move a field up or down, drag and drop the field using the gray dot handle ().

      Important

      If the file's Format is Delimited, the order the fields appear in the list must match the order they appear in the input file.

  6. Click Save in the upper right corner.

Response File Configuration

  1. Click Response File to expand it. The Response File Properties panel opens.

    Response File Field Definitions
    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.

    FeedXChange Template Editor displaying the Response File Properties panel. The main section shows options for file format selection (Fixed or Delimited), a field to enter a delimiter, quote string choices (None, single, double), and toggles for generating header, body, and footer. The left sidebar contains a navigation tree with Template Properties, Input File, Response File, File Properties, and Body.
    Figure 2. Response file configuration

  2. If you want the generated file to have a header, set Header to Yes.

  3. If you want the generated file to have a body, set Body to Yes.

    Note

    It's unlikely that a response file won't have a body, but you might not want a header or footer.

  4. If you want the generated file to have a footer, set Footer to Yes.

  5. Click the Header, Body, and Footer tabs as needed to set the field values.

    Header Field Definitions
    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 Field Definitions
    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.
    Footer Field Definitions
    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.

    FeedXChange template editor showing the Body section with a list of fields. The Error Code field is highlighted and being dragged using a grip icon, while ActivityId appears above. Copy and delete icons are visible next to each field, and an Add button is below the list.

    • To add a field, click + Add at the bottom of the list.
    • To configure a field, click the field to make it active. You can then edit the field properties in the detail pane.
    • To remove a field, click the delete icon ().
    • To copy a field, click the copy icon ().

    • To move a field up or down, drag and drop the field using the gray dot handle ().

      Note

      If the file's Format is Delimited, the order the fields appear in the list is the order they'll appear in the response file.

  6. Click Save in the upper right corner.

Copy a Template

To copy a template:

  1. Click Templates in the left navigation pane.
  2. Find the template you want to copy:
    • Search by template name or description.
    • Filter templates by partner, RCX process, status, or the user who last updated the template.
  3. Click Copy () in the Actions column.
  4. Type the name of the new template.
  5. Click OK.
  6. Edit the template as needed.

Export a Template

You might find it helpful to export an existing template, change its parameter values in a text editor, and import the new template.

To export a template:

  1. Click Templates in the left navigation pane.
  2. Click Export () in the Actions column for the template you want to work with. The file is saved in JSON format to your default downloads directory.
  3. Change the values in the JSON file as needed.

Tip

To avoid overwriting the existing template when you import this file, change the data.name and templateName elements.

Import a Template

To import a template:

  1. Click Import in the upper right corner of the Templates list view. The Include Json File dialog box opens.
  2. Click the Include Json File field () and navigate to the JSON file you want to import.

  3. For the option Do you want to override existing template?:

    • override enabled: the existing template with the same name is overwritten with the imported JSON file contents.
    • override disabled: the import operation continues, but if the template name already exists, the import fails.

    To avoid overwriting an existing template, change the data.name and templateName elements in the exported JSON file before importing.

  4. Click Import. The import job begins.

  5. Click Import Status to view the results.
  6. Edit the template as needed.

Test a Template

Before you publish the template, it's a good practice to test it.

See also:

  1. For information about regular expressions, see About regular expressions and Regular expression tester ↩↩↩