CFNC UAT / Field Mappings

To test the CFNC integration, you will need to work with your integration specialist to have them bring in records from CFNC for you to review.  Once live, the integration happens on a schedule, but for testing, it must be done manually.

Because CFNC is used by both four year institutions and community colleges, the exact fields that are mapped can vary.  The mapping below is for Community Colleges, but a four year institution will be similiar for the common fields and we can work with you to bring in other non-common ones.

Additionally, for community college schools, there are typically several different types of applications (Traditional Undergraduate, CCP, CIHS, etc).  Testing should happen for each group of records you intend to bring over into Element.  We recommend fully testing one type of application before moving onto the next type of applications.  Work with your integration specialists to make sure all use cases are covered.

---

CFNC→Element#

Preparation#

We recommend finding a listing of 5-10 records in CFNC that have a variety of data on them to best represent the different types of scenarios you may get (for example, domestic vs. international, different programs, etc).  For each record you want to have synced over to Element, you will need to note the student’s name and their UserApplication number.  You should provide the listing to your integration specialist using the following format:

• {Student’s Name} | UserApplication/#######-A

---

Requesting a Sync#

Once you have the listing of records that should be synced into Element (and in the correct format), notify your integration specialist and provide the listing to them.  They will work to import the applications into Element for you (this includes the application data and the preview PDF of the application).  Transcripts are typically not imported as a part of testing, but can be done if requested.

Reviewing the Sync Result#

After each sync, check the Integration Log:

• If there are errors:
  • Review Integration Errors - Troubleshooting (CFNC)
  • If needed, reach out in Basecamp for assistance.
• If the record is successful:
  • Proceed to validate the data in Element

---

Validate Data in Element#

Once a record has synced successfully:

• Review the record in Element
• Compare values using the Field Mappings section
• Validate:
  • CFNC fields
  • Corresponding Element451 fields (slugs)

The Field Mappings reflect the standard integration configuration for our community colleges. If your implementation includes additional customizations, use this as a baseline and add any additional validation checks as needed.

---

Community College CFNC → Element Field Mappings#

---

Validating Data in Colleague#

Below you can find the mapping of the Element fields above and where they should be going in Colleague.  Please note this should be reviewed in conjunction with the field mappings/UAT from the Colleague integration: Colleague UAT / Field Mappings

Community College Element → Colleague Field Mappings#