Release Notes 06/15/2025

  • Published on Jun 13, 2025
  • 8 minute(s) read
  • Gina Magana
 Prev Next

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

Image Displays Mountain View

In This Issue

  • Bankruptcy ETL

  • Account Update ETL

  • ETL Description

  • ETL Phone Log Fields

  • Collection Costs

  • Bundle Propagation

  • Pending Transactions

  • Phone Status

  • TCN Login

  • Misc Fields

  • Repay NFTB

  • Payment Batch

  • Too Early/Late

  • View Bundle Letters

  • Cancel/Reactivate

  • pop3 Inbound Email

  • Archiving Chats

  • Flow Action/Trigger

  • Payment ETL

  • Locked Accounts

  • Rainmaker Preferences

Bankruptcy ETL Load Method

A “Batch Insert” option is now available for use with the Bankruptcy ETL Load Method under Data Options.

When Batch Insert is enabled:

  • New instances of a bankruptcy record already loaded to the bundle member account will each initiate the onAfterBankruptcyInsert trigger.

  • New instances of a bankruptcy record that has not yet been loaded to one of the bundle member accounts will also each initiate the onAfterBankruptcyInsert trigger.

When Batch Insert is not enabled:

  • New instances of a bankruptcy record already loaded to the bundle member account will each initiate the onAfterBankruptcyUpdate trigger.

  • The first instance of a bankruptcy record that has not yet been loaded to one of the bundle member accounts will initiate the onAfterBankruptcyInsert trigger. Subsequent instances of the same bankruptcy record loaded at the same time will each initiate the onAfterBankruptcyUpdate trigger.

For the purposes of this feature, having the same chapter, status, case, and date filed in a bankruptcy record is what defines it as the same one.

Image Displays Batch Insert Field in Bankruptcy ETL Load Method

Account Update ETL Load Methods

A new ETL load method is available for account updating. The new load method is “Account Updates Optimized”. The previous load method is renamed “Account Updates Legacy” with no functional changes.

The Account Updates Optimized load method is improved as follows:

  • It is 2x faster

  • Has Multithreading which may dramatically enhance speed

  • Does not have an overlay option

  • If a field is mapped it will be updated and if the value is blank it will update it to a blank value

  • If a value is not mapped it will not be updated or blanked out

ETL Import Profile Description

“Description” is now available to be added as a viewable column on the ETL Import Profiles page (Accounts → ETL Imports → Profiles).

New ETL Fields for Phone Logs

There are two new fields that can be populated as follows using ETL with the Phone Logs Load Method. These are details that might be returned by a dialer vendor.

  1. Sentiment - can be populated with one of these explicit values

    1. POSITIVE

    2. NEUTRAL

    3. NEGATIVE

  2. Transcript - can be populated with a text string

Image Displays Sentiment and Transcript Fields for ETL Phone Logs Load Method

Collection Costs

Under Setup → Collection Costs, “Texts (per text)” has been replaced with two separate options for MMS texts and SMS texts.

Image Displays SMS Texts and MMS Texts Fields in Collection Costs

Bundle Propagation

To reduce risks to data integrity, the ACE user interface has been updated so Primary Demographic Bundle Propagation cannot be accidentally disabled or modified.

No current configuration in place is being changed.

If you feel you have a need to disable it temporarily, please reach out to support.

Pending Transactions

“Assigned Date” is now available to be added as a viewable column on the Pending Transactions page (Clients → Client Access → Pending Transactions).

Image Displays Assigned Date Column in Pending Client Transactions

Phone Status

There is a new Phone status code, "Consumer Blocked," available to be used with Phone Demographic records and Dialer Vendor Codes.

Image Displays Consumer Blocked Phone Status

TCN Login

The Utilities menu now displays a single TCN Login link, replacing separate TCN Agent Login and TCN Operator Login links.

Misc Fields 11–30 Can be Renamed

Misc Fields 11-30 can now be relabeled (Setup → Accounts → Labels). Permissions may need to be configured in permission roles in order to view these fields.

Please reach out to support if you need assistance with updating permission roles.

Repay NFTB

Through our partnership with the payment provider Repay, we are now offering an additional payment processing option: No Fee to Biller (NFTB).

NFTB allows your organization to pass the cost of credit card acceptance to the cardholder. When this option is used, ACE will automatically create a second transaction to reflect the consumer’s credit card fee at the time of payment.

If you’re interested in learning more, please contact sales@interprose.com.  

Payment System Batch Job Tasks

The Payment System: Close Batch and Payment System: Deposit Batch job tasks now accept a comma-separated list of batch IDs, allowing multiple batches to be processed in a single run.

Image Displays Batch IDs in Payment System Close and Deposit Job Tasks

