Release Notes 10/13/2024

Deploy

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

In This Issue

• ITMS MMS Messaging

• Form Modification

• Unique Duplicate Checking

• Client Logo Options

• Commission Rate Logic Updates

• Text Message Compliance

• Rainmaker Client Information Restriction

• Direct Payment Batch Source

• Dormant Users

• Non-SOL Payments/Plans

• Sonnet Palinode Label Update

• AWS Library Update

ITMS MMS Messaging

Our ITMS (text messaging) feature now supports Multimedia Messaging Service (MMS) in addition to Short Message Service (SMS) functionality.

This enhancement allows you to send rich media content, like images, via text message.

Please Note

MMS has limitations:

• MMS is only available for outbound text messages

• A single image or attachment may be included per message

• If multiple files are identified for attachment, a document will be selected over an images or other media types

Form Modification

Users will now be prevented from adding, deleting or editing forms and form fields will while more than 1 user (themselves) is logged in and/or while any job is running.

A message will be presented to the user specifying the reason the form cannot be edited whether it is jobs running or other users being logged in.

Unique Duplicate Checking

Custom duplicate checking is now available for placement ETL loaders.

A custom comma separated list (of field labels data is being loaded to) can be selected based on the mapped fields in the ETL Profile. The selected list is stored in a "Unique Account" field in the configured ETL Profile and will be used as the duplicate checking criteria.

If a field in the file that was previously mapped is removed from the ETL mapping, a message will be presented noting that it has been removed from the Unique Account field.

Client Logo Options

Two client specific logos can now be uploaded and stored in each client profile. One associated with the client and the other associated with messaging to the client's consumers. The logos are available for use in VA 2, email messages and MMS text messages.

If there is no consumer logo uploaded to a client, the VA 2 profile logo associated with the client's accounts will be used.

Only one logo can be included in an MMS text message and it will be superseded by any document attached.

Be on the lookout for an article titled, Step-by-Step Guide to Uploading Logos in Client Profiles for additional details. It should be available by next week.

Commission Rate Logic Updates

Commission Rate can now be applied based on different Received Balance Ranges, each associated with a Commission Rate Logic record.

When using the Received Balance option, each Commission Rate Logic record will apply only to the portion of a payment that fits within each defined Commission Rate Logic record’s received balance range.

If a single payment spans multiple rate logic records, each portion of the payment will be calculated using the corresponding rate for that range.

See the article titled, How to Set up Received Balance Commission Rate Logic for additional details.

Please Note

Reports in ACE showing commission will not represent different rates applied in relationship to Received Balance Commission Rate Logic records.

Commission Rate can now also be applied based on the Assigned Balance range by itself or in conjunction with the other logic options. When more than one logic option is selected, each selected logic option must be true in order for the commission rate logic to evaluate to true.

Please Note

Commission Rate Logic records are evaluated and applied in order top to bottom. Once a Commission Rate Logic record evaluates to true for a payment the specified commission rate will be applied and none of the following Commission Rate Logic records will be evaluated.

A default Commission Rate Logic record should always be created and applied last (with no explicit logic options selected). This ensures that any unanticipated scenario is accounted for and evaluated.

Text Message Compliance

Outgoing text message templates will be evaluated by Rainmaker when they are created to reduce compliance risks. When attempting to save a new text message template, information will be provided explaining problematic content.

Rainmaker Client Information Restriction

When consumers request client details, regardless of how the request is made, Rainmaker will now avoid providing client contact details. Instead, consumers will be redirected to review their account details or contact the agency.

Direct Payment Batch Source

When a payment plan is set up (or a payment is posted) using a DIRECT receiver payment batch, the source is now recorded as “DIRECT” and the source ID associated with the DIRECT batch is also recorded.

Please Note

Source fields are the same fields otherwise associated with a consumer using a link from an email or text message to set up a payment plan (or post a payment) in VA 2.0.

Dormant Users

There is a new option to set users as dormant.

1. Dormant users can be:

   1. Configured to accrue commission

   2. Assigned as the primary agent on an account

2. Dormant users:

   1. Cannot login to ACE

   2. Cannot work accounts as an agent

   3. Will not appear on billing

