You can expect up to 15 minutes of downtime to deploy this release.
Image Displays Sunny Beach with Coastal Blooms
In This Issue
Rainmaker Intake
Client Access User Interface Configuration
Client Access Folder
Account Classification
Account Placement ETL
Text and Email Message Profiles
VA 2.0 Preference Profiles
Phone Blacklist
Email Vendor API
Rainmaker Intake
There is a new Rainmaker Intake feature. Customers can use this new feature to load accounts using a variety of received files that don't match an easily ETL loadable format.
For example, if you receive a PDF file with one page per account, a scanned image of a page for an account, or a handwritten document, those documents can be processed through Rainmaker Intake and be loaded into ACE.
For more information read: Rainmaker Intake
Image Displays Example Rainmaker Intake Profile Configuration
Client Access User Interface Configuration
The Client Access User Interface configuration has been updated to include additional configuration options.
Please see the article related to Client Access for more information: Client Access Configuration.
Client Access Folder
Client Access Users can now access their personal folder when logged in, provided the Client Access UI is configured to allow access and the Client Access User Profile has an upload folder configured.
Account Classification
There is a new option to set Classification at the Account Level when a single client may have more than one classification of accounts.
See this article for more details: Client and Account Classification.
Image Displays Classification Field in Debt Information Section on the Account Page
Account Placement ETL
Account Placement ETL now includes options to reopen previously recalled or canceled accounts during a placement load, reusing the existing account instead of creating a duplicate.
When reopened, the account is updated with new demographic data provided in the file and mapped balance values from the load file, including the reactivate code and reason when provided.
Image Displays Data Options Section in Account Placements ETL Profile Page
Text and Email Message Profiles
A new format_percent function is now available for text and email message profiles. It accepts a variable that represents a decimal number (e.g., 0.8) and converts it into a percentage format (e.g., 80.00%).
For example:
Expression | Result |
|---|---|
|
|
|
|
|
|
|
|
VA 2.0 Preference Profiles
There are two new options in VA 2.0 preferences for ACH.
A maximum dollar amount can be configured for ACH payments. If it is set, ACH will present an error if a payment above the amount is attempted. For payment plans with any payment above the amount, ACH will not be available.
A selected logic block can be used to prevent ACH from being available for payments or payment plans when the logic evaluates to true.
If ACH is unavailable and a No Cost/No Fee to Biller option is available, it will be presented to the consumer. If multiple card options are available, the No Cost/No Fee to Biller option will be the option presented.
Image Displays Payment Options settings within a VA 2.0 Preference Profile
Phone Blacklist
There is a new Utility menu option called "Phone Blacklist". Any phone number that matches a rule on this screen will not be saved to ACE. The Phone Blacklist feature also allows for remediation of existing phone numbers matching a number added to this list.
Image Displays Phone Blacklist Rule Page
Email Vendor API
A new API endpoint is now available for retrieving email templates using a template identifier and Email Vendor ID.
Previously, email templates could only be retrieved using the numeric emailTemplateID. This endpoint adds support for retrieving templates using the combination of template identifier and Email Vendor ID, which matches how the application internally resolves email templates.
This enhancement allows API consumers to retrieve templates using the same lookup method used within the application.
Image Displays Email Vendor API
Fixed These:
PayNSeconds transactions with an "Invalid" provider status were not being updated as expected. Those transactions will now be processed as failures instead of remaining in a PENDING status.
A canceled account without an active debt_status could not be successfully reactivated. This has been fixed.
Demographic data was not being restricted as expected (based on permission roles associated with viewing explicit demographic types) in the summary section of the account page. This has been fixed. Account summaries will no longer show demographic values when a user viewing the data does not have the permission matching the demographic view.
Please note: If a user is unable to see demographic fields in the summary section they could see before this change, it will be important to provide them with the Permission Role that has the view permission for that demographic type. For example, if a user can no longer see Patient demographic fields in the summary section, they need to have the “DEMOGRAPHIC_VIEW_PATIENT” permission.
Loading data via ETL would, in some circumstances, fail to update the commission rate based on the Commission Rate ID or Identifier. Both Legacy and Optimized Account Updates ETL Load Methods now properly update the commission based on the commission rate in the file being loaded.
There was a scenario where deadlocks caused the OnAfterPaymentSuccess trigger to fail. This was fixed.
The onAfterPrimaryAgentChange trigger was not being initiated when the primary agent changed due to Account Workflow Actions. This has been fixed.
Speed Posting notes were not persisting while working from the Speed Posting page. They are now.
Historical text message history was erroneously impacting Rainmaker functions when a consumer was using chat for communication. This has been fixed.
Attempting to modify a standalone single instance form and save it was resulting in an unexpected error. That has been fixed.
A text message was not being sent as expected when the ignoreOptInRequired parameter was passed as true. This has been fixed.