Enhancement Release 14.3.0 - System Performance Fixes & AODA

Enhancement Release 14.3.0 - System Performance Fixes & AODA

 

14.3.0 Go Live: Aug 5, 2026

Ticket #

Summary

Description

Area of Impact

Ticket #

Summary

Description

Area of Impact

SD-80453

Advisor Profile – Updated Credit History Category Name

The Bankruptcy section of the advisor profile – Credit History section has been renamed to “Bankruptcy, Insolvencies & Public Records” to accurately reflect all categories of Equifax consumer reports displayed in this section and ensure they are clearly and correctly presented in APEXA.

Advisor- Credit History

SD-80370

MFA Phase 2 - MFA Reauthentication

MFA reauthentication has been set to an eight-hour interval. This reduces unnecessary MFA prompts while maintaining secure access. The change will apply to clients once MFA is enabled for them.

Security- MFA

SD-80778

Performance – Add Indexes to Tables Referencing Document.Document

Database indexes were added to tables referencing Document.Document to improve query efficiency, reduce processing time, and provide faster, smoother document-related operations.

Performance- Documents

SD-80690

Performance – Optimize SnapshotHub.ListCriminalHistory Endpoint

The endpoint performance was optimized to retrieve criminal history records more efficiently, improving response times and providing a faster, smoother user experience.

Performance– Criminal Check

SD-80687

Performance – Optimize SnapshotHub.ListAddresses Endpoint

The endpoint performance was optimized to retrieve address records more efficiently, improving response times and providing a faster, smoother user experience.

Performance– Address Search

SD-80747

Performance – Optimize ComplianceHub.ListComplianceDocumentsByAttestationDocumentId

The endpoint performance was optimized to retrieve compliance documents more efficiently, improving response times and providing a faster, smoother user experience when loading documents associated with an attestation.

Performance - Attestation

SD-80882

Performance – Optimize "CaseBranchReferenceHub.ListBranchOptions" Endpoint

The endpoint performance was optimized to retrieve branch options more efficiently, improving response times and providing a faster, smoother user experience when loading branch selection lists.

Performance– Branch Options

SD-80766

Performance – Optimize OrganizationHub.ListRelatedOrganizationsByFilter

The endpoint performance was optimized to retrieve filtered organization relationships more efficiently, improving response times and providing a faster, smoother user experience.

Performance – Organization Search

SD-80689

Performance – Optimize DocumentController.LicenceDocument Endpoint

The endpoint performance was optimized to retrieve licence documents more efficiently, improving response times and providing a faster, smoother user experience when accessing licence-related records.

Performance – Licence Search

SD-80698

Performance – Optimize  Licence Success Rate HealthCheck Thresholds for Provinces

Provincial licence success-rate health check thresholds were optimized to improve monitoring accuracy, enable earlier identification of licence lookup issues, and support a more reliable user experience.

Performance – Licence Health

SD-80279

Performance – Review and Standardize Extended Endpoint Timeouts

Extended endpoint timeouts were reviewed and standardized to a maximum of 60 seconds, improving configuration consistency, reducing the impact of long-running requests, and supporting a faster, more reliable user experience.

Performance –Searches

SD-78214

Technical Item - Resolve SFTP Upload Pipeline Task Version Warning

SFTP upload pipeline configuration was updated to address task version warnings, improving deployment stability and maintainability

Technical – Monitoring- Bug Fix

SD-74229

AODA - Client Assets -Section -Revisions

1 instance of 1.3.1 was resolved

  • Info and Relationships

    • Last Header Column

    • Law Row Column

Regulatory -AODA 

SD-75340

AODA - Client Search: Advisor Profile History> Documents

1 instance of 1.3.2 was resolved

  • Meaningful Sequence

    • Advisor profile history screen > "Credit check, Background check, Branch codes & Make advisor VIP" buttons

1 instance of 2.4.4 was resolved

  • Link Purpose

    • Advisor Profile History screen> "Profile Documents" Table -> "Documents" Column

Regulatory -AODA 

SD-75409

AODA – Client Search: Advisor & Corporation >Backoffice Codes

1 instance of 1.3.2 was resolved

  • Meaningful Sequence

    • Back Office Codes screen -> "Add/Click here" button

 1 instance of 2.4.3 was resolved

  • Focus Order

 2 instances of 2.4.4 were resolved

  • Link Purpose (In Context)

  • Back-office codes Screen

  • Branch Codes button

 1 instance of 4.1.2 was resolved

  • Name, Role, Value

    • Back Office Codes screen -> "Add" Button

