Release Notes 09/15/2024

Deploy

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

In This Issue

• Worklist Logic Filters

• Logic Block View and Edit

• Demographic Color Coding

• Scheduled Payment Template Variables

• Tracking Clicks

• Text Messages

• Email and Text Source

• Dispute Resolution

• ETL Bundle Placement

• Logic Blocks

• VA Visible Documents

Worklist Logic Filters

InterProse has now created an option that allows agents to use logic to filter the accounts in their worklists. The option requires the permission role: "Worklist - Logic Filter."

Applied worklist logic filters are not retained between login sessions. However, the logic created is saved and can be applied again during subsequent login sessions.

To learn more about this new feature, please review this article: Worklist Logic Filter Overview.

Logic Block View and Edit

There are now View & Edit Roles that can be applied to Logic Blocks.

When opening a logic block (from Workflow → Logic Blocks), these two fields will be shown below the description. Only users having a permission role with the "LOGIC_MANAGE" permission will be able to see, populate and save role selections to these two fields.

1. View Role ID - Only users having the role populating this field will be able to select and use this Logic Block from the various menus throughout ACE. Some examples where Logic Blocks can be selected for use in ACE are: Account Manager, Jobs, Action Paths, Bundle Groups and VA 2.0 Profiles.

2. Edit Role ID - Only users having the role populating this field will be able to apply or save edits to this Logic Block in the Logic Builder.

Demographic Color Coding

Email address records and phone number records are color coded based on status. Those colors have been updated so they are now more consistent. The colors associated with the same email addresses and phone numbers, when displayed in the summary section will also match.

For additional details, see related content in this article: Navigating Accounts in ACE.

Scheduled Payment Template Variables

Previously when a text message, including payment plan details, was sent to a consumer, it was only including payment plan details when the account the message was sent from was associated with the plan.

Now, if the account is not associated with the payment plan, and another account in the bundle is associated with a payment plan, the email, letter or text message will include the details related to that plan.

For additional information about communicating the next scheduled secure payment to a consumer, please review these two articles: Secure Payment Plan Reminders and Managing Payment Destinations.

Please note:

If there are multiple payment plans set up for a bundle of accounts, details related to only one of the plans will be included when using the identified template variables.

Tracking Clicks

If you click on a link in an email that is being tracked for data related to opens/bounces, etc. additional data related to each clicked_link and clicked_link_date will now be stored. These details can be reported in an email queue/email log SQL report table.

Text Messages

Text messages can now be sent from the Text Log page even when there is no existing text log history, as long as the phone number used has been opted in for text messages.

Email and Text Message Source

When a consumer sets up a payment plan after using this login link to access their account in VA 2.0, ${debt.virtualAgentLoginUrl}, the payment plan will now identify the source of email or text and the source id (Txt Msg Log ID, Email Queue ID) associated with that login.

For more details about auto-login links, please review these articles: How Do I Add an Auto-Login Link in Text and How Do I Add an Auto-Login Link in Email/ELS.

Dispute Resolution

Previously, when a dispute resolution date was entered or updated, the onAfterDisputeResolution trigger was being initiated. Now it will only be initiated when the dispute resolution code is entered or changed.

ETL Bundle Placement

There has been some optimization applied to ETL placement processing. The greatest impact will be seen by customers who load accounts to very large bundles.

Specifically, the originalPrimaryNationalID will no longer be loaded every time a debt is loaded. When viewing the Original Primary Demographic Information section on the account page, in order to see the value populated in the NationalID field, the user will now need to click into that field.

Logic Blocks

When a logic block is locked it will no longer show up in the Logic Blocks list by default. The user will be able to view locked logic blocks by removing "locked:false" from the filter in the list view header.

Please note:

• Some logic blocks are locked by default.

• If you want a particular logic block protected, you can reach out to support to request that it be locked.

• If a customer wants to manipulate a specific locked logic block, they can clone it and modify the cloned copy.

• Logic blocks that are locked can still be used in workflow.

VA Visible Documents

The VA Visible Boolean will now default to false in the user interface for the documents page. A user can set it to true before uploading documents if they would like the documents to be visible to the consumer on VA 2.0.

Fixed These:

• The Client Invoice Last Run Date was not being updated after a previously generated invoice was deleted. It is now.

• Unified name loading via ETL was not working correctly with multi-threading enabled. That has been fixed.

• Expired automatic login links will now redirect to the login page instead of resulting in an error. Information about links can be found in this article: How Do I Add an Auto-Login Link in Text and How Do I Add an Auto-Login Link in Email/ELS.

• Scheduled emails were failing to be sent due to there being restricted emails in front of them. This has been fixed.

• When the VA 2.0 profile setting to “Allow users to stop their own payment plans” was set to false, consumers were still able to cancel payment plans. That has been fixed. Please Note: the “cancel/contact” button at the bottom of the VA 2.0 payment plan modify page has been removed. It is not necessary because it was not associated with canceling a plan. Consumers can use the back arrows to return to the previous pages in VA 2.0.

• The ability to create or edit an ELS Vendor in ACE was resulting in errors for new customers. This has been fixed.

• There was a scenario where aging on the invoice was showing up incorrect. This was due to a specific configuration. It has been fixed.

• Loading Country Codes using the phone number ETL was not working. It is now. Please Note: the country code format that can be loaded via ETL is a two character alpha code (ISO 3166-1 Alpha-2).

• When no “After SOL Disclosure” was populated, an error was being displayed. In addition, payment revival without populated SOL Account Type and State were resulting in a different error. These issues have been fixed.

• A scenario was discovered where accounts for different individuals were showing up when using bundle selector. It has been fixed.

• The Vendor Tracking Status and Status Time were not being updated in ITMS text message data. That has been fixed.

• The minimum allowable VA 2.0 payment amount will now reflect the remaining bundle balance if it is lower than the client and VA 2.0 profile minimum amounts. The minimum setting for a VA 2.0 profile cannot be below $0.01.

• When verifying a priority 1 phone number, the phone number priority was being reordered beneath Active and New phone numbers instead of remaining in the priority 1 position. That has been fixed.

• The Document VA reference url link was not working as expected when the original url link had been modified. This was resulting in errors. A change has been put in place to improve the behavior.

• Changes to the VA Visible Boolean (setting to true or false) were not taking immediately effect. They are now.

• Deleted logic blocks could not be restored. Now they can.

• When loading via ETL with multi-threading turned on, debt notes were not showing the associated Job ID and Job Task ID. They are now.