UI Design - Discharge

[Kaineatthelab]

Discharge Visual Design Comps (including Security Modal): https://projects.invisionapp.com/share/VH11K6AFRDTS#/screens?browse

Also See Design Ticket with all Reg Table Dropdown Menus/Actions: https://app.zenhub.com/workspaces/entity-5bf2f2164b5806bc2bf60531/issues/bcgov/entity/7619

Wireframes (rough design):

Static page views ~https://app.uxpin.com/edit/8887562#?id_page=140340701~

Interactive mockup used for sprint review July 27, 2021 ~https://preview.uxpin.com/1348a94271171ee8e283ecf65f50b9cb4d5f8af2#/pages/140603350/simulate/no-panels?mode=~

---

No fee for any discharge User needs to input debtor name to discharge - look at options before open or when open Single step - review and submit on single screen - the registration cannot be amended at the same time as it's discharged - check this with Court Order info... Notify user that Secured Parties receive a copy of the Discharge Verification Statement. Show icon beside discharge menu item to indicate "password" required

Read only information - displays current state of the registration Length Trust Indenture (if present) Registering Parties Secured Parties Debtors Collateral General Collateral

Inputs for this registration Court Order section/information - TBD Folio/Reference number field for tracking

[jinghualicgi]

Don't have enough requirements now. A debtor name is required

[janisrogers]

Requirements https://docs.google.com/document/d/1DHPmLp1nH368anJX4kPntPlMhvo-74D-cPOoOpGvJLw/edit

[yuisotozaki]

@janisrogers to provide "Court Order" field set.

[janisrogers]

Court Name – 256 characters, Required Registry – 64 characters, Required File Number – 20 characters, Required Date of Order – Date, Required Effect of Order – 1000 characters, Required

[yuisotozaki]

@janisrogers @tlebedovich UXPin mock ready for your review.

Change Summary

General

• Separated out the alternate options and reusable visual elements that are not part of the main design.

Discharge

• Cancel now has a modal for "Are you sure you want to cancel?" REF: Alteration https://projects.invisionapp.com/d/main#/console/20440642/430259307/preview
• Changed "Review and Complete" to "Confirm and Complete" REF: Alterations
• Moved the Registration Details band a the top and remove the header like this REF: Alteration https://projects.invisionapp.com/share/UF11EPFB26ZM#/screens/436252442_00_Alteration_Company_Info_Change_-_Default_View
• Added Court Order fheckbox and fields

Renew

• Added callout for "Repairer's Lien can only be renewed with a court order"
• Added callouts for "Repairer's Lien can only be renewed for 180 days and must have a court order"
• Added specific state for "Length" for Repairer's Lien" case
• Step 2, now only shows the renewal information

Amend

• Added "Amend|v" button to the General Collateral box
• Added callout for "Validation for Vehicle and General Collateral will be the same as new registration"
• Added "Save and Resume Later" button
• Added "Reset" button and modal confirmation
• Step 2 now only shows sections that contains changes; changes are badged.
• Moved Undo button to step 1 for things that was removed
• Updated Step 2 mock data content for consistency

[tlebedovich]

@yuisotozaki @janisrogers

Notes from assets grooming:

Regarding required information before allowing a discharge:

From Patrick

• currently user needs to validate Debtor - First 5 letters and enter Base Registration number

From Kevin

• Feels that clicking on the Base Registration number to get to the discharge is efficient for "entering a base registration number" - UX's call
• Still should ask for (any) Debtor Name (First/Last) - check is about making sure users are discharging the right one not really for security purposes.
• Add Debtor Name fields to the top area of screen number 2 (confirm screen)

Regarding Not charging for Discharge/Renew/Amend

From Kevin

• monitor abuse of this system as it allows users to see the current view of a registration/financing statement without having to pay a fee.

[yuisotozaki]

Will add debtor name field to step 2. What happens if the debtor's name is "Sid Meier"? Is the first 5 letters "SIDME"?

[janisrogers]

@yuisotozaki Doug say the API requires an exact match of the full debtor name.

[yuisotozaki]

@janisrogers Then the rule is "Exact match including case with one of the debtor names on the registration."

[yuisotozaki]

☝️ Not sure if the API is doing what the requirement is asking for. The requirement says first 5 letters. 🤔

[tlebedovich]

@PatrickAHeath @Kaineatthelab - For the Security Step for a Total Discharge/Renew - Can you confirm whether we should use Debtor First and Last Name (which apparently is what the API is using), or First 5 letters of a debtor's name (what the requirements doc says).

Yui also mentioned - If the latter, what happens if the debtor's name is "Sid Meier"? Is the first 5 letters "SIDME"?

