API - Email to MHR Staff for Transport Permits of MHR Changes to Registrations with a Lien

[mstanton1]

Figma Design

When a MHR has a Transport Permit filed AND has a PPR SA against it, a notice of change in location is sent. An email should be generated to BC Registries Staff with a link to Notice of Change in Location documents to be sent to clients.

Report Containing Registrations
Email frequency for MHR Registration: once per day, later in the evening so it is likely to include all Registrations from that day (e.g. 12 AM?)
Email address: bcregistries@gov.bc.ca
Email title: MHR Notice of Change in Location - Month DD, YYYY
Email body: Below you will find a link to download the MHR Notices of Change in Location. These documents are required to be mailed to secured parties when a change of location occurs and the MHR Registration has a Personal Property lien against it.

PDF's for mailing (Link): Include PDF for all Notices of Change in Location since the job last ran in the form of a downloadable link. This should be for any PPR lien type.

Report Without Notice of Change in Location documents
Update Email title: No MHR Notice of Change in Location (note: if this is possible, can should do the same in the Manufacturer Email)
Update body text to read: No MHR Notices of Change in Location documents were created on Month DD, YYYY. (where Month DD YYYY is the day prior, the period for which the query ran)

Other Information
-one notice is sent to each secured party for each PPR Security agreement

• Sort order of registrations by timestamp
• Applies to registrations for change location and have an outstanding PPR lien (document types 103, STAT, REGC, PUBA, Amend Transport Permit - code pending).

Developer Note:
New env var named NOTIFY_LOCATION_CONFIG with notify api and email configuration information.
API changes:

• Create query.
• Generate report.
• Save report to doc storage and create link.
• Conditionally email via the notify api.
• Add event tracking.
• Add unit tests.
  Create GCP scheduled job.

[mstanton1]

Reviewed text with Sharon - note: I've inquired above about a potential change in the email subject when no notices need to be mailed. Having it apparent in the subject line that there are no notices would save the team from having to click to open. Note this is preferred to simply not generating the email, because if we don't generate emails when no reports are available if there was a failure we would not know.

[mstanton1]

@doug-lovett final updates have been made to the ticket / design for this email. It's ready to be picked up.

[doug-lovett]

Deployed MHR API 1.6.5 to TEST to verify the email configuration as no DEV GCP notify api is available. Example emails with and without registrations forwarded to Melissa and Divya. TEST scheduled to run every Wednesday at 5 PM PST. It can be run manually at any time.

[chdivyareddy]

Hey @doug-lovett , here are the registrations from TEST with and without location change and has a PPR SA against it. Please take a look and forward the emails when possible and let me know if I'm missing anything, thanks!!

MHR 107298 without notice of change in location:

MHR 107275 with notice of change in location:

[doug-lovett]

@chdivyareddy it is a batch job with a single email sent nightly to staff. I ran the job manually and forwarded the email to you.

[chdivyareddy]

Verified with the emails attached.