Release Notes 04/14/2024

Deploy

You can expect up to an hour of downtime to deploy this release.

In This Issue

• TCN Update

• Two Way Email

• Email Vendor Templates

• Inbound and Outbound

• Inbound Email Attachments

• Email Vendor Identifier

• Bundles

• Bundle Group Logic

• Bundle List Selection

• Contacts, ETL and Forms

• Payment Calculation

• Triggers / Action Paths

• Action Codes

• Nuvei

• Search by Debt Flag

• VA 2.0

• Worklists

• Fixes

• Account Workflow Actions

!!! TCN Update !!!

IMPORTANT

To avoid disruption, customers using TCN must take action and prepare to update some configuration due to required TCN updates. These changes will dramatically improve click to dial functionality.

A summary of the changes are as follows:

The TCN Password is no longer required in User Profile TCN Agent Settings

Agencies must request OAuth credentials (specifically, client id and client secret for the Operator API) from TCN and should do so in advance of the release - these credentials are different from the API username and access token

In TCN, the agency will need to generate an Access Token for the API and should do so in advance of the release (this token expires and needs to be updated annually)

Immediately after deploying this release, the new OAuth credentials and Access Token will need to be configured in the ACE TCN Vendor page

Additional configuration details and agent visible changes can be reviewed in ACE Help under the TCN Vendor Category.

Two Way Email

Two way email is now available in ACE. Please reach out to sales@interprose.com to request more information about enabling this option in your ACE application.

In addition, be watching for an announcement regarding a demonstration of these updated features. Articles in ACE related to these features can be found in ACE Help under the Two Way Email Category.

Email Vendor Templates

When a new email vendor is created, a set of default email templates are now automatically created and associated with the new vendor.

Only active profiles will show up in the Setup → Emails → Profiles list. Active Email Profiles with the same name will be distinguished in lists and dropdowns by also showing the email vendor. Inactive Email Profiles will be accessed on their associated Email Vendor page.

Inbound and Outbound Email

There is now an Outbound column in Email Logs to distinguish between inbound and outbound email messages.

The inbound email messages are also now highlighted in a different color.

Inbound Email Attachments

When attachments are received in an email message there are three actions that can be applied to the attachments.

    - Download

    - Store in account documents

    - Store in account documents and make VA visible

Email Vendor Identifier

In the Email Profiles list there is now a column for Vendor Identifier.

Bundle Group Logic

Logic Blocks associated with Bundle Groups now have a direct link to the Logic Block page.

Bundle List Selection

There is a new option under Setup → System to Default Bundle Selection for Payments/Plans, Dispute pages and Bankruptcy pages.

When set to true, only the account page the user is on will be selected by default when users are posting transactions, entering payment plans, entering dispute records or entering bankruptcy records.

Please Note:

When this option is set to true, the bundle lists will also be collapsed by default. It is important that agents be trained to expand bundles when they need to apply activity to other members.

Contact Details, ETL and Forms

The ${debt.nextScheduledAmount} and ${bundle.nextScheduledAmount} fields will now include any applicable service fee.

The text message log will now automatically populate the most recent unresponded text message.

A demographic_phone.id can now be mapped in an ETL profile using the Phone Number ETL load method so an existing phone number can be updated when the associated file includes the phone number’s ID from ACE.

There is a new field available to include when exporting form details that can be used to update form data via ETL. It’s called form_id. Updated form records will result in debt notes. ETL Overlay is used with form_id to update form records.

Form Fields can now be added to email profiles from the ACE Fields Account Fields drop down selection list. Multi-Instance Forms are not eligible to be added.

Vendors associated with Email, Letters & Text Messages are now listed only under those associated menus. They have been removed from the Setup → Vendors menu to reduce confusion and redundancy.

Payment Calculation

We have improved the accuracy of payment calculation associated with estimated interest. This will reduce the incidence of small balance over and under payments related to payment plans.

Triggers / Action Paths / Action Codes

Triggers / Action Paths

There is a new onAfterDisputeUpdate trigger that can be configured to initiate an action path for each account associated with an updated dispute record.

Trigger descriptions that were not previously populated have been updated for clarity.

There is a new Flow Action available in Action Paths that can be used to reassess the primary account in a bundle based on account changes that may not otherwise reassess the primary account.

For more information about triggers, please go to the Triggers Category in ACE Help.

Action Codes

Action Code Actions now include a Type of Account Attorney ID which can be used to SET_FOCUS on the Account Attorney field.

There is a new “User Note Required” field on the Action Code page. When populated with a message, a user note will be required after selecting the action code and the message populated will be displayed.

Action Code list column headers are now sortable.

Payment Destination External Fields

External Fee fields that store details associated with some payment destinations are now viewable columns in the following lists

• Transaction lists in Payment Batches

• Completed Transaction lists in Payment Plans

• Payments And Transactions Search results lists

Search by Debt Flag

There is a Debt Flag field in the Search page now that can be used to locate accounts that have a specific debt flag.

The ACCOUNT_SEARCH_DEBT_FLAG which is now associated with any role that had the SEARCH_VIEW permission is required in order to use this search field.

The * wildcard can be used to find accounts based on part of a debt flag.

VA 2.0

Consumers will now be able to enter or edit their email address from the Dispute and Contact Us pages in VA 2.0.

Worklist

Agents can now move through Static Worklists using "Next" without being required to enter a next work date on the account.

Account Workflow Actions

In addition to being able to select Email Sent in Account Workflow Actions to set Last Work Date, Email Scheduled can now be selected. This may help reduce the number of Last Work Date Changed debt notes that are stored to the account.

Fixed These:

• Agents were not seeing the expected account presented in Static Worklists when using “Next”. Fixes were put in place to correct Static Worklist behavior.

• The Build Worklist Job Task was not sorting Static Worklists as expected. It is now.

• Compliance contact window counts are recalculated nightly based on new contact activity. This sometimes resulted in an account continuing to be restricted based on prior activity (outside of the contact window) at the time new activity occurred. Now, compliance contact window counts are recalculated at the time of the new activity and nightly. Please note: email contact activity loaded via ETL, will continue to be included in the nightly recalculation and not at the time the records are loaded.

• The last failed job message was persisting on the Job page after a job completed successfully. It is no longer showing when a job completes successfully.

• Following a previous fix, emails were going out for non opted in email addresses for profiles set with a category of ADDITIONAL_NOTICE. This has been fixed.

• The position field in action code lists was not useful and was removed to reduce confusion.

• The Service Fee was not automatically being updated when switching to a payment batch with a different applicable service fee from the post transaction page prior to saving the payment. It is now.

• There was a scenario where a customer was seeing duplicate remits after invoicing. That has been corrected.