I think First and Last name is more straight forward for the user, if this could work with the regulations and requirements.

c/c @doug-lovett @jordiwes @yuisotozaki @janisrogers

[yuisotozaki]

Answer to above on RocketChat.

• Exact first name last name of base debtor for Discharge and Renew actions
• First 5 letters when adding a registration

Details to still hammer out

• Are middle names included in the exact match and first 5 letter match logic?
• What is the format of the name? First name, last name? First name, middle name, last name?

[tlebedovich]

Conversation from Rocket Chat;

Yui: In both Discharge and Renew epics, there is a “you need to enter 5 letters of the debtor’s last name or business name” called out in the requirement documents. I heard that the API requires exact match (case sensitive?) for the full name of a debtor on the registration. So which is it? Just 5 letters or exact match? And for exact match, is it just for debtor’s name or can it be business name?

Patrick: The current PPR application requires the user to enter the first 5 characters of the debtor Last Name or Business Name, as well as the Base Registration Number. If the 5 characters entered are incorrectly, the system displays the correct 5 characters, which the user can then enter into the field and proceed with the renewal or discharge. The regulations indicate that the full debtor name is required - ‘the name of the base debtor exactly as entered on the base registration’, which was what Kevin brought up last week when we were discussing this.

My understanding from Bob is that entering the 5 characters is another check that the user has the correct base registration number, since no other information is displayed about the registration before the renewal/discharge is completed. In the design for the new application, the information about the registration is displayed not only in the My Registrations list that they select from, but also within the screens for the activity. The user can see more information about the registration and easily tell if the base registration number they entered is the one they want to act on. It seems silly to require a user to enter the first 5 characters of the debtor name that is displayed in full on the same or prior screen.

Kaine: I believe that is what we decided in that last meeting. So if the registration is in your dashboard you can do those actions and the end modal makes you double check…. When adding a registration to your dashboard you do the 5 letter modal

the api is currently exact match but it should work exactly like old system

Yui: I think we landed, on Friday last week, on having the debtor verification at the beginning of the Discharge/Renew flow so that we don’t have users putting in the effort only to find that they had the wrong registration open at the end.

Patrick: If the registration is already in the My Registrations list on the dashboard, the user will already see registration details and not have to enter the first 5 characters of the debtor.

I think having an additional check for debtor name would be useful when the user requests a registration be added to their My Registrations list, but once there and they can see the details of those registrations, allow them to select the registration to act on. A ‘Are you sure you want to do this?’ modal should be included on each activity as a last chance exit for the user.

Yui: For that last chance exit, sounds like the current regulation requires the new application to continue to have a debtor name verification modal for discharge and renew. Once the regulation changes, we can replace these verification modals with a simple “Are you sure you want to do this?” modal.

[tlebedovich]

[tlebedovich]

FINAL DECISION (FOR NOW):

• Keep modal when user clicks Total discharge/Renew (confirm Amend TBD)

• UI modal should ask for a base debtor's LAST Name or BUSINESS Name (don't need first name)

• backend will only be searching for first 5 letters, but user doesn't need to know that

• ON HOLD - remove the word "base" debtor, it will be ANY active debtor (keep base debtor wording for now)

• if the user inputs the wrong name and hits the blue "Continue" button, add a small red field error validation message below the text field

• normalized characters

• Ignore capitalization

• Ignore spaces

---

• future suggestion from Kevin - might offer users a check box to "don't show this again" for the modal (HOLD ON THIS)

[tlebedovich]

@yuisotozaki - comment from sprint review:

• Court Order fields - should "Registry" field be label be more specific?
• Kevin mentioned him and Janis talked about some other specifics of the court order fields that may be needed

[tlebedovich]

@yuisotozaki - if your wiresframes are done for discharge and renew, you can move the tickets back to in progress and they'll go to my design to do list and you can assign them to me.

[yuisotozaki]

Back to In Progress for visual design.

[yuisotozaki]

Policy note around "Expiry Date" https://github.com/bcgov/entity/issues/7560#issuecomment-890207580

[tlebedovich]

notes: dashboard modal updates -

• edit modal title and copy (not security verification, not confirmation - refer to NR advanced look up wording)
• if the user enters the wrong information, display the correct base debtor information (as per current app)

[yuisotozaki]

UXPin updated

• Modal title now reads "Base Debtor or Business Name"
• The modal now shows the correct base debtor last name if the user gets it wrong

[tlebedovich]

@yuisotozaki @janisrogers - my notes from the call --

