Display an alert prompting QS to submit the Transfer due to sale or gift to complete the transfer
- Dominant language
- JavaScript
- Stars
- 23
- Forks
- 62
- Avg merge
- 24m
- Merged PRs (30d)
- 1
Description
### Summary
An in‑product alert must be displayed after the executor/administrator transmission is submitted to prompt the Qualified Supplier to complete the subsequent Transfer to Beneficiary (sale or gift) in the same guided session. The alert must make clear that the estate transfer remains incomplete until the second transaction is filed and submitted. This approach aligns with the two‑step estate handling recognized under the Regulation (transfer includes transmission; transmission on death; verification statement on registration).
### The Ask from the Business
A mandatory prompt is required to reduce partially completed estate transfers, drive immediate continuation into the beneficiary transfer, and lower rejection/rework caused by incomplete packages.
### Business Rules
- Post‑Step‑1 alert: Upon successful submission of the transmission to executor/administrator (Step 1), an inline banner and modal prompt should be displayed, advising that the Transfer to Beneficiary (sale or gift) must be completed to finalize the estate transfer..
- Forced continuation path: The UI should route the filer directly into the Step‑2 flow from the alert. A “complete later” option should be suppressed for ToD, except where an explicit save‑and‑resume pattern already exists for session interruption..
- Single package submission: Both steps should be bundled into one submission package for one staff decision, while retaining two underlying transactions and fees..
- Legislative alignment message: Alert helper text should state that completion of the beneficiary transfer is required to effect ownership change and to enable issuance of a verification statement.
### Validation Rules
- Submission block: Submission to staff review should be blocked until the Step‑2 transfer has been drafted, required uploads and attestations have been provided, and payment lines for both transactions are present.
- Alert persistence: If the filer navigates away from Step‑2 prior to submission, the alert banner should persist on the filing overview and dashboard entry until both steps are complete.
- Clear call‑to‑action: The alert should include a single primary action (“Continue to Transfer to Beneficiary”) which deep‑links into Step‑2 at the first incomplete section.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.