Several improvements, associated with a pending Lender Submission Process, were developed and released in the month of January. These three improvements are listed below:

New User Type

• We introduced a new User Type called "Service Account". This is a different kind of user, one that cannot be logged into, that is not present on billing reports nor is it a paid seat. This was introduced to facilitate machine-to-machine API connections while avoiding the complications of billing and access. Administrators can create Service Account users for companies in order to utilize them for setting API keys for various integrations and other API-related items.

A new Auth Type for webhooks

• We introduced a new authentication type for webhooks called "HMAC". HMAC or hash-based message authentication code is a set of headers that are added to a webhook to secure it in transit from an origin to a destination system (IETF RFC 2104) HMAC protocols are used by leading organizations such as Github, Microsoft, etc to sign webhooks to ensure authenticity in transmission. More details can be found here and here.

API Key Management Page

• We introduced a new API Key Management page to be implemented to maintain the User data for which credentials are issued. Using this API Key Management page, User credentials can be generated from the user list shown. The current Create API Key section will be modified to add a selection for “Credential Type”. This will contain two options: “User Credentials” or “Service Account Credentials”.

Updated Data Validation for Debts Table

Previously, Forth stored account numbers and other similar account numbers as encrypted values in the database. For the Managed Data Cloud (MDC) views, we attempt to decrypt them and show the values as displayed in the interface. We experienced problems decrypting, causing errors. This modification adds input validation so that clients cannot enter invalid information for that field to prevent future issues.

Modified RAM Integration with a New "Voided" status

Previously, we performed transaction status synchronization with the RAM integration for “REFUND”, ”RETURN” and “POSTED”. This update adds a new transaction status for “VOIDED” similar to “REFUND” on the Forth CRM side.

Add Conditions to Prevent Debt Deletion on Data Source

Currently, there is no check that the client is not enrolled and the debt is not settled. To improve the integrity and safety of your data, we implemented conditions to prevent the deletion of settled debt.

This modification prevents the deletion of debt via Data Source Update if a debt is still settled. "&delete_debts=1" is a valid parameter to pass to the data source upon updating a contact record. This will now be used to delete and replace debts.

De-Duplication Enhancement for Enrolled and/or Not Enrolled (CRM-I-818)

This modification created an option for the existing De-Duplication (Dedupe) feature to have the ability to select whether to look at enrolled or not enrolled contacts. This modification added a new dropdown selection in the data source setup page for “De-Dupe Type” These options are now "All Contacts", "Enrolled" and "Not Enrolled".

The benefit of this modification is expanding the functionality of our data sources tool to allow for more control over how duplicate records are managed in the system.

API Updates

Added Debt Updates Logging via API (CRM-I-793)

This modification was instituted so that debts that have been added or modified via the API reflect in the client’s history. The History event user will be listed as the user that the API token is associated with in that company. In addition, the History event will read exactly the same as if a user manually updates or adds debt information.

To access other monthly release notes, click Here.