Skip to main content

2022-07 Release Notes

  • Updated

The release notes for July 2022 are organized as follows:

Release Overview

2022-07 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".

 

What's New

Added Ability to Post Credit Report XML File via WebHook (CRM-I-568)

This new feature provides businesses the ability to post raw credit report data outside of the CRM via WebHook and includes a sensitive information disclaimer. A customer may get qualified for multiple products within DPP, yet Forth does not offer the ability to service all products offered. This feature added the ability to post out the credit report XML Data via webhook which prevents the company from having to pull credit in their other CRM after posting over from DPP.

 

Added Document Tag for Verified Debt Date (CRM-I-576)

To supplement the existing {DEBT_VERIFIED_AMOUNT} tag a new tag for {DEBT_VERIFIED_DATE} has been added. These tags populate in emails or documents when the creditor is selected from the dropdown. A need existed for a document tag to list the verified debt date, along with the verified debt amount to send the client an email when a debt is settled.

 

Added Ability to Unlink Debt from a Document, and Document Type Enforcement (CRM-I-596)

This new feature added the ability to unlink a debt from an uploaded document. For example, after uploading a document and choosing a debt to associate the document with, users wanted to unassign the debt that was linked if it was done by mistake instead of doing the workaround of downloading the document and uploading it again. An additional new feature is that when a debt is being edited, the CRM will not allow for the document type to be un-selected. This now prevents the user from saving if a document type is not valid or selected.

 

Added New Document Editing Read Only Setting

We’ve added a new setting to lock document editing to the creator of a document. This can be enabled and controlled at an individual document level. This adds another layer of control for admins to more strictly control updates to specific mission-critical documents.

 

Added Enrollment Plan Inter-Account Sharing

You can now share enrollment plans between CRM accounts via this new feature. After initial setup, a plan can be designated as shared with specific accounts, eg: affiliates. The destination account will see a shared list of plans from all tenants and can use it to apply to enrollments within its account. This feature does require setup, so please contact us if interested.

Once setup, this new feature adds a new section under the Enrollment Plan Settings page. This new section has two controls: a checkbox to enable inter-account plan sharing, and an input box where Account IDs can be entered. Any changes to fees must be made to the plan in the source account. 

 

Added Bi-Weekly and Semi-Monthly Payment Options

We added the ability to assign bi-weekly and semi-monthly payment options to Advances for all our clients' benefit. This change can be made in the "Pricing" section of the Add Advance page, accessed via the Advances tab. This feature must be enabled by software support (via Forth Settings).

 

Added Tags Settlement Offer Fields (CRM-I-610)

This new capability Introduced new tags for a debt that has a settlement offer. Tags render information when a creditor is selected in a dropdown menu or on settlement contextual events (settlement status change for example) that reference a specific debt. These new tags are usable in email templates, document templates, and SMS templates. The specific tags added are:

    • {DEBT_START_DATE} - The date on which the first settlement payment would be due

    • {DEBT_VALID_UNTIL} - Pulls from the “valid until” field when editing a settlement

    • {DEBT_SETTLEMENT_SCHEDULE} - Displays a table of all payments including the payment date, amount of the settlement payment, and settlement payment type (except for SMS templates)

Added Tags for Remaining Debits and Enrolled Debts Not Yet Settled (CRM-I-566)

This new feature added tags that create a table for the remaining leftover debt as per the payment plan and the enrolled creditor which are not yet settled so that the client gets detailed information about the leftover payments and debt not settled.

These new tags named {DEBITS_REMAINING} & {DEBTS_NOT_SETTLED} are now listed in the tags list under E-Marketing template creation and SMS template creation.

 

Added Filter to "Ready to Settle" Report (CRM-I-529)

A new “Additional Filters” option is now present when going to the "Ready to Settle" page in the CRM. Upon clicking the additional filters option, the modal now displays the additional filter items from the debt reports filters. The modal presents them as checkboxes that can be added and removed from the filterable options of the page. New filters that are added pull the correct debts when the filter is applied to the page and a valid input is selected. When new filters are added:

  • They display in the apply filters section of this page.

  • The behavior or format of the filter matches its behavior/format on the debt reports page.

Additional filters pull from filters currently available on the debts report: (https://login.forthcrm.com/index.php?module=creditors&page=reports&report=531

 

Added Tag to Unsubscribe a Client

This new feature added a tag ({UNSUBSCRIBELINK}) that can be used in email templates to unsubscribe clients, like the tag included in emails sent via e-marketing campaigns. This tag generates just the URL, so if you were making a link inside an email, the HTML would look like this:
<a href=“{UNSUBSCRIBELINK}“>Unsubscribe</a>
This could for example be used in Email templates or Trigger Email templates.

 

Added Search under the Emarketing tab to filter templates (CRM-I-506)

This update provides a means to search through the ever-increasing numbers of email templates that an organization submits for delivery in the CRM. It added a search bar that filters the table of templates by "Created By", "Created Date", "Category", "Title", and email subject.

 

What's Improved

Increase String Length of Support Password (CRM-I-623)

To improve our overall security, we implemented this update to extend the internal CRM support password requirement to eight (8) digits to better match with NIST and PCI security standards. 

 

Account Balance Display Update

Within the "Fee Accounts" page, found under the "Accounting Tab"; the most recent amount displayed in the "Balance" column was not matching the "Account Balance" amount, and matched the "Reserve Limit". With this improvement, the Balance column now reflects the amount listed as the Account Balance.

 

Updated to a New Document Generation Engine

This improvement addressed the most commonly or frequently used documents that were hitting an old document generation service and causing inconsistent document formatting. The improvement involved re-saving those documents as new, so that they received a Document ID number higher than 96230, and therefore hit the new document generation system. Finally, the deactivation of the older documents was the last step to prepare for the deprecation of the old document generation system.

 

Remove Transactions Graph from Portal Transactions Page (CRM-I-630)

This improvement removed the entire transactions bar graph section from the portal transactions page, keeping the transaction behavior/content unchanged. It will help alleviate confusion and speed load times within the Customer Portal.

 

Column Visibility on Emarketing and Docs Tab

The “title” column in e-marketing and the “name” column in the Docs tab (packages & templates) truncated long names. It was impacting users because they were not able to see the full text. This improvement modified these columns in the grid to allow these columns to wrap text and not truncate, for better visibility.

 

 

API Updates

Cleaned Up Response Codes in the API

We identified a need to clean up our API response codes. We were returning a 200 code on almost anything even when we have errors. We have a base response that builds all this out, it just incorrectly set the headers. We cleaned this up to make it easier to handle any errors without even reading the body.

 

Completing a Settlement to Use Company Level GCS Credentials

This update consisted of two parts:

1) Updating the GCS API call to set a settlement only upon the offer being completed.

2) Updated the GCS API call to set a settlement and use the company assignment's GCS credentials.

 

To access other monthly release notes, please click Here.

Related articles