Release Notes 05/18/2025

You can expect up to 3 hours of downtime to deploy this release.

The deploy is expected to take a bit longer this time due to optimization of DB indexing. Client Statistics should refresh approximately 3-5 times faster.

In This Issue

• Promotion Codes

• Running Queries

• Chat Debt Notes

• Worklist User View

• Bundle Group Fields

• Email Profiles

• Email Message for File Upload

• Text Field for Logs

• Duplicate Text Prevention

• SBTv2 MMS Validation Notice

• Form Field Encryption

Promotion Codes

There is a new feature allowing single use promotion codes to be offered to consumers and redeemed by agents. Promotion codes are associated with the bundle and are visible from any account in the bundle.

Please see these two new articles related to configuring or loading Promotion Codes that can be used with payments or payment plans:

• Single Use Promotion Code Configuration

• Bundle Promo Codes ETL Layout

Running Queries Update

The running queries page now includes a Boolean (true/false check box) to allow the user to select multiple running queries. Now multiple queries can be selected and terminated at the same time.

There are also new buttons available to terminate queries older than 5 minutes or 15 minutes.

Chat Debt Notes

Chat summary debt notes will now automatically be created by Rainmaker every hour.

• This applies to new Chat messages moving forward.

• Chats will be summarized

  • if they have not previously been summarized

  • and if the chat conversation is no longer active

SQL Designer worklist_user View

The worklist_user view is now available for reporting in SQL Designer. Here is an example of a query where it might be used to report the users associated with a worklist:

SELECT
  auth_user_passwd.username AS "User Name",
  worklist.label AS "Worklist Name"
FROM
  worklist,
  worklist_user,
  auth_user_passwd
WHERE
  worklist_user.worklist_id = worklist.worklist_id
  AND auth_user_passwd.user_id = worklist_user.user_id; 

Bundle Group Fields

Bundle Group fields that are in context can now be included in Template Letter Vendor Export Files and in Template Enrichment Vendor Export Files. Only bundle fields can be included in this way.

The format for specifying a bundle group field is: bundlegroup_[IDENTIFIER].[FIELD]

Below are a few examples of fields for a bundle group that can be added to export files:

• bundlegroup_STATUS_BUNDLE_GROUP.assignedBalance

• bundlegroup_STATUS_BUNDLE_GROUP.receivedBalance

• bundlegroup_STATUS_BUNDLE_GROUP.currentBalance

Email Profiles

When adding a new Email Profile, from the Email Profiles page or the Email Vendors page, the profile will now be active by default.

Email Message for File Upload

There is now a new Boolean field under Setup → Email → Preferences. When set to true, client access users who upload documents via drop box will receive a confirmation email message.

This message uses the default Vendor’s FILE_UPLOADED_CONFIRM email template.

If a client is associated with multiple client data roles, one of the primary clients they are associated with will be the one used.

Text Field for Logs

A new field, Vendor Request ID, is now visible in the Text Log page, in the Demographic Phone Text Message Log and is available for queries in the SQL txt_msg_log view.

AWS can be provided the value in this field to help trace failed ITMS text messages.

The value will be populated for SBTv2, but it will not be useful for tracing failed text messages for SBT.

Prevent Duplicate Texts

The duplicate message check for ITMS and SBTv2 now includes template ID matching.

If a text using the same template is sent within 30 seconds—even with different variable content—it will be blocked to prevent duplicates.

SBTv2 MMS Validation Notice

SBTv2 can now send MMS validation notices using email template profiles.

Previously this option was only available for ITMS.

For more details, see the article: MMS Images Using Email Profiles

Form Field Encryption

Form fields can now be used with encryption to limit field values that will be visible or editable at a user level.

For use with this new Encrypted String field type, there are 3 new role fields that can be set. These role fields only apply to the Encrypted String field.

• Encrypted Insert Role: A user who has the role listed in this field will be able to insert data into a blank Encrypted String field. Otherwise, even though the field is blank, a user will not be able to insert text into that field.

• Encrypted View Role: A user who has the role listed in this field will be able to see the unmasked, unencrypted data in the UI. Otherwise, users will only see the last 4 digits of this field unmasked.

• Encrypted Edit Role: A user who has the role listed in this field will be able to edit the data in the field.

Fixed These:

• The message confirming “Deleted” after a logic block deletion has been confirmed, was not being presented. It is now.

• When creating a new case, using the Proposed Judgment Spread “Auto Spread” was clearing out details already entered in the Case section. That is fixed. Now those details won’t need to be reentered.

• Using the "Become User" function was not loading a fresh copy of the user, which could cause outdated roles and permissions to appear. That is fixed.

• A scenario was discovered where a user is entering data into separate forms in separate open browser windows for the same account. The results in one form were overwriting the other based on the order of the form data being applied. This has been fixed. Now an error will be presented letting the user know that there is a form matching error.

• Recent changes to the icons in the summary section (next to most values stored there) of the account page resulted in an inability to copy values from that section. That ability has been restored.

• A login error was caused due to non matching addresses between the VA and ACE. This has been fixed.

• An issue was preventing users from being able to successfully generate their SQL Schema. That has been fixed. There is also now a “Force Refresh” button available for use in the event that the SQL Schema does not generate within a reasonable time, for example within 15-20 minutes; this varies by customer.

• Extra long form identifiers and Extra long field identifiers were resulting in problems with adding fields to the account summary screen. This has been fixed and now the field selector for the summary section will allow those fields to be selected and added. Please Note: long form fields may display in undesirable ways. Please test and validate your results.

• Setting a mail return reason via action path workflow was not working. This has been fixed.

• The “Allow Plans Past Expiration Date” setting on credit card payment destinations is now respected in Virtual Agent 2.0. If this setting is enabled, consumers will receive an error when attempting to set up a payment plan with a credit card that expires before the final payment date.

• Accounts in the Metro2 file were being rejected due to diacritical characters in addresses. For example, the symbols added to letters to indicate pronunciation in these address details: 123 Piñata Blvd., El Niño, TX or 45 Rue de la Façade, Résumé, QC. This has been fixed. Please Note: Some diacritical characers, like a cedilla or a tilde can not currently be represented in ACE. Those characters, will be represented as a space or blank character in ACE and in the Metro2 file.

• A report sent using the “Report Runner: Run as User” job task was not using the Output File name identified in the job task when sent via Email. Now it is.