Regulatory -AODA 

SD-75736

AODA - Contracting- Advisor > Contract Menu- Requirements- Banking Information

1 instance of 2.1.1 was resolved

  • Keyboard

    • "Click Here" link in the "Banking Information" comment

Regulatory -AODA 

SD-76892

AODA - InTrust - Advisor Menu - Addresses

1 instance of 1.3.2 was resolved

  • Meaningful Sequence

    • Advisor profile - History - "Credit check, Background check, Branch codes & Make advisor VIP" buttons

1 instance of 3.3.2 was resolved

  • Labels or Instructions

    • Advisor profile screen > "CIPR Number, Preferred Name and Maiden Name" data values

1 instance of 2.4.4 was resolved

  • Link Purpose

    • Advisor Profile "History Documents" screen -> "Profile Documents" Table -> "Documents" Column

Regulatory -AODA 

SD-75716

AODA - Contracting- Advisor > Contract Menu- Requirements- Questions

1 instance of 1.1.1 was resolved

  • Non-text Content

 1 instance of 1.3.1 was resolved

  • Info and Relationships

    • Questions tab -> "Answer" Modal - Agree & Save Button

 2 instances of 2.4.3 were resolved

  • Focus Order

    • Requirements questions" screen -> Popup modal after clicking the "Edit"

 2 instances of 4.1.2 were resolved

  • Name, Role, Value

    • Requirements Questions screen -> Questions Table -> Edits

    • Requirements Questions screen -> Required Document Upload

 3 instances of 4.1.3 were resolved

  • Status Message

  • Questions tab -> "Answer" Modal - Agree & Save Button

Regulatory -AODA 

SD-75953

AODA - Contracting- Corporation> Contracts- Requirements-Question

4 instances of 1.3.1 were resolved

  • Info and Relationships

    • Corporation Requirements Questions -> Comments -> Comments -> Text field -> Search results

    • Corporation Requirements Questions -> Comments -> Select field ->Note type -> Search results

2 instances of 1.3.2 were resolved

  • Meaningful Sequence

    • Corporation Requirements Banking -> Cancel & Save Buttons

    • Corporation Requirements Questions" screen -> "Browse" button

 1 instance of 2.1.1 was resolved

  • Keyboard

    • Corporation> Contracts> Requirements>Banking> Comment

      • "Click Here" link in the "Corporation Requirement Banking"

 1 instance of 2.5.8 was resolved

  • Target Size (Minimum)

    • Corporation> Contracts> Requirements> Questions > Comment- Edit & Delete Buttons in the Table

 1 instance of 3.3.2 was resolved

  • Labels or Instructions

    • Corporation Requirements Questions -> Comments -> Comments -> Text field -> Search results

 6 instances of 2.4.3 were resolved

  • Focus Order

    • Contracts> Requirements> Tag

      • Modal dialog after clicking the "Tag" button

    • Contracts> Requirements> Assign

      • Modal dialog after clicking the "Assign" button

    • Contracts> Requirements> Terminate

      • Modal dialog after clicking the "Terminate Contract" button

    • Contract> Requirement> > Questions > Comment>  “Delete” button in Comment

      • Modal dialog after clicking the "Delete" button in the comment

    • Contract> Profile Header> Effective Date>N/A

      • Modal dialog after clicking the "Effective date" button

1 instance of 2.4.4 was resolved

  • Link Purpose

    • "Click Here" link in the "Corporation Requirement Banking"

 2 instances of 4.1.2 were resolved

  • Name, Role, Value - Level A

    • Corporation Requirements Questions -> Comments -> "Filter" button

    • Corporation Requirements Questions screen -> "Privilege” drop down menu

 1 instance of 4.1.3 was resolved

  • Status Message

    • Corporation Requirements Questions -> Comments -> Select field

    • Note type -> Search results

Regulatory -AODA 

SD-80902

Technical Item - Datadog Maintenance

Datadog monitoring configurations were reviewed and maintained to keep dashboards and alerts current, improving system visibility and supporting timely identification of operational issues.

Technical Item- Monitoring

 

 

Guideline List -Affected Guidelines

Description

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.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.5.8 - Target Size (Minimum) - The size of the target for pointer inputs is at least 24 by 24 CSS pixels

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

4.1.3 -Status Message - In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus