Current Release

Timeline

These changes are in a disabled state pending UAT sign-off by the Governance board

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.

Note: Contracts that are locked by another party will not be updated by this process. In this event the user will not receive an error. Apexa is actively working on a solution to address this issue as it is a requirement that all contracts be flipped to French as part of this process.

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