Enhancement Release 13.6.0- Licence Lookup Optimization & AODA
13.6.0 Go Live: Feb 18, 2026
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-73459 | Infrastructure- Remove Monaco Security | Infrastructure enhancements were completed to remove security constraints and improve system flexibility | Infrastructure- Security |
SD-75582 | Security- Prompt Multi Factor Authentication for Critical Functions- Feature Flag | Security improvements were implemented to prompt MFA for APEXA staff when editing or updating feature flag settings | Enhancement-Security |
SD-75405 | Licence Lookup- Resolve Search with a Partial Licence Number | An issue was resolved where licence lookups were successful using partial licence numbers. This fix ensures licence records are retrieved only when a complete and valid licence number is used for search | Bug Fix- Licences |
SD-75387 | Licence Lookup- Resolve Failure for Complex Username | An issue was resolved where licence lookups for users with complex names were failing. This fix ensures all valid names return a licence record | Bug Fix- Licences |
SD-75811 | Performance- Improve license lookup – Optimize Licence Job | Enhancements were made to the licence monitoring job to prevent false Advisor profile history updates and ensure only valid changes are captured | Licences - Performance |
SD-73558 | AODA - Attestation - Policies & Procedures | 1 instance of guideline 1.1.1 was resolved
1 instance of guideline 1.3.1 was resolved
| Regulatory -AODA |
SD-73617 | AODA - Client Assets- Agreement-Contracts | 3 instances of guideline 1.3.1 were resolved
1 instance of guideline 2.4.7 was resolved
4 instances of guideline 4.1.2 were resolved
| Regulatory -AODA |
SD-73619 | AODA - Client Assets-Packages- Edit Package | 2 instances of guideline 1.3.1 were resolved
2 instances of guideline 2.4.3 were resolved
3 instances of guideline 4.1.2 were resolved
| Regulatory -AODA |
SD-73923 | AODA - Client Assets - Packages - Details | 3 instances of guideline 1.3.1 were resolved
4 instances of guideline 2.4.3 were resolved
3 instances of guideline 4.1.2 were resolved
| Regulatory -AODA |
SD-75161 | AODA - Client Searches-Search-Tasks | 5 instances of guideline 1.3.1 were resolved
2 instances of guideline 1.3.2 were resolved
3 instances of guideline 2.4.3 were resolved
4 instances of guideline 4.1.2 were resolved
| Regulatory -AODA |
SD-75169 | AODA - Client Searches-Search-Tasks | 1 instance of guideline 1.3.1 was resolved
1 instance of guideline 2.4.1 was resolved
1 instance of guideline 2.4.6 was resolved
| Regulatory -AODA |
SD-75389 | AODA - Client View of Advisor & Corporation-Advisor Profile-Credit History | 3 instances of guideline 1.3.1 were resolved
2 instances of guideline 2.4.3 were resolved
1 instance of guideline 3.3.2 was resolved
1 instance of guideline 4.1.2 was resolved
| Regulatory -AODA |
SD-73240 | AODA - Corporate Profile - Contract Request -New Requests | 1 instance of guideline 1.3.1 was resolved
| Regulatory -AODA |
SD-73483 | AODA - Attestation - Documents | 1 instance of guideline 1.3.1 was resolved
1 instance of guideline 2.4.3 was resolved
| Regulatory -AODA |
SD-74704 | AODA- Centralize Loading Indicator on Contract Search Result Page | An issue was resolved where long profile names were no longer being truncated. This fix ensures long profile names are now consistently truncated | Regulatory -AODA |
SD-75510 | AODA-Truncate Long Profile Names | An issue was resolved where long profile names were no longer being truncated. This fix ensures long profile names remain truncated | Regulatory -AODA |
Guideline List -Affected Guidelines
Description |
|---|
1.1.1 - Non-text Content - Level A - All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed below |
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.6 Headings and Labels - Headings and labels describe topic or purpose. |
2.4.7 Focus Visible - Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible |
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 |