Jadu CXM: Identify XFP Fields to Retain and Put Into CXM

To carry XFP data forward into subsequent forms, you need to identify what XFP data needs to be stored in CXM. The data from your XFP fields goes into a corresponding CXM field. These fields each have a data type associated with them. For more information, see the table defining each field type available in CXM.

• Step 1: Determining Which Field Data from your XFP Form Needs Storage in CXM
• Step 2: Reviewing Existing Fields Available in CXM for XFP Data Storage
• Step 3: Considerations Before Requesting New Fields from OIT
• Step 4: Complete the CXM Setup Request Form.

Determining Which Field Data from your XFP Form Needs Storage in CXM

Things to consider:

• If accessing the data in a subsequent form, store it in CXM for later use
• If the data exists in the form to help the submitter answer other questions, that field may not be necessary later in the process.

Example: A Yes/No question that conditionally shows another group of fields may not need to carry forward to the next form in the process; therefore the data doesn't need to send to CXM.

Reviewing Existing Fields Available in CXM for XFP Data Storage

Re-using your CXM fields across case types helps reduce the length of the field list when adding fields to the case type forms, making it easier to identify necessary fields.

There is a small subset of universal fields available to users. To see a list of these fields and their uses please visit: Global CXM Fields

Considerations Before Requesting New Fields from OIT

• Field Names are specific to a unit, with the exception of Global Fields.
• Field Name best practice: Keep field names simple so they can be re-used by multiple case types within your category. 
  •  For example: a form for requesting a new training course includes a Course Type question to indicate if the course should be in-person or online, and another form used to request a new position includes a Type of Hire question. A generic CXM field called Request Type may work well for both case types and re-used across your additional future case types. 
• Field Type: Field types do not always need to match between XFP and CXM. See the table below for best practice on which field type to ask for in CXM.
  

  XFP	CXM	Tips
  Date	Date	Required if the date is used in a CXM rule or if the date passes back to a date field in a subsequent form. Example: Sending a reminder email based on a date.
  Date	Text	Stores a date as static text.
  Dropdown	Text	The value or the label can pull into subsequent XFP forms and displayed in editable text fields or display fields.
  Integrated	{varies}	Each integrated component outputs a different data type. Base the CXM field type selection on this output.
  Text (or Display) Area	Text Area	Stores large amounts of text.
  Text (or Display) Field	Text	Stores small amounts of text.
  {varies}	Email	Required if the XFP text field contains an email used in a CXM rule. Example: Sending an email from CXM.
  {varies}	URL	Stores a URL that can create a hyperlink for use in a CXM email.

Completing the CXM Setup Request Form

After completing steps 1-3, you may request additional fields as necessary. To request new fields from OIT, fill out the CXM Setup Request Form.