Anthology UAT / Property Mappings

Testing the Anthology integration typically happens in two phases:

• Element451 → Anthology
• Anthology → Element451

Element451 → Anthology testing is usually completed first, while the second, Anthology → Element451 will only happen if a partner has requested syncs to happen that direction (most partners are only Element451 → Anthology).

Both phases should begin after the Applications and Decisions modules have been configured and test records are available.

Triggering the Integration

During testing, integrations should be triggered manually. Once live, they can be automated.

For instructions, see How to Sync Records (Anthology).

Testing Element → Anthology#

Preparation#

Create test student records with applications. These should cover a wide range of scenarios used on your campus.

Note: These records should be removed before go-live as they are test records.

Testing#

Follow the steps in How to Sync Records (Anthology) to trigger a sync.

Review the Sync Result#

After each sync, check the Integration Log:

• If there are errors:
  • Attempt to resolve on your own.
  • If needed, reach out in Basecamp for assistance.
• If the record is successful:
  • Proceed to validate the data in Anthology

---

Validate Data in Anthology#

Once a record has synced successfully:

• Review the record in Anthology
• Compare values using the Field Mappings section.
• Validate:
  • Element451 fields (slugs)
  • Corresponding Anthology fields
  • (Please note that documents can also sync into Anthology. The specific documents types in Element that can sync, are governed by a hidden translation table that matches Element document types to Anthology document types)

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

---

Field Mappings#

Below is an overview of the Element451 fields (slugs) and corresponding Anthology API fields included in the standard integration.

Testing Anthology → Element#

Preparation#

Identify the records you want to test.

• If testing updates to existing Element records:
  • Use records previously synced from Element451 → Anthology
  • Make changes in Anthology (e.g., phone, address, race, etc.)
• If testing creation of new Anthology student records → new Element records:
  • Select a group of recent Anthology applicants
  • Note their name and Campus Nexus (Student) ID

We recommend testing at least 5–10 records to cover a variety of scenarios.

Request a Sync#

Notify Element staff via Basecamp with the records to be synced:

• If using previously synced records:
  • Provide a list of Element IDs
• If syncing new records from Anthology:
  • Provide Anthology names and Campus Nexus (Student) IDs

---

Review the Sync Result#

Element staff will notify you once the records have been processed.

After notification:

• Check the Integration Log for any errors
• Resolve any issues if needed

---

Validate Data in Element#

Once the sync is complete:

• Review the records in Element451
• Confirm that:
  • New records appear as expected, or
  • Updates made in Anthology are reflected correctly

Use the Field Mappings section to validate field-level accuracy.

---

Field Mappings#

Below is an overview of the Element451 fields (slugs) and corresponding Anthology API fields included in the standard integration.  Additional fields/properties can be set/read based on a partner’s SOW.