Enhancement Release 13.7.0- Licence Lookup Optimization & AODA

SD-75583

Security- Prompt Multi Factor Authentication for Critical Functions- Security Settings

Security enhancements were implemented to prompt multi‑factor authentication (MFA) for APEXA staff when editing or updating security settings

Enhancement-Security

SD-75584

Security- Prompt Multi Factor Authentication for Critical Functions Password Change

Security enhancements were implemented to prompt multi‑factor authentication (MFA) for APEXA staff during password changes

Enhancement-Security

SD-76014

Security- Prompt Multi Factor Authentication for Critical Functions- Email Change

Security enhancements were implemented to prompt multi‑factor authentication (MFA) for APEXA staff when making email changes

Enhancement-Security

SD-76019

Security- Prompt Multi Factor Authentication for Critical Functions- Add New User+ Edit an Existing User

Security enhancements were implemented to prompt multi‑factor authentication (MFA) for APEXA staff when adding new users or editing existing users

Enhancement-Security

SD-76021

Security- Prompt Multi Factor Authentication for Critical Functions- Create New + Edit Existing User Roles

Security enhancements were implemented to prompt multi‑factor authentication (MFA) for APEXA staff when creating new roles or editing existing roles

Enhancement-Security

SD-76025

Security- Prompt Multi Factor Authentication for Critical Functions- Delete User

Security enhancements were implemented to prompt multi‑factor authentication (MFA) for APEXA staff when deleting users

Enhancement-Security

SD-76026

Security- Prompt Multi Factor Authentication for Critical Functions-Reactivate User

Security enhancements were implemented to prompt multi‑factor authentication (MFA) for APEXA staff when reactivating users

Regulatory -AODA 

SD-75815

Enhancement- Update Licence Lookup Instructions for BC-Individual

Licence lookup functionality was updated to support the retrieval of individual British Columbia licence records following a change to the BC portal, improving data accuracy and reducing manual entry for advisors

Licence Lookup

SD-76039

Enhancement- Update Licence Lookup Instructions for BC-Corporations

Licence lookup functionality was updated to support the retrieval of corporate British Columbia licence records following a change to the BC portal, improving data accuracy and reducing manual entry for advisors

Licence Lookup

SD-76124

Performance- Licence Lookup- Implement Retry Policy for Transient Timeout Exceptions in "UpdateLicencesFromIntegration"

A retry policy was implemented for the licence monitoring process to handle transient timeout exceptions, improving integration reliability and reducing failed licence updates

Licence Lookup

SD-76114

Performance – Licence Lookup – Licence Health Check Optimization

The licence integration health check was updated to support the new once‑per‑day job execution model, improving monitoring accuracy and reducing unnecessary processing

Bug Fix- Licences

SD-73535

AODA - Attestation - Personal Information

1 instance of guideline 1.1.1 was resolved

• Non-text Content

2 instances of guideline 1.3.2 were resolved

• Meaningful Sequence

  • "Personal Information" screen - "Name Change" link

  • "Personal Information" screen - Previous & Next Buttons

2 instances of guideline 2.4.3 were resolved

• Focus Order

1 instance of guideline 4.1.2 was resolved

• Name, Role, Value

  • "Personal Information" screen - Step 1/14 Progress bar

Regulatory -AODA 

SD-72857

AODA - Advisor Profile - History - Request Details

5 instances of guideline 1.3.1 were resolved

• Info and Relationships

2 instances of guideline 1.3.2 were resolved

• Meaningful Sequence

  • Comments section -> Cancel button

  • Comments section -> Cancel & Save Buttons

1 instance of guideline 1.4.10 was resolved

• Reflow

  • Request Details screen -> "Request ID" section & tables

3 instances of guideline 2.4.3 were resolved

• Focus Order

  • Modals / dialog after clicking the "Rescind" button

1 instance of guideline 2.4.4 was resolved

• Link Purpose (In Context)

  • Contract Requests - History Screen ->
    Requests Details Screen -> Comment section -> "Click here"

1 instance of guideline 2.4.7 was resolved

• Focus Visible-Issue

  • Contract Requests - History Screen ->
    Requests Details Screen -> Comment section -> "Click here"

5 instances of guideline 3.3.2 were resolved

• Labels or Instructions

  • Section below the "Request Details" title

  • Comments -> "Filter" button

  • Comments section -> Filter search field

  • The select box appear after clicking the filter button -> Select field

    • Note Type

4 instances of guideline 4.1.2 were resolved

• Name, Role, Value

  • The select box appear after clicking the filter button -> Select field

    • Note Type

Regulatory -AODA 

SD-72919

AODA - Client - Contract Request-New Two-Party Contract

3 instances of guideline 1.1.1 were resolved

• Non-text Content

  • Client - Contract Requests - New Request -> "New two-party contract" Screen -> Select field

    • Request Type

  • Client - Contract Requests - New Request -> "New two-party contract" Screen -> Select field

    • Please select the name of the company you wish to work with

3 instances of guideline 1.3.1 were resolved

• Info and Relationships

1 instance of guideline 2.4.1 was resolved

• Bypass Blocks

  • Client - Contract Requests - New Request -> "New two-party contract" Screen -> Select field info icon

    • Please select the name of the company you wish to work with

3 instances of guideline 3.3.2 were resolved

