The release notes for December 2022 are organized as follows:
- Release Overview
- What’s New (3)
- What’s Improved (1)
- API Updates (2)
2022-12 provides several new features and significant improvements to DebtPayPro. 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".
FORTH Rebranding Update
As you know, DebtPayPro and Debt Pay Gateway are combining into one company, to be named Forth™. As part of this effort, we have created a Transition Guide (Click HERE) to help guide you with updates to URL's, and Contact Information. This transition will become effective on Monday, January 9th, 2023.
Added MAVIS Barcode Authorization System (DPG-1040)
The new MAVIS (Machine Assisted Verification & Identification System) functionality allows DPG to generate, scan and read secure barcodes containing consumer information on the DPG Account Agreement document. This automates the document validation process and improves and brings efficiencies to the enrollment process.
Added the Ability to Link a Non-Enrolled Debt to an Uploaded Document (CRM-I-562) DPP-15545
This new feature was developed to prevent unneeded enrolling/de-enrolling debts for the sole purpose of associating a document. It is useful for a client to be able to attach files to non-enrolled debts as this would save time in the future, should the contact decide to enroll the debt later on.
Added Trigger Condition for "Assigned To = Client" in Task-related Events (CTX-I-112) DPP-14989
Formerly, clients could not filter task event triggers using a condition of "assigned to = client." The "assigned to" dropdown menu only displayed users. Clients want to quickly access the contact dashboard when they receive an "Event Scheduled" notification email. This new feature enables clients to build additional automation around tasks being completed by their customers and updates the "assigned to = client" field automatically whenever a new task is created in the CRM.
Updated Several Document User Interfaces (DPP-15402)
After receiving feedback from clients, changes to the Documents User Interface were made. These updates are listed below:
Wrapped the “file name” and “description” columns into two lines
Deleted the “For Debt” column due to redundancy
Renamed “Debt/Creditor Name” to “Debt/Creditor”
Moved the value in the “for debt column” to the “debt/creditor” column
Removed duplicated tables in contacts and advances tabs
Ensured grid renders in the Advances tab under the “documents” section of an advance.
Fixed document permissions
Array Knowledge-Based Authentication Update (DPP-14535)
This modification updates our method of authenticating with Array at the moment of pulling credit to align with Array's custom authentication. The pull credit report feature (which occurs in the background) now provides a new authentication process that launches when you click the "Pull Credit Report" button (see image below) from the Client's Dashboard (If the "Pull Co-Applicant As Well" checkbox is selected, verification will add questions from the co-applicant's credit report). After this, knowledge-based authentication questions based on the client's credit report appear for verification.
Added Secure Contact & Company Level API Access (DPP-15620)
We modified our authorization and access protocols as part of connecting to our API. As part of our original vision to enable seamless programmatic connections to our platform, API keys previously allowed direct access to records via ID without enforcing some of the strict sharing controls as they exist within the CRM UI. Based on evolving use cases and feedback from clients requesting stricter enforcement of access control, Forth will be making updates to the API as described below.
1. API Keys will be limited to the scope of a user's shared company hierarchy, i.e. records are limited to the current company that a user is a part of, any downstream child companies of that company, and any companies identified in the “Company Contact Access” on a users profile under the Admin tab.
2. For API performance reasons, secondary assignments of companies will not be examined to determine record access. If Company B is secondarily assigned to a particular contact within Company A, then an API user in Company B will not be able to access that record unless they’re a parent of Company A in the company hierarchy.