Enhancement Release 14.1.0 – CITS/ API Enhancement, Licence Lookup Optimization & AODA
14.1.0 Go Live: Jun 24, 2026
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-79370 | CITS - Resolve Email Change Error in CITS Feeds
| A defect was resolved to prevent errors in CITS feeds when an email address is updated. This ensures the updated email address is captured accurately and reflected correctly in CITS | CITS- Bug Fix |
SD-79383 | Email Triggers - Prevent Erroneous Email Task Generation | A defect was resolved to prevent erroneous email tasks from being generated when an email address is updated. This ensures email-related tasks are triggered only when appropriate | Triggers- Bug Fix |
SD-79453 | Performance - Resolve High Latency Issues in Production | A performance fix was implemented to resolve high latency issues in production. This improves system responsiveness and overall user experience | System Performance Fix |
SD-79382 | CITS/API - Improve Performance | CITS feed processing was updated to improve the performance of some endpoints, supporting faster processing and improved reliability | CITS/API Enhancement |
SD-79695 | Licence Lookup – Resolve Lookup and Monitoring Issue for Manitoba Corporation | A defect was resolved to correct lookup and monitoring issues for Manitoba Corporation licences. This improves licence monitoring accuracy and supports more reliable licence lookup results | Licence Lookup- Bug Fix |
SD-79172 | Licence Lookup - Resolve Lookup and Monitoring Issue for New Brunswick Advisor and Corporation | A defect was resolved to correct lookup and monitoring issues for New Brunswick Advisor and Corporation licences. This improves licence monitoring accuracy and supports more reliable licence lookup results | Licence Lookup- Bug Fix |
SD-72929 | AODA - Contract Requests - Corporate Profile - Contract Request -New Request | 1 instance of 1.1.1 was resolved
2 instances of 1.3.1 were resolved
2 instances of 2.4.1 were resolved
2 instances of 3.3.2 were resolved
2 instances of 4.1.2 were resolved
| Regulatory -AODA |
SD-75285 | AODA - Client View of Advisor & Corporation-Advisor Profile-Name Change History | 1 instance of 1.3.1 was resolved
1 instance of 1.3.2 was resolved
1 instance of 2.4.1 was resolved
1 instance of 2.4.6 was resolved
| Regulatory -AODA |
SD-75315 | AODA - Client View of Advisor & Corporation-Advisor Profile-Date Variation | 1 instance of 1.3.2 was resolved
1 instance of 2.4.4 was resolved
| Regulatory -AODA |
SD-75390 | AODA - Client View of Advisor & Corporation-Advisor Profile History | 1 instance of 1.3.1 was resolved
1 instance of 1.3.2 was resolved
2 instances of 2.4.3 were resolved
1 instance of 2.4.4 was resolved
| Regulatory -AODA |
SD-75714 | AODA - Contracting- Client View- Contract Menu- Packages | 1 instance of 2.4.3 was resolved
| Regulatory -AODA |
SD-75745 | AODA - Contracting- Advisor View- Contract Menu- Requirements- Documents | 1 instance of 2.5.8 was resolved
| Regulatory -AODA |
SD-76066 | AODA - Contracting- Client Profile - External Signer Login Page | 2 instances of 1.3.1 were resolved
1 instance of 2.5.8 was resolved
2 instances of 3.3.1 were resolved
2 instances of 3.3.2 were resolved
2 instances of 4.1.2 were resolved
| Regulatory -AODA |
SD-78466 | AODA - Client Profile - Settings | 1 instance of 1.3.2 was resolved
1 instance of 2.4.2 was resolved
| Regulatory -AODA |
SD-78755 | AODA - Attestation - Licenses | 1 instance of 1.1.1 was resolved
| Regulatory -AODA |
SD-76810 | Contract Request Search Results Table - Add Sorting and Pagination | Contract Request search results were updated to support sorting across all columns and pagination of results. This improves data navigation and makes it easier for users to compare search results | Search Results |
SD-79202 | Technical - Review UpdateCaseSignatures Job Schedule | The job schedule that updates agreement signatures was reviewed to ensure it runs at the appropriate frequency and supports reliable processing of case signature updates | Technical Item- Enhancement |
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.1.1- Keyboard - All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints |
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 |
2.5.8 - Target Size (Minimum) - The size of the target for pointer inputs is at least 24 by 24 CSS pixels |
3.3.1 Error Identification - If an input error is automatically detected, the item that is in error is identified and the error is described to the user in text. |
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 |