Bug? - Amalgamation Filing - Aberrant Behaviour on Cancel

[dylan644]

Describe the bug in current situation When clicking Cancel to abandon a Filing in Progress the normal behaviour is for the screen to redirect to the Corp/Entity Dashboard.

Amalgamation filing (all 3 variants) does not follow this pattern, instead redirecting to a different screen causing user to then have to navigate back to where they were.

The Regular Amalgamation does not display the info for the corp where the amalgamation was initiated from at the top of the screen. When cancelling the filing it returns the user to an anonymous corp dashboard presumably based on a temporary corp num so it might make sense to redirect the user to a generic page after deleting the filing, but the filing was still invoked from the corp dashboard or a corp.

Both the Horizontal & Vertical Amalgamations however display info for the corp that the filing was invoked from on the filing screens, the user is also returned to the correct corp dashboard in order to actually delete the draft filing & is then redirected to that generic screen instead of the corp dashboard

Question - if a user initiates an action (delete draft) from a corp's entity dashboard, should they not be returned to that screen after the action is performed ? This would be consistent with the behaviour of deleting a draft for every other filing.

Impact of this bug Minor - may confuse novice system users

Chance of Occurring (high/medium/low/very low) Consistent behaviour

Steps to Reproduce Steps to reproduce the behavior:

1. Go to corp dashboard
2. Start an Amalgamation filing (any flavour)
3. Cancel
4. screen redirects to corp dashboard (specific corp dashboard for Horizontal & Vertical)
5. Delete draft
6. Redirected to.... see screenshots below

Actual/ observed behavior/ results See 3rd screenshot

Expected behavior Every other filing returns user to corp dashboard

Screenshots/ Visual Reference/ Source

[vikas-gov]

To be reviewed with UI team @andyyanggov @janisrogers

[severinbeauvais]

This is a flow issue: when an amalgamation filing is created (from an existing business) then the user jumps into the "bootstrap filing" flow. The amalgamation filing does not belong to the original business.

From Create UI, navigating the breadcrumbs back a level (or clicking Cancel) takes you to the bootstrap business page (amalgamation application in this case).

From Filings UI, navigating the breadcrumbs back a level (or deleting the draft filing) takes you to My Business Registry page.

Because the user has jumped into the bootstrap filing flow, there is no clear way to get back to the business they started from (other than clicking the browser's Back button).

It was suggested in last week's bug triage meeting that some verbiage could inform the user's expectations. We're looking for the UI/UX team's thoughts and advice on this. Thanks!

[severinbeauvais]

Note that amalgamations, continuation ins, incorporations and registrations all follow the "bootstrap filing" flow.

[andyyanggov]

I see two issues here, the first one is more trivial but reveals the bigger underlying issue.

Issue 1: Deleting an amalgamation application from an entity dashboard should not redirect the user to the Business Registry Home page. In our system's current iteration, this action should return the user to the MBR, which is one level up in the breadcrumb.

The ideal behaviour though, would be to keep the user on their entity dashboard, but with the amalgamation application now removed—which brings me to the second issue.

Issue 2: As Sev pointed out, in the flow of creating a business, the system first makes a bootstrap business, which is made to look like an actual business. These are masked objects—different objects masked to look like the same object—and can confuse users. While it's not noticeable in other filings, this issue is highlighted in amalgamation. Because an amalgamation application starts from an existing business, there will be two "businesses" of the same name in the user's MBR—the existing business and the bootstrap business. In the breadcrumb, they look identical.

This can be very confusing and disorienting, especially for more novice users. If I was a user, I'd expect to see something like this instead:

That's my two cents from a UX perspective. I'm interested to hear what others think.

[severinbeauvais]

Thanks, Andy. Your insight is very appreciated!

This comment is not a rebuttal. I am confirming / amplifying the current behaviour.

Here is a deletion of a draft bootstrap filing (amalgamation, continuation in, IA, or registration) from the entity dashboard. Note that one level up on the breadcrumb takes you to the MBR (which I verified).

After the deletion, I am taken to the top of the Business Registry UI (below). I agree that this should take me to the MBR instead.

...

I agree that having two entities in play during an amalgamation (the original business and the boostrap business) is confusing. The thing is, the amalgamation bootstrap filing doesn't belong to the original business, so technically we don't show it in the original business' todo list. (In fact, can't the amalgamaTING business be changed -- then whose todo list should it be in? Maybe all TING businesses?) Also, what about standalone (regular) amalgamations that don't have any TING businesses yet?

Maybe some of us should meet to see how we can improve this. @OlgaPotiagalova @janisrogers