Enhancement Release 12.18.0 -Contract Source -Contract Header & AODA
Contract Source -Contract Header
Contract source has been added to the Contract Header
12.18.0 Go Live: August 13th, 2025
Ticket # | Summary | Description | Area of Impact |
|---|---|---|---|
SD-62677 | Contract Header -Contract Source | Contract source has been added to Contract Header. Clients will have the ability to see whether the contract was created from ‘InTrust’ (legacy contracts imported into Apexa) or ‘Apexa’ (contracts created directly in Apexa) | Enhancement -Contract Header |
SD-70524 | Banking Search -Banking Extract Extract | The banking extract has been updated display the same Selling Codes as on the UI. Previously, the extract was populating with selling codes when the client was the top party on the contract, however the UI displays all selling codes where the client is implicated. The information in extract displays the same values as in the UI. | Bug Fix -Banking Search -Extract |
SD-70500 | Contract Search -Staff Portal | When completing a contract search in the Staff Portal, Apexa staff were seeing leading commas in the Selling Code column in the UI. This issue has been resolved | Bug Fix -Internal -Contract Search Results |
SD-69750 | AODA -Corporation Profile -Security Settings | 4 instances of guideline 1.3.1 were resolved
2 instances of guideline 2.5.3 were resolved
4 instances of guideline 4.1.2 - Name, Role, Value were resolved
| Regulatory -AODA |
SD-69753 | AODA -Corporation Profile -Users | 3 instances of guideline 1.3.1 were resolved
4 instances of guideline 1.3.2 were resolved
1 instance of guideline 2.1.1 was resolved
4 instances of guideline 2.4.3 were resolved
6 instances of guideline 2.5.3 were resolved
3 instances of guideline 3.3.2 were resolved
| Regulatory -AODA |
SD-69751 | AODA -Corporation Profile -Roles | 4 instances of guideline 1.3.1 were resolved
2 instances of guideline 1.3.2 were resolved
2 instances of 1.4.3 were resolved
1 instance of guideline 2.1.1 was resolved
2 instances of guideline 2.4.3 were resolved
2 instances of guideline 2.5.3 were resolved
2 instances of guideline 4.1.2 were resolved
| Regulatory -AODA |
SD-69755 | AODA -Corporation Profile -Settings | 2 instances of guideline 1.4.10 were resolved
3 instances of guideline 2.5.3 were resolved
4 instance of guideline 4.1.2 were resolved
| Regulatory -AODA |
SD-70001 | AODA -Corporation Profile -Internal Branches | 3 instances of guideline 1.3.1 were resolved
6 instances of guideline 1.3.2 were resolved
6 instances of guideline 2.1.1 were resolved
6 instances of guideline 2.4.3 were resolved
| Regulatory -AODA |
SD-70899 | Reporting | Generate Activity Report for all clients | Reporting |
SD-70087 | Technical | A new script was created to improve monitoring of timeouts in the InTrust search | Technical -Internal |
SD-69921 | Technical | Implement environment auto-scaling to additional webservers in UAT environment | Technical -Internal |
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 |
1.4.3 - Contrast (Minimum) - The visual presentation of text and images of text has a contrast ratio of at least 4.5:1 |
1.4.10 - Reflow - Content can be presented without loss of information or functionality, nd without requiring scrolling in two dimensions for:
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.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.5.3 - Label in Name - Level A(Added in 2.1) - For user interface components with labels that include text or images of text, the name contains the text that is presented visually |
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 |