search

bcgov / entity

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

Amalgamations Work Around (Modern and COLIN) #24447

Open davemck513 opened 1 week ago

davemck513 commented 1 week ago

Currently, in BCROS, only businesses that exist in LEAR can be part of an amalgamation. If I select a business that only exists in COLIN, I get this error dialog:

image.png

Ref: https://dev.create.business.bcregistry.gov.bc.ca/amalg-reg-information?id=TyAGnjTB9U&accountid=3040

severinbeauvais commented 2 days ago

Dis-regard this idea; there are problems with it. See Dylan's comment below instead.

One possible way to allow businesses in LEAR to amalgamate with businesses in COLIN is to allow staff to enter the COLIN business information manually, as is done for foreign businesses. For example:

image.png

The above does not sync to COLIN. Staff will need to go into COLIN and manually change such businesses to historical. NOTE: I am not sure if amalgamating information can be (or needs to be) added in COLIN.

One change needed in Business Create UI (LEAR): the list of home jurisdictions needs to include BC (currently BC is filtered out) (this is a shared component and will need a new prop to implement this change).

dylan644 commented 2 days ago

Steps involved in Amalgamation Workaround, as demo-ed to the business: (using as example a BEN created in BCROS and a BC corp resident in COLIN)

severinbeauvais commented 17 hours ago

@davemck513 @OlgaPotiagalova @Mihai-QuickSilverDev What is the requirement here?

dylan644 commented 14 hours ago

This ticket doesn't make sense, functionality cited in this ticket is working as expected and as designed.

For the Directed Launch Amalgamations will not be enabled in BCROS (that is my understanding at least), any Amalgamations that are required will be performed in COLIN.

The scenario where a corp is created in BCROS and the user wishes to amalgamate with an existing corp in COLIN, then the "Amalg Workaround" scenario will be used - outlined in the previous comment.

When we go live with the MVP release then all corps will be in BCROS and this issue will not occur.

Note: we will need to address handling Amalgamations that include XPRO entities soon after MVP go-live, but that is not the issue being cited here.

Recommend this ticket be closed with no action taken