Release 11.5.0
Law 14 -Phase 2B -Ad Hoc Requirements
The following changes have been made in accordance with Law 14 when adding ad hoc requirements directly to a contract. This is to ensure that requirements for a Quebec target party always appear in French first.
Questions
The ability to add bilingual questions directly to a contract was delivered in v11.4.0.
In the current version we have expanded the functionality to tie into the existing language change workflow to ensure that when a contract language change request is submitted, unfulfilled bilingual ad hoc questions are automatically removed and presented to the target party in the preferred language of the contract
Documents & Agreements
Any ad hoc documents that target the target party must be added in the language of the contract or be bilingual.
If an asset is selected for that target party and it doesn't match the contract language, the user will receive an error to indicate that the requirement is not compatible.
In a future release we will look to limit the pick list to only display eligible documents or agreements in the first place.
Law 14 -Phase 2B -Advisor or Corporation Moves to Quebec
This is the 1st of 3 changes required to enable the functionality to allow existing contracts to be updated to French as required by the Law 14 regulations when a party moves to Quebec.
This change is disabled in production and will not be enabled until all of the components are ready and until this item has gone through User Acceptance Testing.
The first change is specific to the pop-up that is displayed when the user edits their business or residential address to Quebec and clicks 'Save'.
- The pop-up will dynamic to provide context regarding Law 14 and
- if applicable a list of 'in flight' English contracts which are currently assigned to the target party and have outstanding requirements.
- The user will be able to click the Application ID link to navigate directly to affected contracts
There are still 2 additional changes that need to be made to:
- Apply the contract language change workflow to the contracts identified (either the unilingual or bilingual workflow) when the user selects the 'Save' option without first completing the outstanding requirements.
- Update any other English language contracts which are not currently assigned to the target party to French
Additional Changes
Please refer to the release notes for any additional changes
11.5.0
Go Live: December 6th, 2023
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
| SD-46279 | Limit Ad hoc Documents & Agreements to be Added in Contract Language | The requirement to restrict ad hoc documentations and agreements to be added only in the current language of a contract when they target the target party on a contract, has been completed. Going forward all ad hoc requirements (questions, documents & agreements) for the target party must be added in the language of the contract (or be bilingual) to ensure that requirements are always presented in a French first for a Quebec target party. | Regulatory -Law 14 |
| SD-48060 | Advisor or Corporation Move to Quebec | This is the 1st of 3 changes required to enable the functionality to allow existing contracts to be updated to French as required by the Law 14 regulations when a party moves to Quebec. Any new requirements added to existing contracts, must be presented in French first for a Quebec target party. This change is specific to the pop-up that is displayed when the user edits their business or residential address to Quebec. The pop-up will provide them:
This provides the user with an opportunity to complete the contracting requirements and submit the contract(s) prior to saving their address change so that their work is not lost This change has been deployed in a disabled state and is therefore not visible to any party at this time | Regulatory -Law 14 |
| SD-51969 | Allow List to be Scrollable | This is a continuation of SD-48060 (above) to allow for the contract list to be scrollable as needed in the event that the user has a long list of English contracts with outstanding requirements. This change has been deployed in a disabled state and is therefore not visible to any party at this time | Regulatory -Law 14 |
| SD-51406 | Ad Hoc Bilingual Questions Tied into Bilingual Workflow | This the second part of SD-47900 (v11.4.0) which provided the capability for clients to add ad hoc questions directly to a contract. When an ad hoc bilingual question is added, it will be eligible for the bilingual language change workflow that was deployed as part of Bill 96/Law 14 -Phase 2B in order to ensure that the process for updating the question to the alternative language is efficient as possible | Regulatory -Law 14 |
| SD-51504 | AODA -Misaligned Columns | The columns in the Transfer Contract Request screen and Advisor Search Results screen were overlapping for some users. This overlap has been corrected | Regulatory -AODA |
| SD-51576 | Corporation Name Too Long | When we released the change under SD-50816 (v11.4.0) it was identified that the updates did not work for some Chrome browsers and resolutions. This has since been resolved. | Support |
| SD-51346 | Unable to Edit/Delete Ad hoc Questions | In certain scenarios the client was able to add, but unable to edit or delete an ad hoc question when it was added to a contract. This limitation has been addressed and they are now able to edit/delete prior to sending the contract to the target party | Support |
11.5.1
Go Live: January 3rd, 2024
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
| SD-51586 | Allow Apexa Staff to Search BackCheck Results | Redeployment of SD-51586 as it was not merged into 11.5.0 version appropriately Apexa staff have been given the ability to pull backcheck results via the Criminal Check Within (Days) filter to help better support internal and external inquiries | Internal |
11.5.2
Go Live: January 16th, 2024
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
| SD-52405 | Improve E&O Integration Monitoring Job | The job is responsible for identifying all records that have been updated in the EasyInsure database for Axis Reinsurance Company issued through the HUB program has been improved to run more efficiently and more frequently | E&O Integration |