Release Notes 07/19/2026

You can expect up to 15 minutes of downtime to deploy this release.

In This Issue

• Rainmaker Insights

• Client Access UI Config

• MMS with Encryption

• Client Access Authentication

• ACE2ACE Forwarding Enhancements

• Legal Case ETL Fields

Rainmaker Insights

InterProse is pleased to introduce Rainmaker Insights (RI), a new AI-powered reporting tool designed to make it easier to create and customize reports in ACE.

Rainmaker Insights will build upon and improve the reporting functionality currently available through the InterProse ACE SQL Designer and InterProse ACE Inventory Designer. As Rainmaker Insights is introduced, customers will receive guidance and support in transitioning eligible reports to the new reporting tools.

Rainmaker Insights will be rolled out gradually with assistance from the InterProse Support team. Support will contact each customer within the next six weeks to begin discussing the rollout, existing custom reports, and any preparation or training needs.

At this time, do not use the “Convert Jobs” option under Setup → System → Portal Settings until you have met with support regarding Rainmaker Insights configuration and use.

During the introduction, Support will:

• Assist with the conversion of eligible custom reports

• Demonstrate Rainmaker Insights features and reporting capabilities

• Help users understand how to request and refine reports

• Answer questions about available data, report formats, and functionality

• Gather feedback as additional features and improvements are introduced

Rainmaker Insights allows users to describe the information they need in everyday language. The tool then helps build the report, making it easier to explore data without needing to understand complex queries or database structures.

The ACE SQL Designer and ACE Inventory Designer are scheduled to be sunset in April of 2027. The guided rollout is intended to provide customers with time to review existing reports, complete necessary conversions, and become familiar with Rainmaker Insights before that transition.

We look forward to helping you discover a more flexible and intuitive way to access the information you need.

Client Access UI Configuration Update

Over the last few months, we've been updating Client Access User Profile behavior, including updates to Client Access User Interface (UI) Configuration to ensure permissions are managed to prevent failures.

Where we can, we are working with customers to reduce some of the challenges they have experienced as a result of these changes.

In addition, updates have been made to these related help file articles clarifying the current state of behavior:

• Adding Users

• Client Access Configuration

MMS with Encryption

Text message profiles can now be used to send Validation Notices as Encrypted PDF attachments in MMS messages. Supported attachment variables for MMS now include PNG images, PDFs, and password-protected PDFs.

When password protection is applied, the text message automatically replaces the variable with a password hint that tells the recipient what information is required to open the attachment.  

These options are available for ITMS, ITMS TD, and SBT V2.

For more information, see Creating MMS Attachments.

Client Access Authentication

Client Access additional authentication (2FA) can now be configured by Admin Users to define how long a trusted device remains authenticated for Client Access Users.

In addition, Client Access user profiles show 2FA trusted devices along with associated email history and text history.

For more information, see Configuring Client Access Additional Authentication.

ACE2ACE Forwarding Enhancements

ACE2ACE Forwarding has been enhanced to improve account synchronization between connected ACE systems.

When an account is forwarded to another agency:

• All active phone numbers, addresses, and email addresses are now transferred for each demographic.

• When the receiving agency cancels a forwarded account, the account is automatically returned to the originating (sending) agency, where the forwarded placement is marked inactive.

• If the sending agency has configured the onAfterForwardReturnSender trigger and action path, the trigger is initiated when the account is successfully returned.

For more information, see Configuring ACE2ACE Forwarding.

Legal Case ETL Fields

The Legal Case ETL load method has been enhanced to support importing additional Legal Case fields.

For more information, including the complete list of supported fields, see the Legal Cases Layout.

Fixed These:

• There was an issue with client access to File Manager when the folders were renamed. Client folders in File Manager can no longer be renamed.

• Customer logos were sometimes overlayed with a link to InterProse. This linking behavior has been removed.

• There was a scenario where text messages using email profile templates were failing when the client's name included a ampersand. This has been fixed.

• TCN Click to Call was failing. It is no longer failing.

• An address2 populated value was resulting in an error when logging in to VA 2.0. This is no longer resulting in an error.

• Due to an inability to identify the time zone based on zipcode, text messages for accounts with unknown or bad zipcodes were being sent immediately. Now, text messages with unknown or bad zipcodes will be scheduled to be sent at 2pm to ensure they are sent between 8am - 9pm time frame in any customer time zone.

• TCN export jobs were sometimes running very slowly. Performance has been improved.

• Some PayNSeconds NSF transactions were not getting updated in ACE as expected due to updated file data. Settlement fields have been updated to match the returned data.

• The Primary Client selector on the Client Profile page was not working as expected. This has been fixed.

• The CreateUserAlert flow action was resulting in a failure when the action was not associated with a debtID. For example: when a Client Access User uploads a document that is not associated with an account. This no longer results in a failure.

• Client Access User cloning was sometimes resulting in permission roles being added that are not permitted for Client Access User types. This has been fixed.

• TCN click-to-call counts were not being reflected in the Phone Information "Calls" count as expected and the provider call id was sometimes empty. This has been fixed.

• TCN click-to-call was sometimes resulting in an account modified error. This has been fixed.