The release notes for February 2023 are organized as follows:
- What’s New (12)
- Added Creditor Current Payment to Servicing Tab for Affiliate Accounts (CRM-I-874)
- Added New Triggers and Enrollment Settings
- Added Data Source Logging
- Added a New Settlement Commitment Tag (CRM-I-847)
- Added a New Tag for the Number of Consecutive Returns (CRM-I-833)
- Added Document Packages into Trigger Conditions (CRM-I-649)
- Added Not Enrolled Debt Tags (CRM-I-740)
- Added Administrative Control for Users' Notification Settings (CRM-I-852)
- Added a NewLine Loan Integration
- Added Two-Factor Authentication
- Added a Debt Field to Debt Reports
- Additions of Features associated with Lender Submission
- What’s Improved (5)
- API Updates (2)
Release Overview
2023-02 provides several new features and significant improvements to the Forth system. Note that the acknowledgment of releases that originated as requests via the Forth Aha IdeaBoard are assigned an Aha Number in the following format - "CRM-I-XXX".
What's New
Added Creditor Current Payment to Servicing Tab for Affiliate Accounts (CRM-I-874)
With this new feature, the Servicing Tab on the affiliate's account would reflect the creditor's current payment in the "Creditors" section. This was developed to have the creditor's current payment reflected on the servicing tab as this will help with retention. This shows the creditor's individual current payments as well as the total current payments (just like on the debts tab). This was needed on the servicing tab so that a client may remove or add debt after the file is submitted to the servicing company and there isn't a way for the affiliate to know.
Added New Triggers and Enrollment Settings
Currently, the status change on the first payment clearing/returning only looks at the first payment of a program. For clients who have triggers tied to a first payment clearing or returning this was misleading as the first payment that clears or returns may not be the first numerical payment in the program.
This new feature introduced a new enrollment event for the first instance of a return or cleared payment and clarified how the first numerical payment that fails or clears is distinct from the first instance. This feature also gives clients more options in their messaging around first payments clearing or returning vs the first instance of those events
Added Data Source Logging
Users are currently unable to see the results of posting in via a data source. This data should be retained temporarily and presented to the user for debugging purposes. Additionally, adding "_debug=true" to the end of the data source URL now toggles this feature on or off.
Added a New Settlement Commitment Tag (CRM-I-847)
Clients have debts that are settled with open settlement payments. This new tag {SETT_COMMIT} provides the ability to reflect the settlement commitment, pulled from the sum of all open settlement payments on the schedule) for a given customer on an email template, sms template, or document template. This feature then generates the client’s settlement commitment upon rendering the template.
Added a New Field and Tag for the Number of Consecutive Returns (CRM-I-833)
This new feature creates a new field on contact lists called “Number of Consecutive NSF Payments", providing the ability to represent the number of consecutive NSF payments on a client's schedule in an email via a new tag titled {NUM_CONSECUTIVE_NSFS}. Additionally, it provides a new filtering capability for clients on a list by the number of consecutive returns.
Added Document Packages into Trigger Conditions (CRM-I-649)
Document templates currently have limited to no functionality in conjunction with our triggers system. Just like we have events for when a document gets sent via Clixsign, we would like to enable the same functionality for document templates. This new feature will expand our automation capabilities and allow clients to further automate their processes. This would further align document package capabilities to individual template experience in triggers, as well as enable more notifications and automation around document packages. The trigger event names are "Document Package Complete", "Document Package Declined", "Document Package Status Event", and "Document Package Email is Opened".
Added Not Enrolled Debt Tags (CRM-I-740)
This new feature provides the ability to display accounts that are not enrolled in a program separate from accounts the consumer is enrolling in the program. This would be reflected as the same table for enrolled debts just showing the un-enrolled as well. This feature is enabled by creating a new tag that generates a tag similar to the {CreditorList} tag. These new tags are {CreditorListUnenrolledOriginal} which uses original_debt_amount and {CreditorListUnenrolled} which uses current_amount.
This feature helps your sales team ensure they are not leaving out any qualified debts for enrollment.
Added Administrative Control for Users' Notification Settings (CRM-I-852)
Currently, only an individual User can update their system alerts for contact opens my emails. This new feature provides the capability to control whether or not users receive system notifications without having to log in as them and modify their "my settings" page. This would enhance administrative functionality around system notifications.
Added a NewLine Loan Integration
NewLine Loan offers debt settlement program loans for consolidating debt. With this new integration, NewLine is now a program option available to clients to pay off their debt. The NewLine integration is used after a client has already been enrolled in a program and wants a loan to pay off that program.
This feature relies on the Forth client being enrolled in the NewLine Loan program (confirm with Forth Sales if you have any questions).
Added Two-Factor Authentication
This effort makes updates and standardizations to the two-factor authentication (2FA) experience by providing enhanced security controls, better administration, and improved organization.
This enhancement creates a new “Access Control” Settings Page, found at the controlling company level (the highest level company within an account). Once enabled at the account level, specific companies can have 2FA functionality enforced on them.
Added a Debt Field to Debt Reports
This new feature added the Debt field "PAPERWORK RECEIVED DATE" as an available field for Debt Reports.
Additions of Features associated with Lender Submission
Several improvements, associated with a pending Lender Submission Process, were developed and released in the month of February. These three improvements are listed below:
Lender Submission Setup Page
- We introduced a new Lender Submission page. This page is accessible by a new tab named "Submissions" under the lender details view. This new tab will contain several different controls, including "Submission Methods" where you can select either Email or API.
Logging
- This new element of the lender submission process allows for logging of the entire Lender submission process with specific identification. Logs will also be maintained for API submission similar to email submission.
CTX API Lender Endpoints
- We added the capability to add a Lender Onboarding process API using OAuth. This adds a new API call for submission to GET Submission Details, GET Submission Statuses, as well as Update Submission Status.
What's Improved
Standardized Debt Updates Logging Rules (CRM-I-794)
This modification provides standardized, expectable behavior for History tab logging of debt adding, removing, or updating. It only logs debts that are being updated or removed when the Edit Debts page is saved. These saved changes are then logged into the History Tab.
Modified Enforcement of Required Fields on External Forms
Formerly, External Forms could be configured to have required fields. However, when the forms are sent to end users, those required fields are not actually required to be filled in to complete the form. This modification introduced enforcement for all fields in the external form that have been designated as required. This feature now ensures that External Form submissions require all fields input to be completed.
Modified the Viewability of the Balance Forecast Chart in the Settlement Scheduler
This modification added a setting under the Settlement settings → General settings section to hide or show the Balance Forecast Chart within the Settlement Scheduler.
Modified MAVIS Review Reasons
This modification strengthens the MAVIS Automated Review Process. When an unknown programming/scan error occurs with MAVIS, the manual review reason should now be "Scan Error". When an unsupported document is uploaded the review reason should now be "Unsupported Document".
Comprehensive Updates to Contact Notes and Alerts
This extensive modification to the Contact Notes and Alerts user interface and features improves the user experience within our CRM. enhancing the visibility of alerts and empowering users to find the important information they seek (note type, creation date, date last updated, etc.).
We added several additional search criteria to speed up the search for existing notes about your customers. You can now search by Note Type, the User who created the Note, the timeframe that the Note was created, as well as sorting by the most recent or oldest Note.
You also told us that you wanted a more modern Alerts experience, with greater options to customize different alerts by priority and allow for an automatic expiration date for your alerts. We took your suggestions and enhanced our “Alerts” feature as well. You can assign Alert Type (priority level), and expiration date if desired.
API Updates
Add Endpoint to Update ACH Returns
Automated Clearing House (ACH) payments processed through NACHA files for CTX clients require manually updating returned payments. This is very time-consuming and for clients that have ~250 transactions daily to update, this saves tremendous time and money. The current solution will allow updating returned payments by hitting a data source endpoint.
Add ForthCRM API Command to sort Contact Notes (CRM-I-842)
Formerly, in trying to get the more recently inserted notes from contacts through the API, it was noticed that the instructions for retrieving such notes did not have that option. In some cases, contacts may have more than 100 notes and the API was restricted to show only the first 100. This update provides an API command that will sort the results from the newest to the oldest.