Table of Contents
PATH: Admin > Merge Settings
The Merge Settings dashboard in the Admin console has a "Saved States" tab, which allows you to save your merge settings and potentially align different merge settings to different scheduling phases.
Although you can have multiple saved states, only one can be enabled at any given time.
The enabled saved state will have its settings applied to both nightly and real-time merges.
Many schools with integrations enabled may automatically have a "default" saved state created (to learn more about your institution's saved state, review your Merge Settings in your Admin console or contact your Customer Success representative.
PATH: Admin > Merge Settings > Activity
Each saved state has its own version history.
To view the version history for a saved state, select it from the “Activity for Merge Settings Name” dropdown menu.
The activity tracker captures every control that is displayed on the merge settings screen except for the “realtime integration schedule”.
That means the following fields are captured via the activity tracker:
Conflict Handling Method
Steps to Execute
Editing Merge Settings
PATH: Admin > Merge Settings > Settings
When editing merge settings, make sure you are editing the intended saved state.
Select the intended state from the “Merge Settings Name” dropdown menu.
You can save changes to a saved state that is currently not enabled.
Executing a Manual Merge
PATH: Admin > Execute Merge
When executing a manual merge, you can have the settings default from one of the existing saved states.
Select the intended saved state from the “Perform integration using existing merge settings” dropdown menu.
Attaching Saved States to Phases
Saved states can be attached to specific Phases, which then change the integration settings used for specific terms.
To attach a particular saved state to a phase, click “Add integration save state” and then select it from the “Merge Settings Configuration” dropdown menu.
As each phase is applied to a term, setting a saved state to a phase only changes the settings for the term-specific merge endpoints (i.e. sections, courses, relationships). This will not affect the merge endpoints that are term-agnostic (i.e. instructors, rooms, buildings, etc.).
To learn more about Scheduling Phases, please see our Configuring and Managing Scheduling Phases article.