- Print
- PDF
Continuing to grow together!
We're adding more enhancements as a direct result of your great feedback at the InterProse ACE User Conference in January. Here are a few you'll see with this release:
New Itemization Bundle Spread Methods.
The ability to Modify Payment Plans.
The option to select an email template in Report Runner job tasks.
New columns in Transaction lists.
Read More about these new features in articles below.
Enhanced ELS Updates
Enhanced ELS now includes the Open Date when the consumer first opened the message along with a Last Open Date when the consumer most recently opened the message.
With Enhanced ELS, Email Log Status is also now updated from SENT to OPENED after a recipient has opened the message.
Enhanced ELS requires the use of the AWS email service integration and is a package add-on. Contact sales@interprose.com. for more information about this exciting new option.
Bundle Spread by Itemization
You can now spread payments to accounts with new Bundle Spread Methods based on the Itemization Age. Labels for existing Bundle Spread Methods have also been updated. For more details related to how each Bundle Spread Method works, please use "Get Help" from the ACE Help menu and search for the article on "Bundle Spread Methods".
Payment Plan Modify
Payment plan details can now be modified. Users who have the PAYMENT_PLAN_MODIFY permission will see the new Modify option next to the Apply and Deactivate options.
When selecting the option to modify a payment plan, ACE will automatically deactivate the old payment plan and present the payment plan page to allow the user to update and save the variables of the plan while retaining the payment credentials.
The new Modify option is also available to be used with Settlement type payment plans.
Just as with a new payment plan, a payment scheduled for the same date will begin being processed in ACE when the payment plan is saved.
Report Runner Email Template
Report Runner: Client and Report Runner: Run as User job tasks can now each be sent using a specified email template with the option of a distinctive subject, body, from name and/or from email address.
If you do not identify a specific email template/profile in either of these job tasks, a default "REPORT_DELIVER" email template/profile will be used.
For example, for "Report Runner: Client", client specific fields that are available for email templates can be used. However, for "Report Runner: Run as User", the job task will not be able to distinguish a client or user in association with the report being sent.
New Transaction Columns
Two new columns are now available to display the Client Account Number and/or the Client Code when viewing Owing, Received and Overpayment Transactions.
New Permissions
A new permission called "ACCOUNT_FORM_COPY_TO" has been added. If this permission is removed from existing permission roles, users won't be able to copy data from a standalone form to multiple bundle members.
A new permission called "FORM_BUNDLE_VIEW" has been added. If this permission is removed from existing permission roles, users won't be able to enter data into a standalone form and apply the same form entry to multiple bundle members at the same time.
The two permissions identified above will show up automatically in any of your permission roles that currently have the "ACCOUNT_SAVE" permission.
Action Codes
The method of reordering Action Codes has changed.
The list of configured Action Codes is visible under the menus for Setup - Workflow - Action Codes. Previously, the list could be sorted in an explicit ascending or descending order only by clicking the Action Code column header.
Now, when configuring the list of Action Codes, the user can click and drag Action Codes up or down to define the explicit order they want the list to be presented in.
Agents will be see the Action Codes in the Account page dropdown list in the order that has been defined.
Form Select Type Fields
By default, Select Elements, in Form Select type Fields, now sort in the order they were originally entered.
ETL
ETL Bundle Propagation
Previously all contact records loaded via ETL (phone, email, address) were added to the primary account in the bundle.
Now, ACE will load data to the member account specified in the file if you are not propagating the demographic type being loaded.
Current functionality is retained if you have propagation enabled.
ETL Phone Numbers Load Method - Location
When using the ETL Phone Numbers Load Method, the location will only be overwritten if the mapped column is populated. In order to update phone number an empty location column can be mapped.
ETL Payments Load Method - Preferred Method of Contact
A preferred method of contact can now be mapped and loaded from the payment data file when using the ETL Payments Load Method.
Demographic Email Address Status
Demographic Email addresses now have a status associated with them. The Demographic Email Status is also now available from the SQL Report Designer using the demographic_email.status field.
Solutions By Text (SBT)
When ACE detects that Solutions By Text (SBT) has identified a phone number as inactive, the number will be opted out in ACE.
Fixed These:
- A fix was put in place to prevent the saving of incomplete itemization transaction rows.
- There was a periodic problem where the second page of account notes would show as blank. The problem has been fixed.
- Using the Back to Worklist flow action after the prior worklist is deleted no longer throws an error.
- A problem with client profile metadata being updated erroneously has been corrected.
- ACE automatically generated passwords were not always working as expected. They are now working consistently and will have at least 12 characters along with symbols from this list: '!', '#', '$', '*', '%', '?', '@'.
- The Voicemail Drop Source per the Dialer Code combined with the call date is now accurately setting the Voicemail Drop Date and Voicemail Drop Age.
- A change was made to improve workflow that impacts the setting of the Original Demographic record when new accounts are placed.
- A problem was discovered where an ETL Transactions profile with Conversion set to true and Do Not Invoice set to true was loading transactions with Do Not Invoice set to false. The problem has been fixed. Please note: a mapped and populated Do Not Invoice value (true or false) will override the setting in the ETL profile.
- A problem where the wrong accounts were being notated while working accounts through a dialer campaign has been fixed.
- There was a problem with data being loaded to multi-instance forms which has been fixed.
- An error is now thrown when a user attempts to change a multi-instance Form in ACE to a single instance Form.
- The ability to Recall Forwarded Accounts has been fixed.
- Users are no longer able to paste text into a form field type of PHONE.
- An "Error: insert or update on table "letter" violates foreign key constraint..." message was showing up in the job when a letter was scheduled following an ELS letter. A fix has been put in place for the particular situation that was causing this error.
- Logic blocks using the Client Type Classification Label field no longer results in an error and does return accounts associated with the value specified.
- When re-spreading payments the spreader no longer needs to be selected twice.