Analysis on BC Online Helpdesk Access

[mstanton1]

• May be set up in the API already to prevent payment.

  LB confirm that payment does not work for BRTEST3

• Test as BCOL user

In BCOL prod Helpdesk is set as Qualified Supplier, and there is a tool in BCOL MHR to change their role to be set for General Users, SBC or Manufacturer so they can simulate their flow. In BCOL there is no payment processed, their BCOL account is debited.

• Need to follow up with BCOL Help Desk to confirm how many calls they receive on MHR and whether they support all client types (Manufacturer, Lawyer and Notary or Home Dealer)

Checked with Debbie Blyth and they support Manufacturer, Lawyer and Notary or Home Dealer, all user types except SCB, they go directly to staff when issues or questions. They received about 250 calls in 2023, and they received an average of 7000 calls per month altogether.

• Option could be to test what happens if we provide all product types. If not, we could provide access as staff and they could have test logons for each qualified supplier type if they wanted an exact match. If providing staff access warnings and error messages will vary so training would be required Melissa can help add user groups through Keycloak

In test they will have a BC service card for each QS type: manufacturer, lawyer/notary and dealership. In prod, Helpdesk is currently using the same account as staff but have helpdesk role which prevents payments from going through.

• Note if safeguards are in place to disable submit buttons is a significant amount of work so would need to assess if this is truly needed if we already prevent submission through the API and advise not to submit transactions in PROD in training

Payments are prevented with helpdesk role but we need to test if we can complete a filing when there is no fee.

[lbergero819]

Checked BCOL Helpdesk accounts in production BCOL legacy system and they use 2 accounts: 384796 and 190940, both accounts are set as Qualified Supplier, but there is a tool in BCOL MHR to change their role to be set for General Users, SBC or Manufacturer so they can simulate their flow.
I will check with them if to work with all the User roles in the new system.

[lbergero819]

@mstanton1 had a meeting with Debbie Blyth and posted the notes in the description.

[mstanton1]

The analysis above has been discussed and the following approaches and action items have been determined.

Approach:

• In PROD the BC Online Helpdesk account will be granted access using the Lawyers and Notaries qualified supplier role (Grant BC Online Helpdesk team access as Lawyers and Notaries in PROD #19364)
• In TEST the BC Online Helpdesk should be provided with accounts set up to mirror other client types (Lawyer and Notary, Manufacturer, Home Dealer) so they can provide support as those types as needed Create BCOL Helpdesk Test Accounts & Share with BCOL Help Team #19371
• In PROD the BCOL Helpdesk account should be set up for payment to fail for transactions. The only transaction staff should be able to complete end to end is the search which provides an unpaid option API - Prevent BCOL Helpdesk from completing Transactions in PROD #19203

cc @arlentees

[lbergero819]

@mstanton1 Test BC Service Cards were set for Helpdesk to use in test: following groups to be added:

Lawyer & Notary (Service Providers): Keycloak group - added mhr_qualified_user
Use BCREG0072
Manufacturer: Keycloak group - added mhr_manufacturer
Use BCREG0070
Dealership: Keycloak group - added add mhr_dealership
Use BCREG0071
Additionally BCREG0070-71-72 have the following groups:

account_holders
mhr_search_user
ppr-user
public_users