Skip to content

CCM-15018: How to request a digital proof#879

Open
bhansell1 wants to merge 25 commits intomainfrom
feature/CCM-15018-request-proof-link
Open

CCM-15018: How to request a digital proof#879
bhansell1 wants to merge 25 commits intomainfrom
feature/CCM-15018-request-proof-link

Conversation

@bhansell1
Copy link
Copy Markdown
Contributor

@bhansell1 bhansell1 commented Mar 16, 2026

Description

  • adds a banner to direct users on how to request a proof for a digital template
  • adds a new page explaining how to request a proof
  • shows request proof banner when digitalProofing is off
  • shows send a test message banner when digitalProofing is on
  • shows banner (digiproofing or request a proof) on; preview-submitted-template, preview-template, /message-plans/preview-template]
  • updates send a test message link to no longer open in a new tab

Context

Type of changes

  • Refactoring (non-breaking change)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would change existing functionality)
  • Bug fix (non-breaking change which fixes an issue)

Checklist

  • I am familiar with the contributing guidelines
  • I have followed the code style of the project
  • I have added tests to cover my changes
  • I have updated the documentation accordingly
  • This PR is a result of pair or mob programming
  • If I have used the 'skip-trivy-package' label I have done so responsibly and in the knowledge that this is being fixed as part of a separate ticket/PR.

Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.

  • I confirm that neither PII/PID nor sensitive data are included in this PR and the codebase changes.

@bhansell1 bhansell1 marked this pull request as ready for review March 17, 2026 14:00
@bhansell1 bhansell1 requested a review from a team as a code owner March 17, 2026 14:00
alexnuttall
alexnuttall previously approved these changes Mar 18, 2026
alexnuttall
alexnuttall previously approved these changes Mar 18, 2026
import type { ContentBlock } from '@molecules/ContentRenderer/ContentRenderer';
import { getBasePath } from '@utils/get-base-path';
import { markdownList } from '@utils/markdown-list';
import { MarkdownToJSX } from 'markdown-to-jsx';
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

maybe re-export this from the util file, rather importing directly?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated.

alexnuttall
alexnuttall previously approved these changes Apr 2, 2026
`${baseURL}/templates/message-plans/choose-text-message-template/${digitalProofingEnabledMessagePlanId}/preview-template/${digitalProofingEnabledTemplateId}?lockNumber=0`
);

await assertTestMessageBannerVisible(
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

in these tests where we're ending on this assertion, can we click the link too so we can test the navigation? since we're now not doing it in the other test?

`${baseURL}/templates/message-plans/choose-nhs-app-template/${digitalProofingEnabledMessagePlanId}/preview-template/${digitalProofingEnabledTemplateId}?lockNumber=0`
);

await assertTestMessageBannerVisible(
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same here, could update to add a assertAndClickTestMessageBanner we can use across all of them maybe?

`${baseURL}/templates/message-plans/choose-email-template/${digitalProofingEnabledMessagePlanId}/preview-template/${digitalProofingEnabledTemplateId}?lockNumber=0`
);

await assertTestMessageBannerVisible(
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

and this one

templateId: templateIds.NHS_APP,
},
] as const) {
test(`should load page ${channelName}`, async ({ page, baseURL }) => {
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
test(`should load page ${channelName}`, async ({ page, baseURL }) => {
test(`should load page for ${channelName}`, async ({ page, baseURL }) => {

'Request a proof'
);

const backLink = page.getByRole('link', {
Copy link
Copy Markdown
Contributor

@nicki-nhs nicki-nhs Apr 7, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it not the standard back link that exists on the base page?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants