Release Notes 12/12/2024
    • 13 Dec 2024
    • 4 Minutes to read
    • Contributors
    • PDF

    Release Notes 12/12/2024

    • PDF

    Article summary

    Deploy

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

    Image Displays Peaceful Nature Scene

    In This Issue

    • Form Visibility

    • Payment Plan Job

    • Payments

    • Transactions

    • Deceased Records

    • Bankruptcies

    • VA 2.0 Primary and Sub Clients

    • Payment Offer via Text

    • Email

    Form Visibility

    A logic block can now be selected to define when the form should be visible to be accessed on the account page.

    For example, if an account form is used only in relationship to a specific client's accounts, logic saved to the configured form will limit the form to being visible only when viewing those accounts.

    Image Displays Account View Visibility Logic Block Field for Form Visibility

    Payment Plan Job

    The Payment System: Payment Plans Job Task now has a field where a Thread Count can be identified. If empty, the job will treat the task as if the Thread Count is set to 1. Increasing the thread count is expected to increase the performance speed when this job task runs.

    Image Displays Payment System: Payment Plans Job Task

    Please Note

    Due to various configurations between ACE and the payment destination, it is recommended that you test changes by modifying this number incrementally until you discover the optimal speed for your specific configuration.

    Payments

    Payment spreader selection in VA 2.0 has been improved.

    In the Virtual Agent, when a consumer is able to post a payment to multiple accounts in a bundle, if the primary account in the bundle is one of the accounts being paid, the spreader for that client will be used when applying the payment.

    If not, one of the spreaders associated with the other member accounts being paid will be used when applying the payment.

    Transactions

    Google Pay and Apple pay have been added as search options to the Transaction search page Card Type list. Diners Club has been removed from the same list.

    Image Display Card Type Search List

    Deceased Records

    There is a new text field available to be populated when entering/saving a Deceased record to an account. it’s called the Estate Executor. It is also available in the letter database to be added to a letter and it is a field in an ETL profile using the Deceased load method. For more information, please review the article related to the: Deceased layout.

    Bankruptcies

    In October there was an update made so dismissed bankruptcy records can be opened from dismissed bankruptcy notes.

    Following that update, Logic Blocks referencing dismissed bankruptcies began to result in errors.

    There is a new trigger that can be used explicitly for dismissed bankruptcy workflow: “onAfterBankruptcyDismissed.” Accounts associated with a dismissed bankruptcy will only be in context for logic blocks at the time the bankruptcy is dismissed and will not be available via logic conditions later.

    Please Note

    Any workflow associated with dismissed bankruptcies will need to be reviewed and updated accordingly.

    VA 2.0 Primary and Sub Clients

    When using one of these fields, ${client.logo}, ${client.consumerLogo}, via email or other communication methods, the following behavior is expected:

    • If the logo field is populated in the sub client's profile, it will be used/displayed

    • If not and the logo field is populated in the primary client's profile, it will be used/displayed

    Inside of VA 2.0:

    • If a sub client is explicitly associated with a VA 2.0 profile, the configuration of that VA 2.0 profile should be respected for the sub client’s accounts logging into VA 2.0

    • If a sub client is not associated with a VA 2.0 profile, the configuration of the primary client’s VA 2.0 profile should be respected.

    Please Note

    "Most Restrictive" value checks such as "Minimum payment amount" will continue to be determined between the account or sub account’s client and the VA 2.0 profile only, including those situations when a sub client account is otherwise using the primary client’s VA  2.0 profile configuration.

    Payment Offer via Text Message

    To provide a delivery method for offers via text message, there is now a specific auto login link available for use. For additional details see this article: How Do I add an Auto-Login Link in Text.

    Email

    Email Profile table formatting options for table loops have been updated to enable more flexibility in email formatting. Please see this article for additional information: Email User Interface.

    Fixed These:

    • Email addresses associated with bounced emails were being deactivated, but were not being demoted in priority below other active eligible email addresses. They are now. See this article for additional details regarding email status: Email Address Status and Priority Handling.

    • The onAfterDemographicEmailStatus trigger was not being initiated after an email associated with the demographic email address bounced. It is now.

    • Action Path Logic Conditions referencing demographic phone, email, or address were resulting in an error. That has been fixed.

    • The Validation Notice sent date was not being updated for all member accounts as expected. It is now.

    • When selecting an email alert, an error was showing "body not found in context." This has been fixed and the error is no longer displayed.

    • Status was not being updated for MMS text messages in the same way as SMS text messages. It is now.

    • An inbound email to a demographic email address that existed on multiple accounts was resulting in an error. That is no longer occurring.

    • Customers with multiple app servers were seeing incorrect data in the user session report. An issue was identified where users could be out of sync. The issue was corrected.


    Was this article helpful?

    Changing your password will log you out immediately. Use the new password to log back in.
    First name must have atleast 2 characters. Numbers and special characters are not allowed.
    Last name must have atleast 1 characters. Numbers and special characters are not allowed.
    Enter a valid email
    Enter a valid password
    Your profile has been successfully updated.
    ESC

    Eddy AI, facilitating knowledge discovery through conversational intelligence