bcgov / entity

ServiceBC Registry Team working on Legal Entities
Apache License 2.0
23 stars 59 forks source link

Unable to submit security agreement - address issue #16849

Open mstanton1 opened 1 year ago

mstanton1 commented 1 year ago

Describe the bug in current situation A client submitted a security agreement. They had entered all required information. For the secured party the client used the manual option, typed in the business name of the secured party, and then typed the address in address line 1, and selected the option that popped up in the address lookup. When the client navigated to complete the transaction they received an error unable to submit.

Staff noticed the address displayed showing British Columbia spelled out and asked that the client go in and update the address. The client did so and was able to submit.

Link bug to the User Story

Impact of this bug A client will experience an error when they have entered a valid address. The client will be unable to submit. Triage takes time and staff resources.

Chance of Occurring (high/medium/low/very low) Presuming low as this is the first instance of this issue.

Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?

Steps to Reproduce Steps to reproduce the behavior:

  1. Go to https://test.assets.bcregistry.gov.bc.ca/dashboard
  2. Click on Security Agreement
  3. Scroll down to Input details for all fields except for secured party
  4. For secured party choose 'Add a Secured Party that doesn't have a code', choose Business, type a business name (e.g. from error REALTECH CAPITAL GROUP INC.), and in address line 1 start typing the address 1210-1030 georgia street w. When the address displays in the lookup list select it. Click 'Done' in the address component.
  5. Try 'Register and Pay'

Actual/ observed behavior/ results In my first test the submission failed. In my second test the submission went through right away. I had to come back, choose edit on the address for secured party, select BC again from the dropdown, and then submit a second time.

Expected behavior

Screenshots/ Visual Reference/ Source If applicable, add screenshots to help explain your problem. You an use screengrab.

Instances Noted in Ops 2837

mstanton1 commented 1 year ago

@chdivyareddy a client reported an issue submitting their PPR Security Agreement. I tested and reproduced, but when I tested a second time (to take screenshots and document this ticket) I didn't hit the error. Can you try? I will send the client email with attachment that shows how the secured party address listed British Columbia instead of BC.

Note: I encountered a second issue when testing this flow where after hitting the error and going back to edit the secured party, the secured party name and address loaded as very narrow, only about 1/4 of the way into the screen. I will test that again and log a separate bug if I can reproduce.

chdivyareddy commented 1 year ago

@mstanton1 Will take a look!

chdivyareddy commented 1 year ago

Current behavior in TEST after hotfix working as expected.

Security Agreement - Review & Confirm: Secured party address listed as BC which is expected image.png

Registration was successful: 100537P image.png

Amending the secured party displays the party name and address as expected and wider: image.png

Editing the secured party displays the party name and address as expected and wider: image.png

chdivyareddy commented 1 year ago

@mstanton1 to note - the second issue was also fixed by @cameron-eyds in TEST, thanks!!

mstanton1 commented 1 year ago

Thank you @chdivyareddy ! @cameron-eyds is on it. I'd created a separate ticket for the width anyways and added to the sprint so we can move that along and release. If this is also fixed we can move it as well with the hotfix.

chdivyareddy commented 1 year ago

@mstanton1 Just heard from @cameron-eyds that no change was made to the first issue, but I was not able to reproduce it...I tested it with adding the address manually and selecting the address from the dropdown list and both worked as expected.

Can we have a quick call?

mstanton1 commented 1 year ago

Putting back to bugs column to monitor based upon discussion with @cameron-eyds and @chdivyareddy

Suspected it is related to manual entry of province and not properly mapping to the value.