"Too Early/Late to Call” Alert

The "Too early/late to call this customer" pop-up has been refined to reduce repeated interruptions. The message will now only appear when viewing the first account within the bundle.

View Bundle Letters

A new “View Bundle Letters” option is available in the Letter Actions dropdown menu. When selected, letters associated with any accounts in the bundle will be listed and can be cancelled or deleted from the list.

Please note: The "View Letters" option will continue to have only letters associated with the account being viewed.

Cancel/Reactivate Performance Optimized

Cancel and Reactivate action path performance has been optimized to complete faster at scale, reducing job runtime for large account batches.

pop3 Inbound Email Update

A change has been made to configuring pop3 inbound email settings in the Email Vendor screen. These settings can now only be modified by InterProse. Please contact sales@interprose.com to enable or update inbound email settings.

For associated information see the article: Configuring an Email Vendor

Archiving Chats

A new “Archived” status is available for chat logs. In Chat Manager, you can use the multiselect option to archive multiple chats at once.

Archived chats will no longer appear in the Chat Manager. Archived chats can be found using Utilities → Chat Search.

New Flow Action / Trigger

There is a new conditional flow action with the Class Name, "If Module" that can be used to identify expected behavior based on the module in context.

There is also a new trigger, onAfterDebtDoNotContact, which is initiated when an account is marked with any 'Do Not Contact' status. The new trigger is only initiated based on account level Do Not Contact updates, and not Demographic Do Not Contact updates.

Image Displays If Module Class Name and onAfterDebtDoNotContact Trigger

Payment ETL Transaction Batch

A new Transaction Batch ID mapped field has been added to the Payment ETL loader, allowing payments to be assigned to specific batches during load. A fallback batch ID is still required in the ETL options for any records missing a mapped value.

Update Locked Accounts

Users with the DEBT_STATUS_UPDATE_LOCKED permission are now able to update cancelled or otherwise locked accounts as if they were not locked.

Please note: the "LOCKED" pill will show for staff who don't have the permission, but will not show for admins and users with the permission.

Rainmaker Preferences

Rainmaker Preferences allow administrators to control how Rainmaker interacts with account data. Settings include:

  • Summary Action – Triggers an action path to generate account summaries when Rainmaker is used.

  • Rainmaker Prompt – Uploads a text file to guide Rainmaker’s responses.

For more information see the article: Rainmaker Preferences

Fixed These:

  • Applying changes to more than one account in a bundle inadvertently allowed a user without appropriate permissions to update locked accounts. This has been fixed.

  • Text Validation Notices were sometimes sent with unpopulated data. Now, if itemization data is not populated in the ACE account, an error will be logged to the job or presented to the user.

  • An extra “View Note” was being created after “View Account” was being used to return to the account page from the email log page. This behavior has been updated to reduce excessive View Notes.

  • The Payment System: Deposit Batch job task was slow. This has been improved.

  • API searches using an invalid phone number as the only parameter were incorrectly returning results. This now returns an “Invalid search results” error.

  • ACE account searches with no input were returning results. This has been fixed to show an “Invalid search results” error when no search criteria has been provided.

  • Minimizing a form on the account screen previously only collapsed up to 100 fields, leaving the rest visible. This has been fixed.

  • Primary jobs that are used to run other jobs were showing a status of COMPLETED while one or more of the jobs being run by it were failing. Now, the primary job will now display a status of ERROR if any of the jobs in it fail.

  • The onAfterDemographicAddressUpdate trigger was firing based on state regulation settings even if no address changes were made. This has been updated so it will not fire when address changes were not made.

  • When sending a Validation Notice MMS Text, an error was being thrown if the account had a form with a PERCENT type field. This will no longer cause an error.

  • The text template dropdowns for Payment Reminders, Payment Receipts, and Authorization Requests in the Payment Destination Profile were not displaying all available options. This has been fixed so that all text message profiles now appear correctly in the dropdown lists.

  • Creating a new Virtual Agent profile in multi-application environments was always assigning the profile to the host customer. A new VA Profile will now be applied to the environment in which it was created even if it is not the host customer.

  • The validation end date field, when used in an MMS text message template, was not displaying the populated validation notice end date in the message. This has been fixed.

  • After a Judgment account was deleted, the Judgment pill was still displayed in the summary section of the original accounts that were party to the judgment. Now the Judgment pill will be removed if all Judgment accounts associated with the legal case have been deleted. The legal case record will remain in place.

  • There was a problem identified with restoring deleted flow actions from the audit log. This has been fixed.

  • When a Client Access User added a new account in ACE that automatically bundled with an account they had no permission to, the Client Access User received an “Unauthorized Lookup” error. This has been fixed and the account will be loaded without error.