Added support for to embed text from a Report Designer Document into the "state disclosure" fillpoint.

Report Designer State Disclosures

We have added a new property to Validation Notice and the Send Communication action nodes within Beyond that allows selecting a Report Designer report to populate the State Disclosure template fillpoint. This new property allow more fine-tuning and control over exactly what the state disclosure says based on the communication template or account/consumer information.

---

Both the Validation Notice and Send Communication action nodes now include a new optional property for selecting a State Disclosure. This new property allows you to select any report saved in Report Designer*. When the communication is sent DCS, will copy the text from the Report Designer report and embed it within the State Disclosure fillpoint of the outgoing message. This differs from a traditional DCS document attachment because rather than embedding the report itself as an attachment or message or providing a link to view the document, the text from the state disclosure instead is written directly within the body of the communication. If a communication or Validation notice is sent without a state disclosure report, DCS will use the existing “Communication State Disclosure” as setup on DAKCS Hub. Additionally, if a template does not contain any State Disclosure fillpoints, then the new report will not be added to the communication.

---

Note: A report designer State Disclosures report should contain only text. Images or complex formatting are not supported at this time.

New

Fixed an issue when using a zero-cost payment processor where one-time PDC payments were created with a future due date.

We have fixed an issue when using a zero-cost payment processor when processing one-time PDC payments that were created with a future due date. When the future PDC payment is saved, the technology fee could sometimes be improperly saved as $0.00 rather than the proper amount and when the payment attempted to process the processor would reject the payment due to the incorrect technology fee.

Fixed

Fixed an issue with Flow Documents and Regulation E signature request not updating consent properly.

When a Flow Document request was being sent to an email address and the email message bounced, in some cases consent was not being updated properly. This fix ensures that when an email bounces from a Flow Document or Regulation E Signature request, consent will be properly updated to indicate that the request bounced.

Fixed

Fixed an issue where a credit card payment may attempt to be requested more than once.

When doing the online authorization of a credit card in Beyond, there was a rare chance that the online authorization would be submitted twice. This caused one request to succeed and the second to fail. This issue has been fixed so that the credit card will only be submitted once.

Fixed

Added the ability to skip updating accounts in IDI bankruptcy cases when a dismissed date is provided.

We have added a new flag that can be configured in the Update Setup tab of the DAKCSNet Utilities Screen for IDI. This new setting is to allow bankruptcy “hits” to skip updating the debtor information if the bankruptcy has a dismissed date.

---

• If the flag is enabled, the incoming “hit” will be skipped and no information will be updated on the debtor.
• If the flag is disabled, the “hit” will be processed and update the debtor as normal. This is the previous behavior of a “hit” and has not been changed.

Note: By default this unchecked by default. This will ensure DAKCSNet Reports continue to operate unchanged until you are ready to enable it.

New

Added a new "Run Custom Program" action node in Beyond.

Run Custom Program Action Node

We have created a new Run Custom Program action node in Beyond. This is a new tool in Beyond to allow the DAKCS Customs team to create programs that can run as part of an action. This will allow the DAKCS Customs team to create new kinds of custom programs to be used within Beyond. Please contact the DAKCS Customs team (customs@dakcs.com) for more information about using custom programs with the Run Custom Program action node.

---

Note: Only programs that are specifically made to work with this new action node can be selected in the action node. There may be additional cost to modify existing customs to make them useable with the Run Custom Program node.

---

New

Added the ability for DAKCS Support to configure the order in collector queues build.

Overnight Collector Queue Building - Improvements

Previously, the overnight processes that build collector queues always built the queues in the same company-order. This could introduce a scenario where, if the queues were not finished building by the next morning, the company(s) that happen to run later in that order may not be ready by the time they are needing to be worked.This new configuration allows DAKCS Support to specify the order in which each company on the system has its queues built to ensure the most important company's collector queues are built first and are ready for the morning.Note: This configuration cannot be changed by users within Beyond. Please contact DAKCS Support if you would like to have this configuration changed.

New

Fixed an issue when posting a negative adjustment as an overpayment the amount would be posted to the incorrect field on the account.

Fixed

Fixed an issue where the Consent Screen could sometimes create duplicate consent records.

Fixed

Fixed an issue where client history was not properly setting the collector who requested the client letter.

Fixed

Fixed an issue when running an action with the "History Comment" node where the legal history tab would sometimes not show previous history comments.

Fixed

Fixed an issue where purging would sometimes not remove action history records.

Fixed

Fixed an issue where Flow Document requests would not update properly if the email bounced.

If a Flow Document request was sent to an email address, and that email message bounced, the status of that Flow Document request was never getting set properly in a completed state.Now when an email message bounces, the status value for the Flow Document request is updated to “Rejected”.

Fixed

Changed some logic when a Sonnet dispute is pushed to Beyond where, if the account was in an inactive status code, it would incorrectly update the account jackdate.

Previously when a Sonnet dispute was pushed to Beyond, if the Sonnet configuration was setup to jackdate the account, it would update the jackdate of the account regardless of the status code of the account.This was allowing inactive accounts (PIF, SIF, C-code, and X-code) to have their jackdate updated when the dispute was pushed to Beyond. This would result in inactive accounts having active jackdate despite still being in an inactive status code. We have adjusted this logic so that if a Sonnet dispute is pushed to Beyond it will no longer jackdate the account if it is in an inactive status code.

Fixed

Fixed an issue where ACH payments could encounter an error during authorization.

Fixed

Fixed an issue where the DCS response message box could appear blacked out when OS dark mode was enabled.

Fixed

Fixed an issue where canceling a credit or ACH payment did not properly close.

Fixed

Fixed an issue where creating PDC Payment Schedules would sometimes not the full amount owed on an account could not be scheduled.

Fixed