Confirm and Submit an Intentional Duplicate Activity
After the Duplicate Warning Dialog is displayed, the user has the option to review the conflicting record and confirm that their submission is a separate, intentional activity — not a duplicate. This action dismisses the warning and proceeds with saving the candidate activity to the database. The system records that the user explicitly overrode the duplicate warning, which supports audit trail requirements. This is important for cases such as a peer mentor having two separate appointments with the same contact on the same day, or a coordinator knowingly re-entering a corrected version of an activity.
User Story
Acceptance Criteria
- Given the Duplicate Warning Dialog is visible, when the user selects the confirm/proceed action, then the activity is saved to the database and the user is returned to the success state of the registration flow
- Given the user confirms submission despite the duplicate warning, when the record is saved, then an audit marker indicating the user overrode a duplicate warning is stored with the activity
- Given the user confirms an intentional duplicate, when the activity is saved, then the existing conflicting record is not modified or deleted
- Given the user confirms submission, when the flow completes, then a success confirmation is displayed to the user
Business Value
A duplicate detection system that cannot be overridden would block legitimate submissions and create friction that undermines adoption. Providing an explicit override path, with an audit trail, balances data quality enforcement with operational flexibility — ensuring the system is a guard rail, not a barrier.