Testing the Ethos/Colleague integration typically happens in two phases:

• Element451 → Ethos/Colleague
• Ethos/Colleague → Element451

Element451 → Ethos/Colleague testing is usually completed first. This phase tends to take longer, as errors often originate in Colleague and require investigation and updates on the partner side.

Ethos/Colleague → Element451 testing is typically much faster, as there are fewer issues to resolve.

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 (Ethos).

Testing Element → Ethos/Colleague

Preparation

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

Note: These records will sync to your TEST SIS environment and should be removed before go-live.

Testing

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

Review the Sync Result

After each sync, check the Integration Log:

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