The release notes for March 2023 are organized as follows:
Release Overview
2023-03 provides several new features and significant improvements to Forth. 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
Xactus 360 Migration
As you're aware, our integration partner Xactus ended their relationship with MCL at the end of February. In order to support the transition from the MCL platform to Xactus 360, we have deployed the following new features:
- Added Xactus 360 to the Credit Parsing Tool
- Added {CREDIT_UTILIZATION}, {CREDIT_TOTALLIABILITY} and {CREDIT_SCOREFACTORS} functionality for Xactus360 (CRM-I-888/866)
- Add Applicant and Co-Applicant Credit Pulls with Xactus360 (CRM-I-688)
- Add Endpoint to Pull Credit from Xactus360 Service (see API Updates section at the end of this release)
Added Xactus 360 to the Credit Parsing Tool
The credit pull parsing tool (script editor) is something a lot of clients use to filter out creditors or trade lines that they do not want entering the system. This addition enables the Parsing Tool to be used with the xactus platform as it has with others like MCL.
Added {CREDIT_UTILIZATION}, {CREDIT_TOTALLIABILITY} and {CREDIT_SCOREFACTORS} functionality for Xactus360 (CRM-I-888/866)
This modification updates the Xactus360 Integration to capture fields relevant to existing tags for credit utilization and credit score factors.
Add Applicant and Co-Applicant Credit Pulls with Xactus360 (CRM-I-688)
Formerly, joint credit pulls were not functioning in conjunction with the Xactus360 integration. With this modification, we added support for this feature so that both applicants and co-applicant's can have their credit pulled jointly.
Added New Field to Debt Reports
This feature added a field for the number of Accounts Unsettled from the enrollments reports page to be available on the Debt reports on the Creditors tab.
Added a Delete Button on the Edit Triggers Page (CRM-I-674)
Formerly, when deleting a trigger we had to find the trigger, edit it to make sure we want to delete it, then go back to the main page just to click the delete button instead of doing it from the page we're already on. This new feature adds a delete button to the edit triggers page. This will reduce the need for users to jump between pages to manage the triggers that they are editing.
Document Package 2.0
This past month, we released a comprehensive update to our Document Package feature within the Forth CRM. This comprehensive update includes the following improvements:
- Document Package Splitting
- Document Packages Searchability
- Copy/Duplicate a Template for a Package
Package Splitting
Packages often have multiple pieces that need to be sent to different parties. The new Document Package Splitting feature allows our system to seamlessly split packages that are already signed through Clixsign into individual PDFs. These PDFs can now be downloaded (see image below), composed of the individual documents that comprise the package. These individual PDFs from the package will have the Clixsign certificate appended to them.
This feature eliminates the need for customers to leave the system to extract a document from a package and will reduce friction when uploading documents to third parties or other integrations that require specified documents pulled from a package.
Search for Document Packages (CRM-I-814)
This new feature provides the ability to search for saved Document Packages more efficiently than before. Before this, a user had to spend precious time scrolling through a list of packages to find a particular document.
This feature improves the usability of the Documents module by adding Search functionality by Document Package name or package ID field.
Copy/Duplicate a template for Document Packages
This exciting new feature provides the ability to duplicate an existing document package. All document templates part of the original package are copied to a new package. This new time-saving feature allows administrators to clone similar packages with a single click, instead of starting from scratch each time.
Added New Triggers and Enrollment Settings: First Payment Cleared and First Payment Return (CRM-I-598)
Until now, the status change upon first payment clearing/returning only looked at payment transaction #1 of the program. For clients who have triggers tied to a first payment clearing or returning, this may be misleading as the first payment that clears or returns may not be the first numerical payment in the program. As such, we introduced a new enrollment event for the first instance of clear or nsf payment and clarified how the first numerical payment that fails or clears is distinct from the first instance.
What's Improved
Modified the Balance Amortization Calculator
Forth made some performance improvements to the balance amortization calculator. The updates were focused on increasing the speed of balance and amortization calculations within the settlements interface and laying the groundwork for exciting new mass payment management features that are on the horizon, to help make servicing easier and more efficient.
Changes are purely in backend algorithms, and there are no changes to the user interface or any modules within the system.
Modified Moneveo Access Integration
Monevo is streamlining its hosted experience from individual branded domains to a single domain that is driven by the campaign code to show any client-specific branding. As a result, our integration with them now requires us to always use the same base URL - app.monevo.us/apply - in all instances of the app link getting sent to the customer.
This update benefits the user by streamlining the Monevo Access integration by standardizing the base URL and by providing a more uniform client experience across all customers using Moneveo Access.
Added Suspension Date to Database User Table (CRM-I-914)
With this modification, Managed Data Cloud users now may easily retrieve a user's suspension history. Formerly, the only way to find the date/time a user was suspended was by searching the system log, which is time-consuming and inefficient. The system now stores the date and time of the user's last suspension in the database user table. This information is updated whenever the user is suspended or re-suspended, and includes the user ID of the person who suspended the user.
By storing the suspension history in the database user table, administrators can quickly access the necessary information without having to search through system logs. This will save time and improve the overall user management process.
Modified the Pull Credit Report Interface
This modification enhances the "Pull Credit Report" button by adding a dropdown menu. This will enable users to select their preferred credit pull provider. It improves the user experience for credit pull providers by providing a modular, user-friendly, and easy-to-use interface for requesting and retrieving credit reports.
Additional Updates to Contact Notes and Alerts
Since deploying a major update to the Contact Notes and Alerts user interface, we received several requests for further enhancements.
- Increasing the Page Size for Notes
- Updating Note Template Search Dropdown Menu
- Make Templates of Excluded Note Types Unavailable
Increasing the Page Size for Notes
Until now, the maximum page size for notes in our application is 10 notes per page. This modification increased this limit to 50 notes per page to provide more flexibility and accommodate users who need to view more notes at once.
Updating Note Template Search Dropdown Menu
Formerly, the note template dropdown appeared to be a searchable field when there are fewer than 10 templates when it is actually now a dropdown menu. This modification updates the dropdown field so that it reflects as a dropdown menu and not a search field.
Make Templates of Excluded Note Types Unavailable
Note templates created with note types that are “excluded” as valid note types a user can select are displaying as available regardless of the note type’s exclusion status. This leads to a situation where note types that a business has elected to exclude from use can still be applied by a note template. This leads to an adverse situation where the business is saving notes with a type that they do not wish to have users save which can impact reporting or operational activities.
Updated the Settlement Return Process
This modification updated the settlement return process by creating a connection between the original transaction processed and the offsetting transaction so that the debits and reversal tied to the deposit can be linked and viewed.
The goals for this modification include keeping the cleared date and the original transaction so that the reporting doesn’t change; offsetting the reversal with a new transaction so that the original transaction will still be a withdrawal of funds from the account; and ensuring that the new transaction offsets the original transaction and also shows that it is tied to the original transaction. All of this provides greater clarity and transparency for our clients.
API Updates
Add Endpoint to Pull Credit from Xactus360 Service (CRM-I-871)
This update allows a client to add an API endpoint to the existing system that can pull credit information from the Xactus360 service so that the Client can pull a credit report on an enrolled contact. The pulled credit information will be retrieved based on the unique identifier Social Security Number.