Support Business team to perform first BEN amalgamation

[OlgaPotiagalova]

We should provide a support to the Business team to try out the amalgamation

Case 1. BEN and BC LTD resulting in BEN company. The deadline for this filing is May 1 - The request was abandoned by client/law firm.

• [x] Discuss steps and possible risks.
• [ ] Perform test for FF in Test environment
• [ ] Copy a BC LTD from CPRD to BCROS (Omid/Dave), verify dates/times match
• [ ] Enable the amalgamation option in PROD (for a specific user/staff only?)
• [ ] Entity team performs amalgamation filing (over a call with Business team)
• [ ] Verify the result is correct in BCROS
• [ ] Disable the amalgamation/FF
• [ ] Sync back to CPRD : TED BEN () and BC LTD (historical)-> manual process/OPS ticket, the status needs to be correct in legacy system
• [ ] Without sync in place we don't receive BN15 -> manual process/OPS ticket
• [ ] Record the feedback (including from Business) and create tickets as required

Questions:

1. What type of amalgamation? - amalgamation is long form/regular - 2 companies being combined into one. Business team is going to confirm once they get documents

Case 2. Two BEN companies resulting in BEN company. Sort form, no NR is required. The deadline - today (Aug16). Execution date - Aug 16.

• [x] Discuss steps and possible risks.
• [x] Perform test for FF
• [x] Enable the amalgamation option in PROD and confirm it is available (for Naveen only)
• [x] Entity team to perform amalgamation filing (over a call with Business team)
• [x] Verify the result is correct in BCROS
• [x] Disable the amalgamation/FF
• [x] Sync back to CPRD : TED BEN BC1497351 -Active) , TING BEN (BC1191266,BC1276727 historical) -> Amalgamation automatic sync is in place now, so OPS ticket should not be required
• [ ] Verify BN15 message is triggered and BN is received @Mihai-QuickSilverDev to connect with business
• [ ] Record the feedback (including from Business) and create tickets as required - see comment below dated Aug 16, 2024
• [x] (NEW) load the user's dashboard and affiliate the new business
• [ ] (NEW) load the staff dashboard and remove new business from table @Mihai-QuickSilverDev to connect with business

[OlgaPotiagalova]

The assumption that no work is required for the sync implementation.

[severinbeauvais]

I looked into enabling the FF for staff users only. In the LaunchDarkly "entity-ui" Production environment, in the Supported Amalgamation Entities feature flag Targeting tab, we need to add a custom rule that looks like this:

We could fine-tune this to allow only certain users, or only certain entity types, but this is the basic principle. I tested this in Test environment and it works as expected.

[OlgaPotiagalova]

This amalgamation has been pushed out to May 15th, the law firm is waiting on paperwork from their client to proceed.

[OlgaPotiagalova]

Update from the Business team: the closing is now scheduled for mid to end of June

[severinbeauvais]

For case 2, the new (TED) business is: https://www.business.bcregistry.gov.bc.ca/BC1497351

Also, the following bugs were created:

• Staff email bug: 22845
• Resolution date bug: 22846
• Amalgamation type bug: 22847
• Receipt bug: 22848
• Amalgamated into bug: 22849

[severinbeauvais]

Waiting for Mihai to review this and check off the remaining boxes. Then we can close this ticket.

[Mihai-QuickSilverDev]

@severinbeauvais Just to confirm that I am checking the boxes for the BEN's only amalgamation, that already took place, and not for the first BEN + LTD one that was cancelled.

[severinbeauvais]

Correct. The first one was abandoned.

[vikas-gov]

Changing estimate from 5 --> 0 as at this point its a BA activity