3. Commission data associated with dormant users will be reported using existing tools and configuration in ACE

4. If a dormant user needs to be restored to an active billable user, support will need to be contacted to make that change

5. User records that are created and have not had the “Make Dormant” button used will appear on billing.

Non-SOL Payments/Plans

There is a new Non-SOL Boolean field on the Post Transaction and Speed Posting pages.

• When this value is set to true at the time a payment is entered, payment revival statute of limitations (SOL) will not be impacted.

• If the value is left false, payments will continue to revive the SOL as appropriate for your existing configuration.

The Non-SOL field is also available from the Payment and Transaction ETL loaders. This means you can map and import data with the Non-SOL attribute.

The non_sol state is stored in the payment_trans, payment, and debt_trans views for use in SQL Designer reports.

Sonnet Palinode Label Update

Previously dispute record fields associated with the Sonnet Palinode vendor were labeled with "Sonnet." They are now labeled with "Provider."

1. The section header and field labels that are highlighted were updated from “Sonnet” to “Provider”.

2. The SQL debt_dispute fields were also updated from “Sonnet” to “Provider."

   1. Sonnet Id = Provider Id

   2. Sonnet Sent = Provider Sent

   3. Sonnet Received Timestamp = Provider Received Timestamp

   4. Sonnet Date Complete = Provider Date Complete

   5. Sonnet Alert Message = Provider Alert Message

3. If the Provider ID field is blank, a separate section with the header, “Additional Information" will be visible. If the Provider ID is filled in, the “Additional Information" header won't t be visible.

See the article titled, Sonnet by Palinode for additional details related specifically to Sonnet Palinode.

AWS Library Update

We have updated the AWS libraries used in our application to ensure continued compatibility with the latest AWS services and features.

These updates include important security patches, performance improvements, and support for new AWS functionalities.

Keeping these libraries up to date is essential to maintain a secure and stable environment, leverage new capabilities, and provide the best possible experience for our users.

Fixed These:

• Selecting a dismissed bankruptcy note was not linking to a dismissed bankruptcy record. It is now.

• A VA profile could not be created in the absence of a Default profile already existing. That has been fixed. Please Note: If a user attempts to delete or alter the DEFAULT VA 2.0 profile to be client specific, a new DEFAULT VA 2.0 profile will be created.

• Changes to the Email Upload user, the Max attachment size and the Max invitations fields on the Email Vendor page were not being retained on Save or Apply. They are now.

• The DOCUMENT_DEBT_DELETE permission was not governing the ability to delete documents as expected. That has been fixed. When a user has that permission, they will be able to delete account documents in the account documents page using the red X to the right of each document record row in the list. If a user doesn’t have the permission, the user won’t see the red X to delete documents.

• The Email Logs Page was not showing up as expected with email history in place. That has been fixed.

• Client access users were able to see the TCN Agent Login menu selection. That has been fixed and they will no longer be able to see that menu option.

• Accounts were showing up unexpectedly due to bundle selector configuration. There should no longer be erroneous record matches if the First Name is not a match.

• When a PDF Form Letter was cloned, it was taking the PDF Form Fields from the original Letter profile and they were not remaining in place on the original Letter profile. That has been fixed.

• The NCTB Disclosure Text has been updated to remove the explicit part about mailing a check or money order.

• If a Custom Color Scheme css text file and/or a Custom Text json text file did not exist on one or more VA 2.0 profiles, those files could not be changed on other VA 2.0 profiles. That has been fixed.

• When a user deactivated a payment plan, the user’s name was not being recorded in the notes. That has been fixed.

• After using an auto login link, in some scenarios, the consumer was unable to use the back button to successfully navigate to the summary page in the VA 2.0. That has been fixed. After using an auto login link, the back arrow should now take the consumer to the summary page.

• Images copied from a different File Manager Folder to the PUBLIC folder were being linked instead of copied and were therefore, when referenced from an email profile, were not being included in the email as expected. That is fixed.

• In the September Release, we introduced worklist logic filtering. A supervisor with the LOGIC_MANAGE permission role was unable to view, create and test logic filters when logged in as a user. That has been updated and they can now do so.

• Changes to the Bank Account selected in the “Trust Account” field on a client profile were not being retained. This has been fixed.