Enhancement Release 13.11.0 & 14.0.0- Licence Lookup Optimization & AODA
13.11.0 & 14.0.0 Go Live: Jun 3, 2026
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-75152 | Security – Replace Username as Primary Key in the Database | Username was replaced as the primary key in the database, enabling the use of a dynamic unique identifier instead. This change also allows users to reuse a previously associated email address in their Apexa profile | Security |
SD-75159 | Security- Enable Password History Enforcement | Password history functionality was updated to prevent users from reusing their last 5 passwords on Apexa, improving account security | Security |
SD-77135 | Licence Lookup - Insert A New Licence Record for Future Dated Licences When Current Valid Licence Is Active | Licence lookup functionality was updated to allow future dated licences to be added while an active licence remains valid, ensuring all available licences are displayed on Apexa and preventing gaps in licence history | Licence Lookup |
SD-78347 | Licence Lookup – New Brunswick - Update Licence Type for Corporations | Licence type data was corrected for corporation profiles to ensure profile accuracy on Apexa. | Licence Lookup |
SD-76974 | Licence Lookup - Standardize Licence Upload Process for Expired Licences- Lookup & Manual Process | Licence lookup functionality was updated to allow expired licences to be added through the lookup process and displayed consistently with manually uploaded expired licences | Licence Lookup |
SD-78392 | Equifax -Update Data Mapping to Populate Rate Change Information Correctly | Equifax data mapping was updated to populate rate change information in the correct credit history field, improving data accuracy on Apexa | Equifax- Bug Fix |
SD-74777 | AODA - Client Searches-Banking Information -Search | 1 instance of 1.3.2 was resolved
| Regulatory -AODA |
SD-75165 | AODA - Client Searches-Search-E&O | 1 instance of 2.4.1 was resolved
1 instance of 2.4.6 was resolved
| Regulatory -AODA |
SD-75166 | AODA - Client Searches-Search-Licenses | 1 instance of 2.4.1 was resolved
1 instance of 2.4.6 was resolved
| Regulatory -AODA |
SD-75167 | AODA - Client Searches-Search-Name Change | 1 instance of 3.3.2 was resolved
1 instance of 4.1.2 was resolved
| Regulatory -AODA |
SD-75314 | AODA - Client View of Advisor & Corporation-Advisor Profile-Credit History | 1 instance of 1.3.2 was resolved
| Regulatory -AODA |
SD-75341 | AODA - Client View of Advisor & Corporation-Advisor Profile-Name Change-History-Profile Date | 1 instance of 1.3.2 was resolved
| Regulatory -AODA |
SD-75388 | AODA - Client View of Advisor & Corporation-Advisor Profile-Background | 1 instance of 1.3.2 was resolved
| Regulatory -AODA |
SD-78603 | AODA - Client Profile - Dashboard-Outstanding | 1 instance of 2.4.3 was resolved
| Regulatory -AODA |
SD-78624 | AODA - Client Profile - Profile - Banking Information | 1 instance of 2.4.4 was resolved
1 instance of 4.1.2 was resolved
| Regulatory -AODA |
SD-78691 | AODA - Advisor Corporation - Dashboard - Credit History | 1 instance of 4.1.2 was resolved
| Regulatory -AODA |
SD-78708 | AODA - Contract Requests - Corporate Profile - Contract Requests - History | 1 instance of 1.3.2 was resolved
1 instance of 1.3.2 was resolved
| Regulatory -AODA |
SD-77502 | Technical Item - Delete Unused Tags in Datadog After Enabling Auto Scaling in PRD | Unused Datadog tags were removed after enabling auto scaling in PRD to reduce monitoring noise and improve tagging consistency. | Technical – Auto Deployment
|
SD-78678 | Technical Item - Monitoring - Correct Licence HealthCheck Progress Calculation | Licence health check monitoring was updated to correct progress checker calculations, preventing false job stalled alerts and improving monitoring accuracy | Technical – Monitoring- Bug Fix
|
SD-79073 | Technical Item - Improve Auto Deployment Validation for Apexa Migration | Auto deployment validation for Apexa migration was improved by adding a connection check, helping identify connectivity issues earlier and reducing the risk of deployment failures | Technical – Auto Deployment
|
Guideline List -Affected Guidelines
Description |
|---|
1.3.1 -Info and Relationships - Information, structure, and relationships conveyed through presentation can be programmatically determined or are available in text |
1.3.2- Meaningful Sequence - When the sequence in which content is presented affects its meaning, a correct reading sequence can be programmatically determined |
2.4.1-Bypass Blocks - A mechanism is available to bypass blocks of content that are repeated on multiple Web page |
2.4.3- Focus Order - If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation; focusable components receive focus in an order that preserves meaning and operability |
2.4.4 - Link Purpose (In Context) - The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general |
2.4.6 - Headings and labels - Headings and labels describe topic or purpose |
3.3.2 - Labels or Instructions - Labels or instructions are provided when content requires user input. |
4.1.2 - Name, Role, Value - For all user interface components (including but not limited to: form elements, links and components generated by scripts), the name and role can be programmatically determined; states, properties, and values that can be set by the user can be programmatically set; and notification of changes to these items is available to user agents, including assistive technologies |