ATIPXpress Release Notes 26.1.3.0

Product Enhancements

1.1  Casepoint Rebranding

ID #1416387

All references for Opexus have been updated to Casepoint across the system, along with the copyright year. This is a cosmetic change with no impact on functionality.

1.2  Customer Enabled Support Account

ID #1277582

The Customer Enabled Support Admin feature allows you to optionally provide Support representatives with limited access to your Collaboration platform for troubleshooting purposes.  

Support representatives are authenticated via SAML-based Single Sign-On (SSO) using your organization’s identity provider without separate ATIPXpress credentials. SAML configuration maps FirstName, LastName, and EmailAddress attributes. All login and logout actions are fully audited, including unsuccessful attempts.

Click Administration and navigate to Security. Select Customer Enabled Support Admin to display the Customer Enabled Support Admin page shown above.

Select the Customer Enabled Support Admin option to enable Customer Enabled Support Admin access. This will enable it to perform support-related tasks.

NOTE: The Customer Enabled Support Admin feature is visible only for SaaS deployments.

1.3  SaaS Security Hardening

ID #1321288

Multiple security enhancements protect sensitive infrastructure details from SaaS users:  

• Hidden Infrastructure Details: Database names, server paths, scheduler details, and file system paths are now hidden from SaaS non-support users across Administration pages including EDR, Jobs, System Configuration, and System Settings.  

• Hidden Configuration Pages: System configuration pages containing sensitive details (Services Configuration, AWS Comprehend Configuration, Request for Documents Provider Settings, TeleMessage Integration, Global Address List Settings, and EDR Change Password) are no longer accessible to SaaS non-support users.  

• ATIPXpress Sync Configuration: Login URLs and credentials are masked for SaaS users. The page is read-only for SaaS users while Support Admin users retain full access for troubleshooting.  

• Error Log Masking: Sensitive details in error logs (UNC paths, drive paths, database/table/column names, IP addresses) are automatically masked with "****" for SaaS users.  

NOTE: On-premise users and Support Admin users retain full visibility of all infrastructure details and error logs.

1.4  Dedicated System Account for Background Jobs

ID #1428498

All system background jobs now execute under a dedicated system account instead of an administrative user account. Audit Logs now clearly distinguish between manual user actions and system-generated actions, with all background job operations logged as UpdatedBy = System Account.

1.5  Field‑Level Audit Logging  

ID #1368264

Administrators can now enable field-level tracking, configure audit data retention, and review detailed audit activity from a centralized Audit Logs page.

This update introduces field-level audit tracking configuration within the Audit Configuration settings, allowing administrators to control how individual field changes are logged and retained.

You can now enable field-level audit tracking to capture detailed change history for configured fields and define how long this audit data is retained. Once enabled, all tracked field changes are recorded and made available through the Audit Log, providing greater visibility into configuration updates and ensuring compliance with audit and retention requirements.

When field-level audit tracking is enabled, the Action Performed column in the Audit Logs displays detailed change history for each audited action. Each entry follows this format: <tablename> : <columnname> was updated from {OldValue} to {NewValue}. When multiple fields are changed in a single action, each change is separated by a semicolon.

Audit records older than the configured retention period are automatically deleted. System-level user activities are excluded from audit logs.

1.6  Request Page Counts on Request Information

ID #1361256

This update introduces a page overview section on the Request Information screen, providing location-based page counts across three document repositories.

You can now view the total number of pages currently residing in Electronic Document Review, the Review Log, and the Request Folder directly from the Request Information screen. These counts reflect the current state of each location and update dynamically as documents are added or removed, enabling you to assess request progress and document distribution at a glance without navigating to multiple sections.

1.7  PAL Sync Failure Management for Requesters and Requests

ID #1425339

A new Admin-only page has been added under PAL Config to help administrators quickly identify and resolve failed synchronization of requester and request details from PAL to ATIPXpress .

The Requester/Request Sync Failures page provides two views — one for Requester sync failures and one for Request sync failures — each displayed in a grid layout with the following columns:

• Resync — action to re-initiate syncing for the failed entry

• Identifier — Requester ID or Request ID

• Requester Details — associated requester information

• Status — current sync status

• Sync Error — the error message describing the failure reason (with a copy action for troubleshooting)

• Attempts — number of resync attempts made

• Last Attempt — timestamp of the most recent resync attempt

Administrators can perform single or bulk resync actions to re-initiate syncing for selected failed entries. Each resync attempt updates the Attempts count and Last Attempt timestamp, and the status is updated in real time during execution.

The grids support filtering with wildcard, search, and sorting, with the default sort displaying the latest failures first. An Export option is available for each grid, respecting applied filters and sorting, and using date-stamped filename conventions.

NOTE: This page is restricted to Admin roles only.

Security Updates

We’ve made the following security updates in this version of ATIPXpress:

Bug Fixes

We’ve addressed the following bugs in this version of ATIPXpress: