- Print
- PDF
You can expect up to one hour of downtime to deploy this release.
Virtual Agent 2.0 Updates
VA 2.0 User Interface (UI) Updates
Changes have been made to the user interface for the Virtual Agent Profiles configuration pages.
The following three options have been moved from the individual Virtual Agent Profiles to a new "General" section on the main configuration page you arrive at via Setup - Virtual Agent - Profiles:
Enable Chat
Support Bundle Selector
Enable Rainmaker Responses in Chat
Changes have also been made to the user interface for managing Customizable Text. The text was previously accessed from each main VA 2.0 Profile page. Now it is stored in a Custom Text file. The default file is called "translate.json" and the "Download Default" button can be used to download a copy to be customized for your use.
For more information about the Custom Text file, please use this link to the Custom Text in VA 2.0 article in ACE Help. This file is also referenced in the article below related to VA 2.0 Spanish.
VA 2.0 Bundle Selector
Configuring the VA 2.0 Bundle Selector will enable consumers with accounts in more than one bundle to choose which bundle to view when logging in.
For details about configuration and use of this feature, please use this link to the VA 2.0 Bundle Selector article in ACE Help.
VA 2.0 Spanish
VA 2.0 and the Custom Text default file have been updated to incorporate U.S. Spanish which will be displayed when a consumer's browser is set up to use U.S. Spanish as the preferred language.
For more information about the Custom Text file, please use this link to the Custom Text in VA 2.0 article in ACE Help.
VA 2.0 Bundle Group Filter
Bundle Group Filters applied to VA 2.0 Profiles allow you to limit which accounts will be available for a consumer to access when they log in.
For details on this topic, please use this link to the VA 2.0 Bundle Group Filter article in ACE Help.
VA 2.0 Account Document URLs
VA 2.0 document URLs are now available so an Agent can copy them from account documents and send them to a consumer. The consumer will be able to use the url received to view a document directly in their Browser.
For more information, please use this link to the Managing Documents in VA 2.0 article in ACE Help.
VA 2.0 Get in Touch With Us
There have been changes to VA 2.0 “Get in touch with us” / “Contact Us” page behavior based on configuration options.
For details, please use this link to the How Do I Configure VA 2.0 Profiles? article in ACE Help and look for the Blue note distinguishing "Get in touch with us" behavior.
VA Consumer Payment Credentials
A consumer can now modify their payment credentials in an active payment plan.
When the consumer selects the new option to "Change" they will be presented with the payment plan page where they can select a different or new credential method.
Future payments will be processed using the new credentials.
Payment Plan Enhancements
Move a Payment Plan to a Different Payment Destination
There is a job task, “Payment System: Payment Plans Move,” that now allows the payment destination used to be changed when a specific logic condition is met.
Update/Enter Values in Miscellaneous Fields on a Payment Plan
Users having the following permissions are now able to modify or enter values in those fields after a payment has been applied. The permissions are associated with the Manage - Transactions Permission Role by default.
PAYMENT_MISC001
PAYMENT_MISC002
PAYMENT_MISC003
PAYMENT_MISC004
ACH NSF Option
In October, an option was introduced to prevent an ACH payment plan from deactivating when a single NSF occurred on the plan. The feature added the NSF payment to the end of the payment plan and deactivated the plan when there was a subsequent NSF.
Intelligent Reschedule is a new option a customer can enable so a NSF that does not deactivate the plan can be added back to the end of the payment plan. If Intelligent Reschedule is not active and an NSF does not deactivate the plan (due to Intelligent Failure being active), the NSF payment will not be added back to the plan.
Invoice Enhancements
Invoice Email Delivery Template
There is a new option to select a distinct Email Delivery Profile/Template to be used for each Invoice Profile used in your ACE application. The existing default template, INVOICE_DELIVER, can now be reviewed and modified Setup -> Emails -> Profiles.
Invoice Aging Table Loop
Two new table options are available for client invoicing so customers may include aging data in their invoices.
Automatic
Create a table and use the table property named client_aging_loop
Include a row below the header, but do not choose fields for the row below the header. Leave them empty and they will be auto-filled.
It’s important that you add the column header names in the same order when using this table loop and leave an empty row below the column headers. This is different than other table loops used for our invoice and letter templates where you can rearrange the order.
Manual
Create a table manually and populate any values you want from new clientAging beans
Be sure to download a fresh copy of the Letter Data Source to get the new beans
The images below are representative of how these two tables may appear in your invoice template if they are set up to represent the same data.
Email Deliverability Dashboard Panels
There are two new dashboard panels available relating to email deliverability.
Email Deliverability Graph:
The graph represents email deliverability over time.
Selecting/deselecting the words displayed for each of these options will set the values to represent in the graph
Show All
Sent
Opened
Bounced
Email Deliverability Chart:
The Chart panel settings gear has an Edit option where the date range period of time to apply to the chart can be selected.
Email Profile Send and Edit Roles
It is now possible to apply a Send Role ID and a Edit Role ID to Email Profiles. This availability can be used to control which agents are able to view and select specific email message templates to send to consumers and which managers are able to edit specific email profiles.
Please Note
Unless you are using existing Permission Roles to use for the Email Send and Edit Role IDs, Roles (with or without permissions) will need to be created and added to the users as appropriate. You may need to reach out to ACE support to create new Permission Roles.
New SQL View Layouts
Two new views are now available for use in the SQL Designer. You can review the fields in these two views by downloading the Layout documents via Help -> Layout -> SQL Views.
user_alert
chat_log
Commission Rate Logic
Payment Receivers are now available to be used to distinguish Commission Rate Logics in Commission Rates.
Debt Purchaser Credit Reporting
There are two new fields you will see in the Credit Reporting section of a Client Profile page if the Client Collection Type is "0C - Debt Purchaser".
Only one of the two fields should be populated.
When one of these fields is populated, the METRO2 credit reporting file will store K2 segment details instead of K1 segment details.
Recalculate Collection Costs
There is a new job task “Recalculate Collection Costs” that can be used when collection cost rates have been modified.
It will not remove manually entered collection costs and it will only recalculate those costs associated with the specified Date Range.
When the “Direct Update” option is set to true, the job task will not initiate associated triggers, which might otherwise result in undesired behavior.
Fixed These:
A problem has been fixed where client charges were not being included when an invoice was regenerated.
Inventory Designer reports no longer show the word “BOOLEAN” in the report column headers for fields that are BOOLEAN values.
The option to mark a text message as Read was not available for a text received from a phone number that was not opted in for text messaging. The Read button is now available in that circumstance.
Collection costs were representing totals only associated with the stored rows displayed in the visible page. Now the collection cost total at the bottom of each page will always represent the full total of collection costs regardless of the number of rows represented in the page.
Changing the status of an email address to INACTIVE will now propagate the change to matching email addresses. The onAfterDemographicEmailStatusChange can be set up to initiate workflow when this happens and will now only be initiated once per e-mail record across the bundle.
The Alert menu time and status columns were broken with a recent release. They have been fixed.
Fixed a problem associated with reactivated payment plans where a trigger was initiating action paths incorrectly.
There was a null overpayment error related to spreading that showed up when speed posting after a recent change to defaults for spreaders. This problem has been corrected.
Speed Posting was not correctly choosing the right account when an account had a debt id number that matched a different account’s client account number. This has been fixed.
A problem where some copies of invoices generated were not respecting the Filename Override settings introduced in November was fixed.
There was a problem preventing unused invoice profiles from being deleted. That has been fixed.
Duplicate VA 2.0 login notes are no longer being created if the auth token appears in the url after a person has been authenticated.
Favicons for VA 2.0 can now be uploaded and applied for different VA 2.0 profiles.* (there is a separate polish ticket submitted due to a problem when using/replacing the same named favicon in two different VA 2.0 profiles / DEV-11944)
A fix was made so that the VA session record now includes the initial payment taken in the payment count along with the count for subsequent payments made during the same session.
There were some problems using Chat on some branches of ACE. Those have been fixed.
The Download Default buttons for VA 2.0 Profiles were sometimes resulting in the wrong file being downloaded for Custom Text or a Custom Color Scheme. That has been fixed.
The VA Chatbot url link was not routing to the url correctly due to punctuation being included in the url link. That has been fixed and is working correctly now.
Rerunning a Failed Payment was not behaving as expected. That has been corrected.