Release 11.6.0
Go Live: Jan 24, 2024
Ticket # | Summary | Description | Area of Impact |
---|---|---|---|
SD-50272 | PSG -Integration to new eSignature Vendor | This change is in a disabled state Apexa has integrated with a new E-signature vendor for signing agreements. The look, feel and business logic remains the same with slight changes to the user interface. Improvements have been made to the agreement signing process for more seamless user experience & bottle necks previously experienced have been removed | Contracting - Enhancement |
SD-52727 | PSG -Preferred language for eSignature iFrame | This is a continuation of SD-50272 above to allow users view the iframe of agreements in their preferred Apexa language. Hence, the iframe buttons, popup and messages will be displayed in the user's preferred language for clearer communication. | Contracting - Enhancement |
SD-51983 | Non-billable parties adding ad hoc questions | The option for Non-billable corporations to add ad hoc questions to contract has been removed. When added, it would result in the inability to then assign the contract to the target party or forward to the client and the contract would need to be reset | Contracting -Bug |
SD-51182 | Law 14 -Phase 2B -Ad Hoc Multiple-choice Questions | The Contract language change request process has been enhanced to provide more information to clients regarding ad hoc questions that were removed as part of the Language Change process. The Removed Requirement (s) comment will now specifies the type of ad hoc questions (if any) that was removed e.g. Multiple choice, Yes/No etc in addition to the options if Multiple choice was the type. | Regulatory -Law 14 -Phase 2B |
SD-51840 | Law 14 -Phase 2B -Ad hoc Documents & Agreements dropdown field not reset | Following the enhancement where all ad hoc documents or agreements for the target party must be added in the language of the contract SD-46279 (v11.5.0), the dropdown list was not refreshed when attempting to add an incompatible document or agreement. This has been resolved | Contracting -Bug |
SD-51932 | Law 14-Phase 2B Pop-up not shown for newly added QC address | This change is in a disabled state 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 SD-48060 (v11.5.0). The pop-up which provides the user with an opportunity to complete contracting requirements of listed English 'Inflight' contract(s) prior to saving their address change was not displayed correctly. This has been resolved | Regulatory -Law 14 -Phase 2B |
SD-52051 | Law 14 -Phase 2B -English fulfilled contracts on popup | This change is in a disabled state Also in line with SD-48060 (v11.5.0), English contracts that had been fulfilled by the Target party but not yet submitted were incorrectly listed in the popup when a user was editing their current address to Quebec. This has been resolved | Regulatory -Law 14 -Phase 2B |
SD-52204 | Penetration Test Finding: Enforcing Strict Web Security on Apexa | A Medium finding from our annual penetration test which allowed an unencrypted connection vulnerability was resolved | Application Security |