Overrides: Correct, Enrich, Suppress

Sometimes the data from the source system is not quite right -- or not quite enough. The Safety Gate lets you apply manual overrides to individual changes before they reach your target system. You have three override types, each designed for a specific situation.

The Three Override Types

| Override | Purpose | Example | |---|---|---| | Correct | Fix a wrong value before it syncs | Source shows department as "Eng" but your target uses "Engineering" | | Enrich | Add data the source does not provide | Attach a cost center code that only exists in your planning model | | Suppress | Block a specific change from syncing | A termination record arrived early and should not sync until next month |

Applying an Override

1. Find the change in the review queue

   Use the queue filters or search to locate the specific change you want to override.

2. Click the Override button

   On the change detail view, click Override to open the override panel.

3. Select the override type

   Choose Correct, Enrich, or Suppress. Each type presents a different editing interface.

4. Make your changes

   For Correct: Edit the field value that needs fixing. You see the original source value, your corrected value, and a preview of what will sync.

   For Enrich: Add new field values that are not present in the source data. You select from the target system's available fields.

   For Suppress: Confirm that this change should be blocked. You can add a reason note that is stored in the audit trail.

5. Save and approve

   Save the override. For Correct and Enrich, the modified change is marked as approved and moves to the Load stage. For Suppress, the change is blocked and will not sync.

Correct: Fixing Source Data

Use Correct when the source system has a value that is technically wrong or does not match your target system's conventions.

Common scenarios:

• Naming mismatches -- The source uses abbreviations ("Mktg") but the target requires full names ("Marketing")
• Data entry errors -- An employee's start date is clearly wrong (e.g., year 1900)
• Stale values -- The source has not been updated yet, but you know the correct value

When you apply a Correct override, the original source value is preserved in the audit trail alongside your corrected value. The target system receives only the corrected value.

Enrich: Adding Missing Data

Use Enrich when the source system does not have a field that your target system requires or benefits from.

Common scenarios:

• Planning-only dimensions -- Cost center codes, planning scenarios, or custom attributes that exist only in your EPM tool
• Cross-system references -- Linking a Workday employee record to a project code from a separate system
• Manual classifications -- Tagging a GL account with a reporting category that the ERP does not track

Enriched fields are added to the change payload before it reaches the target system. The source data remains untouched.

Suppress: Blocking a Change

Use Suppress when a change is real but should not sync right now (or ever).

Common scenarios:

• Timing issues -- A termination is effective next month, but the record appeared early in the source system
• Test data -- A test employee or test transaction leaked into production data
• Contested changes -- The change is under dispute and needs resolution before syncing

When you suppress a change, it does not reach the target system. The suppressed change is logged with your reason note.

Override Persistence

Overrides can be one-time or recurring:

• One-time (default) -- The override applies to this specific change in this specific sync run. If the same situation arises in the next sync, you must override again.
• Recurring -- The override applies every time this row key appears in future syncs with the same condition. Recurring overrides are useful for systematic corrections that cannot be handled by transform rules.

You manage recurring overrides in Safety Gate > Recurring Overrides. Each recurring override shows the row key, override type, applied values, and the number of times it has fired.

Audit Trail

Every override is fully auditable. The Safety Gate history records:

• Who applied the override (user name and email)
• When the override was applied
• What type of override (Correct, Enrich, or Suppress)
• The original value from the source system
• The overridden value that was sent to the target (or "Suppressed" for suppress overrides)
• The reason note if one was provided

Auditors can filter the Safety Gate history by override type to review all manual interventions across any time range.