BA - Does modern need the ability to suppress outputs

In legacy there are various cases where the business area asks that outputs are suppressed. Examples are below. Work is required to determine if

**1. Incorrect Information that Requires Updating** In a recent example a reinstatement was filed with errors. Staff requested the Certificate of Reinstatement is suppressed to allow for them to update the errors (in recent case this included name and jurisdiction). Jira 269937

**2. Certificate Formatting Issues** In a recent example a certificate was formatted where the seal overlaid text. Jira 241195

**3. Filing is Correct, Outputs are Incorrect** In a recent example staff noted that a filing for Notice of Cancellation or Change of Assumed Name of Extraprovincial Company was correct, but the output was incorrect. Jira 232014

**4. Amalgamation Certificate Exceeds 1 page** In a recent example an amalgamation certificate included so much information it extended beyond one page. The legacy system puts the stamp over the text rather than spacing over two pages, so the certificate ended up illegible. Jira 22686

**5. Wrong Certificate Type Generated** In a recent example a company registered with what was noted as a slightly incorrect name and then reinstated. Due to the difference in name upon reinstatement the certificate showed Change of Name, whereas staff advised it should not show as such.

No files, tests, or entry points are identified. Start by reviewing the five legacy scenarios and the referenced Jira cases (269937, 241195, 232014, 22686); the work is done when the modern system's suppression requirements and expected behavior for these cases are defined.

Written by the indexing model from the issue text.