Release Notes 07/13/2025

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

In This Issue

• Role Groups

• VA 2.0 State Fees

• Rainmaker Chat/Text

• Rainmaker Responses

• Rainmaker Condition

• Chat and Rainmaker

• Dispute Search

• Document Transfer

• Dispute/Resolution Code Sorting

• Multi-Factor Authentication

• Email Previews and Rainmaker Refresh

• File Uploaded Email

• Webhook URL for Inbound Email

• Credit Reporting Canada

Role Groups

There is a new option for Role Groups under Setup → Roles.

Permission Roles and Data Roles can be stored in a Role Group. Then the Role Group can be assigned to individual User Profiles.

For more details review this article: Adding Role Groups.

VA 2.0 State Fees

State Fee Configuration in ACE is now supported for use in VA 2.0.

For more details review this article: VA 2.0 State Fee Configuration.

Updated Rainmaker Options for Chat and Text

Rainmaker options for Chat Vendors and Text Message Vendors have been updated as follows:

1. There is a new option for Chat Vendors: Enable Rainmaker even when agents are available: "When enabled, Rainmaker will be used to generate responses even when agents are available."

2. There are two new options for Text Message Vendors:

   1. Enable Rainmaker auto-responses: "Automatically respond to inbound texts with Rainmaker."

   2. Enable Rainmaker auto-responses when agents are available: "By default, Rainmaker will only automatically reply to inbound texts if there are no agents or supervisors available. Enabling this option will allow Rainmaker to automatically respond to all inbound texts even when an account's primary agent or text message supervisors are logged in."

Rainmaker Responses

Rainmaker responses have been optimized to better display symbols included in chat response prompts. Symbols likely to display as expected now include quotes, dashes, and ampersands.

New Rainmaker Condition Flow Action and Trigger

The Rainmaker Condition flow action is now available to evaluate summarized chat logs.

In addition, there is a new onAfterChatSummary trigger the Rainmaker Condition can be used in conjunction with.

Agent Chat Sessions and Rainmaker

Rainmaker behavior that automatically results in DNC, Dispute, Escalate, or Settlement Request will no longer be initiated as a result of a chat conversation with a logged in agent or supervisor.

Those automatic behaviors will continue to function as a result of Rainmaker / Consumer conversations not involving an agent or supervisor.

Dispute Search Field in Utility Bar

There is now a field in the blue utility bar allowing accounts to be searched by dispute ID numbers.

In order to view the new Dispute Search field, a user needs the permission, “ACCOUNT_DISPUTE_SEARCH”. This permission could be added to the “Manage - Disputes” permission role. An admin may need to reach out to support to request the addition of this permission.

Document Transfer From Job Task

The Document Transfer From job task has been updated to include an option that will prevent the transfer of files with the same filenames that already exist at the destination.

Dispute and Resolution Code Sort

When selecting dispute codes and dispute resolution codes for a Dispute record, the code lists are now sorted alphabetically based on the code's label.

Multi-Factor Authentication

If “Force Users to Enable Multi Factor Authentication” in Setup → Users → Preferences is set to true, and “Require additional authentication for Client Access users” in Setup → System is also set to true, a Client Access user will only be required to perform the authentication associated with the latter option (the additional authentication for client access users).

Previously ACE required Client Access users with this configuration to authenticate twice.

Email Previews and Rainmaker Refresh Options

There is an option in the Email Manager page where an inbound email reply can be previewed and the user can refresh a Rainmaker generated reply.

This option is now also available from the Email Queue page (after selecting an inbound email from the Demographic Email Log list).

This option is also now available when responding to an inbound email from the account sidebar Email Log.

File Uploaded Email Profile

The FILE_UPLOADED email profile now has client fields in context so they can be included in the subject line or email message.

The FILE_UPLOADED email profile is the one used when a message is sent to a File Manager client's, user's or admin's folder updating them that a file has been uploaded to the folder.

Webhook URL for Inbound Email Messages

There is now a Webhook URL field in Text Message Vendor configuration Vendor Information section.

In addition to in addition to inbound email and notification in ACE, when this field is populated with a URL, ACE will also send inbound texts to the URL.  

There is also a new API endpoint available in ACE to be used for searching and retrieving text logs.

Credit Reporting Country Code Canada

The Metro2 Credit Reporting file will now reflect the country code as CN if the customer and consumer records both reflect CA as their country code.

Fixed These:

• When attempting to load a flag identifier using the Notes ETL Load method, the flag identifier was not showing up on the account. It is now. Please Note: When using the “Account Flag” field in ETL profiles, there must be other data mapped for the file being loaded in order for the populated flag to be recorded to the account.

• Account Client Codes were not showing in alerts. They are now.

• When using a debt group account field in an email template, the generated field was not appearing as expected in email messages. This has been fixed.

• The “Terminate queries older than” buttons for 5 minutes & 15 minutes, available from the “running queries” page, were not working as expected. They are now.

• Duplicative payment reminders were being sent when reminder timing applied to more than one payment and/or more than one account. This has been fixed.

• Customers configured for Canada were sometimes seeing currency displayed to consumers in the VA 2.0 as US$100.00. Consumers were erroneously thinking that the amounts seen were being converted to U.S. dollars. Now, when a consumer for a customer configured for Canada is logged in with browser settings for “English (Canada)”, they will see the currency as $100.00 with no country designation. If a consumer for a customer configured for Canada is logged in with browser settings for “English (United States)”, they will see the currency as CA$100.00.

• The API end point was not returning TxgtMsgLog as expected. It is now.

• Cloning a client was not showing the last assigned date updated as expected. It is now.

• An issue causing balloon payments has been identified and fixed.

• Saving a payment schedule after taking a payment was erroneously recalculating the plan, resulting in incorrect payments and balance. This has been fixed.

• Customers in Canada are not required to wait 365 days to credit report medical debts under $500. Customers in Canada are now automatically configured to disregard that requirement.