• Labels or Instructions

  • Client - Contract Requests - New Request -"New two-party contract" - form - "Request Type" dropdown field

  • Client - Contract Requests - New Request -> "New two-party contract" Screen -> Select field

    • Please select the name of the company you wish to work with

  • Client - Contract Requests - New Request -> "New two-party contract" Screen -> Select field

    • Request Type

    • Please select the name of the company you wish to work with

1 instance of guideline 4.1.2 was resolved

• Name, Role, Value - Issue

Regulatory -AODA 

SD-73641

AODA - Client Assets - Logo- Edit Logo

3 instances of guideline 1.3.1 were resolved

• Info and Relationships

  • Assets - Logo - "Revision" screen - "Tags" input list

2 instances of guideline 2.4.3 were resolved

• Focus Order

  • Assets - Logo - "Revision" screen - language change Modal (English)

  • Assets - Logo - "Revision" screen - language change Modal (French)

1 instance of guideline 2.4.4 was resolved

• Link Purpose (In Context)

4 instances of guideline 4.1.2 were resolved

• Name, Role, Value

  • Assets - Logo - "Revision" screen - "Tags" input value

  • Assets - Logo - "Revision" screen - "Tags" close icon in input

  • Assets - Logo - "Revision" screen - language change Modal (English)

  • Assets - Logo - "Revision" screen - language change Modal (French)

Regulatory -AODA 

SD-74222

AODA - Client Assets -Package- New Package - Settings

2 instances of guideline 4.1.2 were resolved

• Name, Role, Value

  • New Package - "Settings" screen - "Search" field in the Retention Period (Years)'s dropdown list

  • New Package - "Settings" screen - "Search" field in the "Target Party Type" dropdown list

Regulatory -AODA 

SD-74238

AODA - Client Assets -Agreement- Edit

2 instances of guideline 1.3.1 were resolved

• Info and Relationships

  • Agreements (HTML) - "Revision" screen - Table Header last column

1 instance of guideline 1.3.2 was resolved

• Meaningful Sequence

  • Agreements (HTML) - "Revision" screen

    • Preview as Advisor &

    • Preview as Corporation Buttons

1 instance of guideline 2.1.1 was resolved

• Keyboard

  • Agreements (HTML) - "Revision" screen - Edit screen - "Click Here" link

1 instance of guideline 2.4.3 was resolved

• Focus Order

1 instance of guideline 2.4.7 was resolved

• Focus Visible

  • Agreements (HTML) - "Revision" screen - Edit screen - "Click Here" link

1 instance of guideline 3.3.2 was resolved

• Labels or Instructions

  • Agreements (HTML) - "Revision" screen - Edit screen - Input Field's Label

    • Logo

    • Section

    • Preview

4 instances of guideline 4.1.2 were resolved

• Name, Role, Value

  • Agreements (HTML) - "Revision" screen - "Edit" Button

  • Agreements (HTML) - "Revision" screen - Edit screen - "Add" Button

  • Agreements (HTML) - "Revision" screen - Edit screen - "Delete" Button

  • Agreements (HTML) - "Revision" screen - Edit screen - "Delete Popup" from delete button in the table

Regulatory -AODA 

SD-76340

AODA - Contracting Requests Approval - Pending Contracts

1 instance of guideline 3.3.2 was resolved

• Labels or Instructions

Regulatory -AODA 

SD-73410

AODA - Attestation - Associated Corporations

2 instances of guideline 1.1.1 were resolved

• Non-text Content

  • Associated Corporations" screen - Step 2/14 Progress bar

  • "Associated Corporations" screen - Table column data

    • Contact Person column data

    • Setup completed column data

Regulatory -AODA 

SD-75807

Technical Item-Add LogRequest attribute with performance logging to all MVC controllers 

Performance logging was enhanced by adding a LogRequest attribute across all web controllers, improving request traceability and enabling more granular performance analysis

Technical Item - Enhancement

SD-76115

Technical Item – Enhance File Upload Error Handling When Backend Is Unreachable

File upload error handling was improved to better manage exceptions when the backend is unavailable, reducing user‑visible errors and improving system resilience

Technical Item - Enhancement

SD-76112

Technical Item- Enhance Licence Integration Logging

Licence integration logging was enhanced with request correlation and more granular error classification, improving traceability, diagnostics, and supportability of integration failures

Technical Item - Enhancement

SD-76271

Technical Item-Create New DataDog Alert to monitor CheckDocumentScope Timeouts

A new DataDog alert was created to monitor documents search/ upload timeouts, enabling earlier detection of issues and improving operational visibility and response

Technical Item - Monitoring

SD-76480

Technical Item- Data Dog- Create Alert for Low Disk Space in Central CAN

A new DataDog alert was created to monitor low disk space in the Central CAN environment, enabling earlier detection of capacity issues and supporting platform availability and operational stability

Technical Item - Monitoring

SD-76498

Technical Item - CI/CD - Stabilizing intermittent failures in testing that impact the Testing Pipeline

Improvements were made to reduce intermittent test failures, helping ensure smoother and more reliable releases

Technical Item - Enhancement

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 

1.4.10- Reflow - Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:

• Vertical scrolling content at a width equivalent to 320 CSS pixels.

• Horizontal scrolling content at a height equivalent to 256 CSS pixels.

Except for parts of the content which require two-dimensional layout for usage or meaning

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.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