Decline an Already Approved Registration Application

📖 User Story
As an Examiner or Manager,
I want to decline an application that has already been approved,
so that the Registration status is updated or the Registration is canceled, and the system accurately reflects the new status of the application and registration.

Context:
This user story handles scenarios where an Examiner needs to decline an application that was previously approved. In such cases, the story ensures that the system provides options for canceling or suspending the existing Registration and records the changes in both the application and registration statuses.

Note: The "Issue Certificate" functionality is out of scope for this story and will be addressed in a separate user story #21685

Note: Initial Approval or rejection of applications without existing registrations is handled in user story #22187. Note: Approve a Previously Declined Registration Application is handled in #23673 Note: Escalating to Registrar is handled in #23674

Declining an Application with an Existing Registration

Declining an Application with an Existing Registration:
If the application has already been approved and a corresponding registration entry has been created and recorded in the Registration table:
- When the Examiner clicks Decline, a modal dialog appears asking if they would like to:
- Cancel the registration.
- Suspend the registration.
- If the Examiner selects Cancel or Suspend, the system updates the status of the existing Registration accordingly in the Registration table.
- A record of this action, including the Registration status change, is logged in the Filing History.

📏 Business Rules

[ ] The system should validate if a Registration number already exists for the application before displaying the Decline options.
[ ] The system should prompt the Examiner with options to Cancel or Suspend the Registration if a previously approved application is declined.
[ ] Modal dialogs must require user confirmation before any decline actions, such as declining an application, canceling, or suspending an existing Registration.
[ ] The system must log every decision (status change, rejection) with a timestamp in the Filing History for audit purposes.
[ ] All status changes, including both application and registration statuses, must be recorded in the Filing History, including the Examiner’s name who made the change, the date, and the time.

🎭 Story Scenarios

Scenario 1: Decline an Already Approved Application and Cancel Registration
Given the Examiner is on the application details page, and the application status is "Approved":
When the Examiner clicks the "Decline" button:
Then a modal dialog appears asking if the Examiner would like to Cancel or Suspend the existing Registration.
And the Examiner selects Cancel.
Then the application status changes to "Declined."
And the existing Registration status changes to "Canceled."
And a record of the action is logged in the Filing History with the Examiner’s name, date, and time. And the application status is reflected and visible in the Examiner Dashboard

Scenario 2: Decline an Already Approved Application and Suspend Registration
Given the Examiner is on the application details page, and the application status is "Approved":
When the Examiner clicks the "Decline" button:
Then a modal dialog appears asking if the Examiner would like to Cancel or Suspend the existing Registration.
And the Examiner selects Suspend.
Then the application status changes to "Declined."
And the existing Registration status changes to "Suspended."
And a record of the action is logged in the Filing History with the Examiner’s name, date, and time. And the application status is reflected and visible in the Examiner Dashboard

bcgov / entity