Release Notes 03/16/2025

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

In This Issue

• Cloning Roles

• Worklist Permissions

• Job Task Icons

• Swagger API

• SQL Rainmaker Assistant

• Transaction Reports

• UI Roles

• Account View UI

• Validation Notice

• Text Message Search

• Text and Email Search

• ITMS Text Validation

• Text and Email Counts

• Client Contacts

• Pay N Seconds

• Note Action Path Links

Cloning Roles

Permission and Data Roles can now be cloned.

Please note:

Configurating multiple permission roles with overlapping permissions or multiple data roles with overlapping primary/sub clients may lead to unintended consequences. It is important to test and verify user access when making changes to permission and data roles after assigning those roles to users.

If you are unable to edit or create roles, please contact support for assistance.

Worklist Permissions

There is a new permission, WORKLIST_SEND_MY_SUPERVISORS, that may be added to a permission role to limit which supervisor worklist a user may escalate accounts to. Associated permissions are now:

1. WORKLIST_SEND_ANY_WORKLIST - user is permitted to move an account to any worklist or any Supervisor Worklist

2. WORKLIST_SEND_OTHER_WORKLIST - user is permitted to move an account to any worklist as follows:

   1. Where the Worklist has the user in the Users list section

   2. Where the Worklist is a Supervisor Worklist selected in the User’s Worklist Rules section

3. WORKLIST_SEND_MY_SUPERVISORS - user is permitted to move an account to a Supervisor Worklist selected in the User’s Worklist Rules section

Please note:

In order to avoid limiting account movement options for administrative users, a new permission role may need to be added for this permission.

If you are unable to edit or create roles, please contact support for assistance.

Job Task Icons

When using icons in a Job Task to open a Report, Action Path, or Logic Block, the selected item will now open in a new browser window instead of the current window.

Swagger API

The Swagger API documentation (Help → API Documentation) now includes example JSON requests for ACH and credit card (CC) payments under /account/{debtID}/payment, providing guidance on posting payments.

For more information see this article: ACE API Documentation Overview.

SQL Rainmaker Assistant

There is a new Rainmaker Assistant in the SQL Designer.

1. The Rainmaker Assistant can be used to ask questions and obtain feedback regarding an existing query.

2. It can be asked to provide a starting query.

3. It can also be used to optimize an existing query.

Customers can submit misidentified field examples to support for potential improvements to the Rainmaker Assistant.

Additional SQL Designer updates are implemented with this feature as follows:

• When first tabbing to the Identifier field from the Label field, after a SQL Report is created, the Identifier field will be automatically populated with the contents of the Label field.

• The SQL query window has been moved up the page to provide more efficient access to the section most used.

For more information see the article: SQL Rainmaker Assistant.

Please note:

all SQL queries should be tested with a LIMIT variable in the WHERE clause to quickly return a sample of data to be validated. The final report must also be validated against a broad assortment of expected data to rule out erroneous joins and other possible erroneous statements in the query.

A fundamental understanding of PostgreSQL is necessary in order to understand the ways in which a provided SQL query may not meet the desired needs and to understand when the Rainmaker Assistant may have provided a field that does not match the intended context.

Transaction Reports

When using the core report under Reports → Accounting → Transactions to find data associated with accounts in judgment, only the judgment account data will now be shown.

The original accounts associated with the judgment will no longer be included in the resulting reported data.

User Interface (UI) Roles

The auth_user_passwd.ui_config_role_id field is now exposed in SQL. Using the auth_user_passwd.ui_config_role_id field, the UI Template set for users can be reported via the SQL Designer.

Example SQL Query:

SELECT 

     auth_user_passwd.username, 

     auth_role.label AS "User Interface Role"

FROM 

     auth_user_passwd, 

     auth_role

WHERE 

     auth_user_passwd.ui_config_role_id = auth_role.role_id;

Account View User Interface (UI)

Setup → User Interface → Account View now includes the ability to rearrange the “Original Primary Demographic Information” section so it can be displayed in a different place on the Account page.

Validation Notice

When sending a Validation Notice using an ELS letter profile:

• If the Validation Notice is sent as a letter, the validation_notice_sent_channel will be recorded as “LETTER.”

• If the Validation Notice is sent as an email, the validation_notice_sent_channel will be recorded as “EMAIL.”

This update ensures accurate tracking of the validation notice for compliance and reporting.

Text Message Search

The Utilities → Text Message Search now allows the user to search by Sent Text Status. When not populated, all records are returned.

Text and Email Search

The Utilities → Text Message Search now allows the user to search for a Text Message by the Text Message Profile used to send it.

Utilities → Email Search now allows the user to search for an Email by the Email Profile used to send it.

ITMS Text Validation

ITMS Text Validation “FAIL” text will now be shown in two different colors to designate if the Text Message Profile fails to meet best practice (ORANGE) or fails to meet requirements (RED).

A red "FAIL" will not allow the profile to be saved, but an orange "FAIL" will.

Text and Email Counts

The client_summary and client_summary_by_placement tables now include six new fields for tracking text and email counts:

• texts

• texts_outgoing

• texts_incoming

• emails

• emails_outgoing

• emails_incoming

These fields will be updated when the client statistics are refreshed.

Client Contacts

Client Profile Primary and Secondary Contact records now include an explicit Mobile Phone Number field.

Several new contact records are available now to be populated on the Client Profile. They are labeled as follows:

• Owner

• IT

• Legal

• Accounting

• Dispute

• Billing.

The contact records can be populated via file using an ETL Profile.

