Field Mapping: Attributes and Values List

Modified on Mon, 12 Feb 2024 at 09:47 AM

This article includes all details related to the field mapping of member attributes in the Engagement Rx system. Field mapping is required for portals assigned to authentication types of User Eligibility or SAML 2.0.

The table below includes the following:

System Name: The attribute field name used by the system

Data Type: How the data should be entered and the character limit, if applicable

Notes: Further explanation for the field, when necessary

A single * by the System Name indicates that it can be used as a validation field for User Eligibility (note that any field designated as a validation field is required)

A double ** by the System Name indicates that it is a required field for SAML 2.0

Beneath the table are lists of values for the following System Field Names:

Gender: A list of all acceptable values. (Note: Engagement Rx supports Gender Legacy data type—see the “Data Transformation” article for more details.)

System Name	DataType	Notes
Birthdate *	Date
CustomField1 *	VarChar(255)
CustomField2 *	VarChar(255)
CustomField3 *	VarChar(255)
CustomField4 *	VarChar(255)
CustomField5 *	VarChar(255)
Email *	VarChar(255)	Standard email address format
FirstName *	VarChar(45)
Gender	VarChar(255)	Can be mapped for Gender legacy
Key Field , *	VarChar(255)
LastName *	VarChar(45)
PortalGroup **	VarChar(50)
PortalGroupName **	VarChar(50)	Is only required for SAML if it is assigned for portal
PhoneNumber *	VarChar(255)	Must be unique; if duplicate, it will be logged as an error
CultureCode	VarChar(2)	The root culture code for the preferred language

Gender

The Engagement Rx system allows clients to use Gender Legacy data types for the Gender attribute. This is done by using the “Data Transformation” column in the field mapping tool. Accepted values are:

Male

Female

TransMale

TransFemale

GenderQueer

NonBinary