Add a statement to both discharge and renew letting users know that the registration may have been subject to an amendment/court order(s) and that this is just showing a current snapshot of the registration, there may be additional information then what is displayed (users can do a search to see the full history of this registration.

Kaine mentioned writing two versions of the statement - one general and one specific if we can know for sure.

please add more details if I misunderstood

it can be in regular text, a yellow alert is not needed.

[yuisotozaki]

UXPin updated

• Discharge and Renew screens now has a text bringing user's attention to a possibility of the registration being subject to an amendment.

[janisrogers]

@yuisotozaki I don't think "subject to an amendment" makes sense as the text. We should discuss.

[yuisotozaki]

@janisrogers I could use some technical lingo tutelage for sure. I was just looking up what I heard during the meeting.

[yuisotozaki]

Asset Grooming Meeting Decisions

• Remove "Review the information in this registration prior to total discharge." message from the top.
• Keep "Conduct search to ..."
• Keep yellow box about secured parties

[PatrickAHeath]

@yuisotozaki For the wording related to performing a search to retrieve complete registration details, here's my suggestion:

Other activity exists for this registration. To obtain complete details, it will be necessary to conduct a Registration Number search.

If the only registration entry for this Base Registration number is the original registration (no amendments or other activity), the complete registration is already displayed and there's no need for the message.

Also, performing a Registration Number search can only result in one exact match (or a nil report if they enter the number wrong). If they perform any other search, they may end up with multiple results and there could be confusion as to which registration they should be looking at.

[yuisotozaki]

@tlebedovich ☝🏻 Additional recommendations from Patrick re: text content.

[PatrickAHeath]

Decision from August 16 standup: (revised again) Debtor Verification which looks at Base Debtor Last Name or Business Name will be modified as follows:

• The client will be asked to enter the full Last Name or Business Name of any Debtor associated with the registration.
• The application will attempt to match the first 5 characters against the first 5 characters of the Last Name or Business Name of any debtor, not just the Base Debtor. (If the client enters less than 5 characters, the complete Last Name or Business Name must be an exact match)
• If there is no matching Debtor Last or Business Name, the application will display the Last or Business Name of the first active debtor for the registration as a hint to the client.

The term Base Debtor will not be added to the Search output PDF.

[tlebedovich]

Thanks @PatrickAHeath - I think we were going to have the user put it the full debtor's last name or full business name, just for ease of use, but the check will just be for the first 5 characters. And I'm hoping if its not a match then we can show the full last name or full business name for users as the hint (versus just first 5). Just a technical FYI.

[PatrickAHeath]

@tlebedovich Yes - the magic behind the curtain!

[yuisotozaki]

• Remove "Save and Resume Later" for now until we can figure out race condition handling.
• "Amend" vs "Change" on the small icons - "Amend" for now but @forgeuxGH5 to confirm.

[janisrogers]

@PatrickAHeath I think the decision might have been to allow entry of any debtor, not just any active debtor, because we want to support people entering the base debtor even if it has been removed.

[PatrickAHeath]

@janisrogers I heard Active Debtor, which is why it's worded that way. I support your reasoning.

[janisrogers]

I think the first active debtor was what we will show if they get it wrong, but they can enter any debtor.

[Kaineatthelab]

yes

[yuisotozaki]

August 18 Assets stand-up discussion minutes around the "Confirm registration to be discharged" modal. EDIT: BA/Design Grooming clarification included from August 18

• The drop down list is triggered when the user focuses on the field
• The visible debtor and business name list should contain active ones only (ie if a debtor was removed that name should not be displayed)
• The user must enter at least 1 character to trigger the filtering using "case-insensitive begins-with"
• The partially matched list item should be highlighted
• The list must contain the full list of debtor names and business names even when more characters are entered in the field (This bullet is a nice-to-have feature)

@tlebedovich @forgeuxGH5 Please review above list to assist Kial with dev.

[tlebedovich]

@forgeuxGH5 - I'm not sure that is how type-ahead works - ie Bullet 2 above about keeping the full list of debtor names even if they have typed some letters that aren't matching, otherwise it ends up more like an open text field, but we don't want the user typing their own name in if its not included in the list. The typehead works by filtering through a restricted list.

[janisrogers]

Going with stock vuetify auto-complete component as in Tracey's design.

[jinghualicgi]

@tlebedovich Hi Tracey, I am going to closed Done ticket after tickets stay there more than 2 days. I saw you reopened some UI Design ticket, Please let me know if you have any suggestions regarding this process. Thanks

[tlebedovich]

hi there

Sometimes I will finish/close a design ticket but then a new dev ticket needs it so I have to reopen my design ticket to be able to link it to the new dev ticket. its a flaw of zen hub unfortunately.

[jinghualicgi]

Thanks Tracey, so I will continue close tickets by following 2 day rule, please feel free to reopen design ticket when needed. Thanks