Add Staff ability to file and pay for a name in Name Request

[lmcclung]

Background

Staff can request names on behalf of citizens who do not have access to a computer, are unwilling to file on their own, or need assistance.
Citizens send in a paper form with payment.
In order to enable staff to request names on their behalf, we need to allow them to submit a name request while logged in with their IDIR(staff role). This will give them staff payment options, and let them do things like give free NRs, or charge someone's BCOL account.

With the elimination of terminals at SBC regional offices, SBC staff are no longer able to assist in the capacity that they did before (have their own special fields for payment, enabled by IP address). We have decided not to implement this. They can instead provide citizens with a paper form and mail it to registries for them.

Story

AS A staff
I WANT to file and pay for a name in Name Request
SO THAT I can accommodate citizens who cannot/will not use a computer

Acceptance Criteria

Scenario 1 - New Name Request

GIVEN I am a BC Registries staff with an IDIR(staff role)
WHEN I submit a name in Name Request
THEN I can pay with a BCOL account, Routing Slip or indicate No Fee. (Priority Fee option is already in UI, so don't include it here).

Scenario 2 - Pay with BCOL Account

GIVEN I am a BC Registries staff with an IDIR(staff role)
WHEN I pay for a name request with a BCOL account
THEN they BCOL account will be debited the fees
AND a line item will appear in the staff account's transaction history

Scenario 3 - No Fee

GIVEN I am a BC Registries staff with an IDIR(staff role)
WHEN I pay for a name request with "no fee"
THEN the payment will complete
AND the receipt will show $0.00? "no fee"? Cant remember.

Scenario 4 - Cash or Cheque

GIVEN I am a BC Registries staff with an IDIR(staff role)
WHEN I pay for a name request with a routing slip
THEN then the routing slip information will appear on the receipt

Scenario 5 - View (verify)

GIVEN I am a BC Registries staff with an IDIR(staff role)
WHEN I pay for a name request with a BCOL account
AND I view the receipt
THEN I will see the correct payment method that was used on the receipt

Note
change to the shared component, remove the priority from the component, or disable (and fill with whatever the selection was in the name request flow)
Decided to update shared component, and hide the priority selector from the staff payment component when in the name request flow. Default show priority selector in all other instances of this component.

Definition of Ready for Sprint - User Story

• Are the Acceptance Criteria defined?
• Does the user story speak to the value being created, and is understood by the team?
• Are the dependencies known/ understood? (to the our best knowledge)
  • Relationships team, update payment receipts depending on payment option
  • ?
• Is this user story small enough to be completed in one Sprint?
• Dev team accepts UI artifacts? (visual UX designs ready to go)
• Is it clear whether this work is intended for deploy or limited/staged-release?
  • Release to market after completion

[sienna-oldaccountdontuse]

Met with Loren, Linda, Melissa, Trish, on Jan 29th, 2021

Decided that there is not a lot of value for us to build a solution for SBC regional offices, considering they process 63 NRs/year.
We are considering allowing them to accept paper name request forms. They can also search clients existing name requests using the public site, help them get their results, edit or cancel the NR, etc. with the clients phone number and email. This will require updated forms, and some training for SBC staff.

[lmcclung]

Can we also look at making search by email/phone optional - can search just by NR
Also what about giving ability to search by name or NR#? How much extra effort is this?
Or maybe we just make Scenario 2 its own enhancement ticket to be prioritized later.

Nevermind - created ticket 6379 to address this. Rough estimate from Severin:
To make email/phone optional would require both UI and API updated. Probably 1/2 day each.
To search by name would require UI work of course, and probably a new API endpoint for searching by name. Probably 1/2 day for UI and 1 day for API.

[lmcclung]

Outstanding questions:

1. What if person submitting form doesn't include both Email and Phone number? What if they don't have an email?

We can change the business process for staff to be use their staff email, then they can wait for the results letter, and when they get it, print the results and mail it to the applicant info mailing address. This process is a little bit more involved than the current process, where they just select "send results by mail" on NRO and then the staff has no more involvement.

2. How many levels of staff access are required? Do Maximus/BCOL help desk staff need any staff access? just BC Registries staff

should be just one

[tlebedovich]

Hi @lmcclung and @Sienna-Blumstengel - Is this the Dev ticket? I'm wondering if it should it be in a dev zenhub pipeline versus the design pipelines? We have a corresponding design ticket already. The design is ready to go for dev.

[lmcclung]

Yes, we hijacked your design ticket.

[lmcclung]

Moved back to ready for QA
@riyazuddinsyed are you still working on verifying the receipt?

[sienna-oldaccountdontuse]

Missed some requirements, we are finishing the missed ones in https://app.zenhub.com/workspaces/entity-5bf2f2164b5806bc2bf60531/issues/bcgov/entity/7825