The release notes for May 2023 are organized as follows:
- What’s New (1)
- API Updates (3)
2023-05 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".
We added CheckFlo functionality by creating a new user interface (UI) to integrate with CheckFlo API endpoints which now allows the upload of check payments to their platform from the Forth Pay CRM.
API Contact Search by Field Endpoint (CTX-I-187)
The existing search endpoint allowed searching for contacts in the database based on a specific type (Enrolled, Settlement, All) and a term that matches any searchable field in the UI. This update enhanced the search functionality by providing the option to search by a specific field. This was achieved by improving the existing API contact search endpoint by adding a new parameter named "field" in addition to the existing "type" and "term" parameters. For more information, click Here.
Contact Stage and Status API (CRM-I-564)
This update allows clients to retrieve a Contact's Stage and Status values and to update that Stage and Status via the API to improve reporting and business workflows.
This update utilizes the specific ID for each Contact Stage and Status in a particular account, which will be passed as integer values for the "stage" and "status" parameters. Also, a new Contact GET endpoint will be created and added to the existing API documentation to retrieve all available Contact Stage and Status values. For more information, click Here, and Here.
Update to the "Update Debt Record by ID" API Endpoint (CRM-I-949)
This update now allows users to update the charge-off date (i.e., when a creditor wrote off a debt) in the format of YYYY-MM-DD when updating a debt record. This allows users to keep accurate records through the "Update Debt Record by ID" API endpoint.
If a valid charge-off date is provided, the API will update the charge-off date for the creditor associated with the specified debt ID.
If the debt ID does not exist, the API returns a 404 not found error response. If the API can not update the charge-off date due to system errors, it issues a 500 internal server error response.For more information, click Here.