Pay N Seconds

Through the payment provider Pay N Seconds a no fee to biller (NFTB) option is now available.

NFTB provides the option for your organization to pass the cost of card acceptance to the card holder.

When used, ACE will automatically create a second transaction with the consumers credit card fee at the time of the transaction.

If you are interested in learning more, please reach out to Pay N Seconds.

Note Action Path Links

There are two new columns in the Notes list on the Account page. They allow the user (with appropriate permissions) to open the Flow Action or Root Action Path related to the generation of a note.

Fixed These:

• SSO users were erroneously being routed to the password reset page. This has been fixed.

• Client Searchable Form Fields are now included in the Search Options section of the Clients Search Form instead of being separated into a different section.

• Dragging and dropping forms in the Forms list to rearrange their order was causing a timeout. This issue has been resolved.

• Standalone form fields appeared available for the Account Summary section but could not be added. Now, they are available and can be added as long as they are not associated with multi-instance standalone forms.

  • Please Note:

    • Multi-instance standalone form fields do not appear in the list of available fields for the Account Summary section.

    • “Display On Summary” applies only to a multi-instance form summary and does not relate to the Account Summary section.

• Selecting the copy icon next to a field in the Account Summary section previously caused screen jittering. This has been fixed, and a checkbox icon now confirms the field value has been successfully copied.

• Selecting the Agency # from the Summary section to refresh the account page or using View Account from the Account Page sidebar was causing the section to expand and collapse twice. This no longer occurs.

• The Discharged Boolean was not being updated when a Bankruptcy was discharged. It is now.

• Action code notes failed to save when the referenced note value contained an ampersand (&). The system now processes and saves notes with more special characters.

• There were situations where the collapsible sidebar feature was interfering with chat window use. That has been fixed.

• The Help → About → Database IOPS metrics panel was not consistently displaying data. Now it is.

• Some accounts were showing up in a forwarded batch but not showing in SQL as forwarded. The scheduled job that purges old data will now clear those stuck records when found.

• Browser Cookies are required when using ACE and are now forced at login in the event they have been disabled.

• Retrieving accounts by Client Account Number in a logic block was slow. This performance has been improved.

• Consumers were able to enter invalid phone numbers in Virtual Agent and ACE rejected them without notifying the user. Now, if a consumer enters an invalid phone number, they will receive an error message, and the number will not be saved.

• Invalid User Token errors for Nuvei payments occurred when modifying a payment plan due to a mismatch between the new plan ID and the payment token. This is now fixed.

• During a single browser session, when a user was logged into ACE and attempted to log into a VA account using the “Log in to Virtual Agent” sidebar option after having already done so with a different account the user ended up at the first VA account again. That has been fixed.

  • Please Note: only the latest logged in VA account will be active and accurately represent the account being tested.

• currentUser and currentUserID are fields that are now in context for JavaScript Condition Action Path Workflow.

  • Please note: As with any conditional flow actions, unexpected results should be evaluated carefully. While troubleshooting, it’s necessary to determine if the condition being evaluated may have changed immediately before the conditional check took place.

• The lightning bolt icon was flashing for all timed alerts. It will now flash only for expired alerts. Unexpired alerts will still appear in the list, but only expired ones (shown in red) will trigger the flashing bolt.

• When agents were given the LOGIC_VIEW permission in order to use Worklist Logic Filtering, they were also able to access the Account Manager page. New Account Manager page permissions have been added and included in the “Manage - Account Manager” permission role that will be required in order for a user to see the Account Manager page.

• Please Note: There may be additional permissions needed in order to access the Account Manager page.

• When a consumer added a new phone number in Virtual Agent 2.0, the previously opted-in number was being automatically opted out. Now, the new number is opted in, while the previous number remains opted in.

• Phone log records created via API were not executing the configured dialer code action path workflow. They are now.

• The “Text Message Search” sidebar item was showing up at the bottom of the page instead of immediately below “Text Message Manager.” That has been fixed.

• Duplicate Virtual Agent login notes were appearing in ACE due to service provider initiated email link testing. This issue has been resolved.

• When ACE timed out while a user was on the jobs page, after logging back into ACE, an unexpected page was being presented. That is no longer happening.

• Jobs to send text messages and email messages were failing when attempted for phone number or email addresses set with “DO NOT CONTACT”. Now, the job will not fail and a note will be included in the job logs regarding those that were not sent due to being set with “DO NOT CONTACT.”

• A $NaN value was erroneously being displayed in place of interest due to missing itemization data in a bundle member. This issue has been fixed.

• Clicking the Action Path icon from the Trigger List page incorrectly redirected to the Trigger Setup page. This issue has been fixed.

• Provinces, when loaded via ETL and spelled out, were not visually represented in the demographic address record. This has been fixed. Now a state or province loaded via ETL will be represented by the two letter abbreviation correctly in the displayed demographic address record.

  • For example:

    • “washington”, “WASHINGTON”, and “wa” will be displayed as “WA”

    • “ontario”, “ONTARIO”, and “on” will be displayed as “ON”

• Errors while building worklists were associated with infinite loops. This is fixed.

• The Report Runner Job Task includes options for sending emails to users or other email addresses with the report. Previously, an email template with a ${body} parameter needed to be selected. Now, these emailed reports will be sent successfully, even if no template is selected or if the selected template has no ${body} parameter.

• A job sending texts and emails was failing altogether if one of the messages failed to send due to "DO NOT EMAIL" or "DO NOT TEXT." Now a note will be recorded on the account for the failed message send and the job will not fail.