UI Design - NR result email content

[yuisotozaki]

This design ticket covers the email content design update for NR results.

The PO/Design team has decided to pursue this design effort to:

• Come up with a couple of options to improve email content to guide user to next step
• Gauge development effort based on proposed draft design
• Run research to drive final design

Draft Design on UXPin https://preview.uxpin.com/86ca5ddbe4d40318d3395577c17d4a692946fd27#/pages/163300702

[yuisotozaki]

@oanyahuru Please bring this up with SRE team to gauge development effort based on the draft design in UXPin link in the description above. The design team will be revising, evolving the design in the coming weeks.

[bolyachevets]

@pwei1018 i remember you mentioned before that with gc notify we can only supply text in the email body. it looks like the design the email body would need to be more than just plain text

[pwei1018]

@bolyachevets @yuisotozaki @oanyahuru Yes, GC Notify can only support text format in the email body. It can have some basic formatting syntax. We can't put the html style into the body. Here is the formatting guide.

https://notification.canada.ca/formatting-guide

[oanyahuru]

The email body looks as expected . I however noticed that under "You're not done yet! Follow these steps to register your business using this name:", the link under the first bullet point "1. Visit BC Registries and Online Services" takes the user back to the Name Request application instead of the whatever page (Colin, Societies Online, BCROS, etc.) to continue the business registration with the approved name request.

Private Zenhub Image

Similar to #17213

[bolyachevets]

uxpin emails are layout examples. source of truth for email contents: https://docs.google.com/spreadsheets/d/17wMY9znmWMr2RoXH9S2elffC8uE7iifUGB5Hu3VVFpE/edit#gid=0

[yuisotozaki]

I have a feeling that the email content is different depending on whether the business entity is modernized or COLIN. We should double check this. @oanyahuru do you have insight into this?

[oanyahuru]

@yuisotozaki the push is to make the distinction between entities that are modernized and those from Colin (possibly include Societies too). The current content (to my knowledge) does not make the distinction. I spoke with Patrick Wei last week about fine tuning the current letters, then releasing the letter with the distinction between entity types when the "way of navigation" upgrades go live. This will clear any existing confusions around the letters. The letters with entity distinctions is still a work in progress the scope of which might be widened to include other entity types. This might take a bit more time

[severinbeauvais]

Has this been tested (QAed) and can be deployed to Test and Prod?

Does this code change get deployed as part of namex-api, or does it need a separate deployment?

[bolyachevets]

Has this been tested (QAed) and can be deployed to Test and Prod?

Does this code change get deployed as part of namex-api, or does it need a separate deployment?

it is under a feeture flag and is in prod already

[severinbeauvais]

Just confirming: how did it get deployed to Prod?

[bolyachevets]

Just confirming: how did it get deployed to Prod?

as i just reapplied to your comment in another ticket, currently prod has code from August 15th, which should have the relevant launchdarkly flag: https://github.com/bcgov/namex/commit/c92d6484a63b5407aea5ea31bbeb8bb060d99f15 the commits that you might be concerned about under this ticket would have been ux updates to email templates

[severinbeauvais]

I don't know how this change gets deployed, so I don't know if it's in the next Namex API release or if it needs its own release.

-> Does this get deployed along with Namex API or do you need to release it separately?

[severinbeauvais]

Leaving it with you guys to deploy this as needed.

@ozamani9gh

[oanyahuru]

Letters updated and reviewed with @bolyachevets