Enhancement Release 12.12.0 -Moving to Quebec
Timeline
Law 14 -Moving to Quebec
Due to Law 14, there is a legal obligation for all contracting requirements to be presented in French first for residents of Quebec.
Currently all new contracts for Quebec residents are created in French first with the option on a contract by contract basis, to opt into English by submitting a Contract Language Change request.
Historical contracts for those residing in Quebec were also updated at the time of Law 14 implementation.
However, Advisors or Corporations which are moving to Quebec after that update, require that their historical contracts also be updated to French. To ensure any new requirements are received in French first with the option to opt into English
Functionality will be introduced to:
Present and allow users to complete and submit outstanding requirements for English so they are not removed.
Update English contracts to French using the Contract Change Language Workflow which will be initiated based on the type of requirements that have been previously been attached to the contract (unilingual or bilingual) and the current party on the contract.
English Contracts Assigned to Target Party
When an Advisor or Corporation edits or adds a new address to the province of Quebec (through Attestation or regular profile updates), the following message will appear to inform them of the contracting requirements in Quebec.
If there are any currently assigned to the target party which have unfulfilled contracting requirements. The associated contracts will appear with an extended message. The user will have the opportunity to complete these requirements prior to fully saving the address change.
If the user selects 'OK' and saves their address, outstanding English requirements will be removed and will need to be re-completed by the Advisor or Corporation
Otherwise, the user can select the 'Application ID(s)' to navigate directly to the contract(s) or select 'Cancel' in order to complete and submit the contract to the party above prior to saving their Quebec address.
If the English contracts are assigned to another party (with or without outstanding requirements):
Any unfulfilled contracting requirements in English will be removed and the contract language will be updated to French
English requirements that have already been completed by the target party will not be removed. Even if there are other parties within the contracting chain who have not yet completed them.
Historically completed requirements will be maintained in their original language
Error Handling
If for any reason all of the English contracts for an Advisor or Corporation cannot be changed to French:
The system will make 3 attempts to process the records.
Upon failure all contracts will be rolled back to their original state and will remain in English.
The address change to Quebec will not be saved and an error message will be displayed to alert the user.
Removing Unilingual Requirements
A unilingual/non-bilingual requirement is defined as any package or ad hoc requirement for which unilingual components are available
Non-Fillable (Read/Accept) requirements are available in one language only
Fillable/Signable requirements are available in one language only
Questions are available in one language only
Regardless of who the contract is assigned to, if there are English requirements outstanding on a contract to which unilingual requirements have been attached and there are unfulfilled:
The unfulfilled requirements will be removed
The contract will be returned to the client that added the package or to the client that added the most recent ad hoc requirement
The following comments will be captured on the contract:
Un-editable, bilingual comment to capture the language change with a comment type of Language change
Un-editable, bilingual comment to capture consent with a comment type of Language change
Un-editable, bilingual comment that lists all the removed requirements (name of package or name of ad hoc requirement) with a comment type of Removed Requirement(s) *This comment will be visible to clients only
A bilingual banner message will be displayed to the target party informing them that the contract has been returned to the billable party for action
This banner message will be dynamic and will reflect the name of the current party
This banner will be removed when the contract is sent backwards to the target party
Removing Bilingual Requirements
A bilingual requirement is defined as any package or ad hoc requirement for which bilingual components are available
Non-Fillable (Read/Accept) requirements are available in both English & French
Fillable/Signable requirements are available in both English & French
Questions are available in both English & French
Regardless of who the contract is assigned to, if there are English requirements outstanding on a contract to which bilingual requirements have been attached and there are unfulfilled:
The system will automatically remove the requirement and re-attach it in the alternative language
No client intervention is required
Bilingual Packages [Contract, Requirement. Maintenance and Transfer Packages]:
The same version of the bilingual package that was removed will be reattached in the opposite language
If a revised version of the bilingual package exists, and it has been pushed down to related contracts by the billable party, the revised (current) version will be reattached to the contract
If a revised version of the bilingual package exists, and it has NOT been pushed down to related contracts, the same version of the package removed from the contract will be re-attached in the opposite language.
Bilingual Ad Hoc Requirements [Documents and Agreements]:
The same version of the ad hoc requirement that was removed will be reattached in the opposite language
The following comments will be captured on the contract (same as above):
Un-editable, bilingual comment to capture the language change with a comment type of Language change
Un-editable, bilingual comment to capture consent with a comment type of Language change
Un-editable, bilingual comment that lists all the removed requirements (name of package or name of adhoc requirement) with a comment type of Removed Requirement(s) *This comment will be visible to clients only
Workflow
Go Live: April 9th, 2025
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-65211
| Moving to Quebec -English Contracts With Outstanding Requirements Assigned to Target Party -Pop-Up | This change is in an disabled state When an advisor or corporation edits their current residential or business address to Quebec (during Attestation or regular profile maintenance) and clicks ‘Save’, they will be presented with a pop up to display: “Due to Law 14, as a resident of Quebec, you will be presented with the French version of all your contracts going forward. You will have the option of requesting the contracts in English after the fact.” If they also have English contracts currently assigned to them which have outstanding requirements, a second message will be displayed “When you Save this change, any incomplete requirements will be removed from the following English contracts. Please complete the requirements and submit the contracts prior to saving” The following fields will be displayed:
User will have the option to select ‘Ok’ to save their changes or ‘Cancel' to return to the previous screen. | Enhancement -Moving to Quebec |
SD-59386 | Moving to Quebec -English Contracts With Outstanding Requirements | This change is in an disabled state From the pop-up in SD-65211, users have the option to Cancel, or navigate directly to the contract to submit requirements prior to saving. However, once the address is saved by clicking ‘OK' any outstanding requirements from these contracts will be removed and the language on the contract will update to French. If Unilingual requirements are removed they will need to be re-added by the client who added them and the contract will be automatically assigned back to the party who added the package or adhoc requirement. If Bilingual requirements are removed they will be re-added automatically by the system and the current party will remain the same. The changes will be captured in comments on the contract the same as the existing Contract Language Change functionality. Which include a comment to recognize the language change, consent and list of packages or ad hoc requirements which were removed. The contracts currently assigned to the target party will be prioritized to be updated to French first, you may experience a delay while the system updates contracts assigned to other parties. |
|
SD-59385 | Moving to Quebec -English Contracts with No Outstanding Requirements | This change is in an disabled state When an advisor or corporation edits their current residential or business address to Quebec, any English contracts which do not have any pending requirements currently assigned to the target party, will be updated to French. The current party will remain the same. Any previously fulfilled requirements will remain in their original language even though the language on the contract has changed. | Enhancement -Moving to Quebec |
SD-55297 | Moving to Quebec -Bug -Address Not Saving | This change is in an disabled state The address change to Quebec was not saving for newly onboarded Advisors or those who have had their attestation expired. This issue has been resolved | Enhancement -Moving to Quebec |
SD-66558 | Moving To Quebec -Bug -Contract Language Not Updating | This change is in an disabled state In certain scenarios, when the contract was assigned to the target party, the outstanding requirements were either not being removed or language on the contract was not updating to French This issue has been resolved | Enhancement -Moving to Quebec |
SD-66264 | Pushing Revision -Disable Functionality for Maintenance Packages | This change is in an disabled state Functionality that allowed revisions to be pushed to maintenance packages was reverted as this package type is handled differently in the backend and the change were not compatible with the business logic | Enhancement -Pushing Revisions |
SD-66465 | Pushing Revisions -Improve French Translation | This change is in an disabled state When pushing revisions to applicable contracts, the message was improved to indicate “Appliquer la révision de la trousse” | Enhancement -Pushing Revisions |
SD-65894 | Pushing Revisions -Automated Tests | This change is in an disabled state Development of automate tests to be execute any time changes made to this area of the application were implemented to prevent unexpected impact of future updates | Enhancement -Pushing Revisions -Technical Item |
SD-66036 | CITS API | Improved performance related to the function which allows clients to pull AdvisorPriorName. This change may improve overall CITS Performance | CITS -Performance |
SD-65714 | CITS API | CITS responses were updated to ensure updates to licence type or shareholder information is not transmitted when the contractual relationship is terminated | CITS -Bug |
SD-62006 | InTrust -Contract Search -Performance | To address performance issues in this area, we have introduced a change in behavior. The search will no longer run automatically each time a character is typed. Instead, a search icon has been added. When a user types a character, if they would like to conduct a search they can either select ‘Enter’ on their keyboard or click the ‘Search’ icon | InTrust -Performance |
SD-62065 | InTrust -Advisor Search -Performance | To address performance issues in this area, we have introduced a change in behavior. The search will no longer run automatically each time a character is typed. Instead, a search icon has been added. When a user types a character, if they would like to conduct a search they can either select ‘Enter’ on their keyboard or click the ‘Search’ icon | InTrust -Performance |
SD-23945 | Contract Packages -Grant Staff Access | Access to review the contract package attached to a contract has been extended to our internal staff portal to improve troubleshooting and turnaround on related tickets | Internal Enhancement |
SD-65833 | DB Optimization | A secondary email audit table which was not being used was removed in order to free up space in the database to improve overall performance | Technical Item |
SD-66491 | Technical Cleanup | Various cleanup activities to address technical debt in the application such as
| Technical Item |
SD-15307 | Technical Monitoring | Improved system monitoring by creating custom metrics to monitor Apexa and InTrust database and table growth | Technical Item |