Enhancement Release 10.0 -Bill 96 -Phase 1

Enhancement Release 10.0 -Bill 96 -Phase 1

In order to ensure compliance with Bill 96, the following changes will be made in Phase 1 to ensure that all Quebec residents are first presented with French contracts and contracting requirements, regardless of their previously identified language preference

All other parties in the contract will continue to view the contract (other than documents and agreements) based on their Preferred language (SD-46904)

Legacy Contracts

SD–45851

Legacy contracts for target parties who have a current address in Quebec (business or residential) will import with a language setting of French for:

  • New advisors or Corporation 
  • When merging records into an existing advisor or Corporation profile 

The entire contract will appear to the user in French (header section and all tabs)

New Contracts

SD-45866

All contracts for target parties who have a current address in Quebec (business or residential) will default to a language setting of French.

This applies to all contracts created in Apexa:

  • Contracts created using the Related Contract option 
  • Contracts created through an existing relationship 
  • Contracts created by adding an Advisor or Corporation to a contract 
  • Contracts created by the target party directly
  • Contract requests created when a net new Single-Advisor Corporation or Multi-Advisor Corporation on-boards into the system

The entire contract will appear to the user in French (header section and all tabs)

Process for Requesting an English Contract 

SD-46618, SD-46531

As part of Phase 1 we will have a temporary process in place when a Quebec target party has been presented with the French version of the contract or contracting requirement and they would like to opt into the English version.

In order to facilitate the request, we ask them to email us through a new banner on the contracting screen which will be available to all target parties when the contract is assigned to them. 

By actioning the banner, the target parties email client will launch with a pre-populated email template.


Once all required details are received, we will process the request within 1 business day. 

This process will: 

  1. Update the language on the contract​ from French to English
  2. Add a system generated comment to indicate the language change from French to English visible to all parties
  3. Add a system generated comment to indicate which requirements were removed visible to partner organizations:
    • If the unfulfilled requirements were part of a package, the entire set of requirements will be removed and the name of the package will be listed.
    • If the requirement was added directly to the contract, the question itself or name of document or agreement that will be listed. 
  4. Re-assign the contract back to the client who added the package/requirement
  5. Existing triggers will create a task when the contract is re-assigned (the is also a new Comment Type = Language Change Request available to build a trigger off of in the Contract>Search area)
  6. The client will need to reattach the package or requirement and send it back to the target party

 

Historical & Pending Records 

SD-46320

Any new requirement that is added to an existing contract for a Quebec target party must be presented in French first.

When Phase 1 goes live in production, the system will identify any existing contracts with a language setting of 'English' and a Quebec target party and update that setting to 'French'.

If ​there are outstanding and unfilled requirements, they will be removed from the contract so they can be re-attached in French.

  • If the unfulfilled requirement was part of package the entire set of requirements will be removed
  • If the unfulfilled requirement was added directly to the contract, only that individual requirement will be removed

An  unfulfilled requirement includes: 

  1. Requirement that has been attached, but not yet sent backwards 
  2. Requirement that has been sent backwards, but is not fully fulfilled 
  • We will not remove requirements that have already been completed by the target party even if there are other parties within the contracting chain who have not yet completed them
  • Historically fulfilled requirements will be maintained in the language they were provided in.  However, the wording of questions will display to the target party in the updated language of the contract.
    • If the previous question was responded to in English, the response and any attachments will be captured 'as is', but the wording of the question will appear in French.
    • If the user opts back into the English version, the wording will be updated to display English

Once the unfulfilled requirements are removed, the system will

  1. Update the language on the contract​ from English to French
  2. Add a comment to indicate the language change from French to English
  3. Follow steps 3-6 as outlined above

Overview of Workflow

Additional Changes

Bug Fixes: 

SD-45643, SD-45644, SD-46377, SD-45442, SD-45843, SD-46533

  • Pushing Package revisions has been temporarily disabled 
  • Users invited from InTrust with ‘French’ designated as their preferred language will now see the registration page in French
  • Users invited with ‘French’ as their preferred language, will now see the registration page in French. 
  • The Subject of the French Registration email is now correct. 

Areas to Test

  • Validate a legacy contracts for a Quebec target party are imported in French 
  • Validate that new contracts created for a Quebec target party are created in French 
  • Any target party can view and action the banner when the contract is sent to them 
  • Validate that when actioning the banner a pre-populated email will be generated with defined subject line and body 
    • Please do not submit the email to us as it will create a ticket in our Help Desk and we will not be running actioning these requests during UAT