search

bcgov / entity

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

UI - Frozen business: missing obligations info box #24437

Closed saragunnarsson closed 1 day ago

saragunnarsson commented 1 week ago
image.png
mstanton1 commented 5 days ago

@janisrogers our team has been doing extensive regression testing to identify discrepancies between our dashboard and the existing entity dashboard. In this case, although our dashboard functions differently, I'd suggest we don't actually make the change to match the old behavior. If we add a legal obligation box when a company is frozen we are advising the company to do something they cannot do. I think what's more important is that the legal obligations box shows in cases where the client has some available action. Do you have any concerns with our team not implementing the box in the frozen scenario?

cc @OlgaPotiagalova

mstanton1 commented 1 day ago

Sent to the business for input on whether we display the legal obligations box.

janisrogers commented 1 day ago

I had a discussion with Sara about this yesterday. Since the box should only be displayed until it is dismissed, I think it should remain. In addition, a business can be frozen for various reasons and time periods, but I don't believe that makes them exempt from legal obligations, or not in all situations. @mstanton1 Let me know if you want to discuss.

mstanton1 commented 1 day ago

@janisrogers the legal obligation exists in all cases for sole proprietorships. Legislation creates that legal obligation. I believe the box was added with the intention of reminding users who had not yet completed a post registration filing of their obligation. That being said, since we don't know if a SP has actually undergone any changes, this is simply a reminder that may or may not require action.

If the box is to remind the user of possible action, but there is no possibility of action in this frozen scenario, it seems purposeless to spend the additional time for this build. We'd be putting dev effort into a low volume scenario (frozen SP) to advise a user to take an action that can't be taken. I've checked with the business and they don't see value in having the message in this case. They've also noted freezing is limited, with the key reason for SP freeze being NSF payment which no longer happens often because within the system if the payment is rejected the registration won't complete. Based upon this, my inclination is to close the ticket. If this did feel like something worth revisiting it could be done once the entity dashboard has launched and stabilized.