Added a new expression in Action Designer for getting the current day of the week.

We have added a new Expression in Action Designer “Current Day of the Week”. This expression works similar to the other current date expression. This new expressions returns the current day of the week fully written out.

• I.E. If the current date was 9/3/2025 the expression would output “Wednesday”.

This expression also has a Days parameter similar to the other current date expression. This lets you offset the current day by adding days or subtracting days.

• I.E. if the current date was 9/3/2025 and the Days parameter was set to “3”, it would output the value for 3 days in the future (9/6/2025) which would output “Saturday”.
• I.E. If the the current date was 9/3/2025 and Days was set to “-1”, it would output the value “Tuesday” (9/2/2025)

New

Added a new action node in Beyond for sending the DAKCS Validation Notice as an email through DCS.

DAKCS Validation Notice

DAKCS has created a new action node in Beyond that allows sending a Validation Notice through DCS as an email.

Validation Notice Action Node

A new Validation Notice action node has been added in Beyond. The new node can be found in the “Communication” tab in the Action designer toolbox. Unlike the other communication nodes, this new node has no needed configuration and does not need any communication template to be selected. Instead, DAKCS has created a core validation notice template that the node uses. An example of what this notice looks like can be found in the Email Validation Notice section of these release notes.

DAKCS Validation Notice Communication Trigger

A new entry in the Template dropdown is available for creating triggers for the validation notice. The new option is called DAKCS Validation Notice template supports all the same features for Communication Triggers as other outbound communication triggers.

Email Validation Notice

A new core DAKCS Validation Notice email template has been created. An example of what the new email template looks like when sent to a consumer is shown below. Note: This is a core template created by DAKCS. The DAKCS Validation Notice template cannot be modified or customized at this time. Note: The example above was viewed within Gmail inside of Google Chrome. Emails can be viewed in many different email clients and different viewers may cause slight visual differences depending on the email client and device used to view the email.

Validation Notice Buttons

At the bottom of the DAKCS Validation Notice email we have added four interactable buttons with the following functions:

• Dispute Buttons - All three dispute buttons open a new email with the To address and subject lines pre populated for their respective dispute reason.
• Send Original Creditor Button - similar to disputes, this button opens a new email with the To and subject line pre populated to request the original creditor information.
• Make a Payment Button - Opens a new browser tab and navigates to the Consumer Portal, automatically logs the consumer in. Once logged in the consumer can make a payment or perform any action they normally would when logged into the Consumer Portal.

Note: The Make a Payment button use a Magic Link to let the consumer log in without any extra steps. Like other Magic Links sent by DCS, this link remains active for one week. After it expires the link, when the link in the email is clicked the consumer will be taken to the regular sign in page of the Consumer Portal and must log in normally.

DAKCS Hub Space Contact Information

We have added some new fields to the Contact Information section of a space on the DAKCS Hub. The new fields are

• Email
• Address Line 1
• Address Line 2
• City
• State
• Postal Code

These fields are populated on the DAKCS Validation Notice and should be populated with the desired address information you want consumers to see when they receive an DAKCS Validation Notice email. Note: Address Line 2 is an optional field but all the others are required to be populated out when saving contact information.

New

Fixed an issue in Action Designer with the decision node when building a condition with a constant value would not allow typing a value manually in the dropdown.

Fixed

Added permissions for users to create suits

Admins can now set permissions that determine whether users are allowed to create suits. MAIN MENU → SYSTEM ADMINISTRATION → USER SETUP → Command Box → S - Suit → Add New Suit The Add New Suit permission will be granted to the PUBLIC Role by default.

New

Fixed an issue where Client Letters were stuck in a waiting status.

Fixed

Fixed an issue where Report Designer would infinite loop instead of displaying an error message.

Fixed

Fixed an issue where MMS messages were being counted as emails instead of text messages.

Fixed

Fixed an issue with MMS where attempting to send documents containing blank pages would cause the action to fail.

Fixed

Added a new action node in Action Designer that allows updating values in user defined tables (U_tables).

Update U_Table Action Node

We have added a new action node within Action Designer. This new node “Update U_Table” allows you to update the value of an account-linked or debtor-linked U_table by running an action. This allows updating U_Tables from the action line, scheduled actions, and action triggers.

---

The new action node can be found in the “Action Event” section of action designer. The action has these options that you can configure:

• Input Value - this is an optional input that lets you enter a hard-coded value you want to update the field to.
• Input Variable - this lets you pick from a list of Expressions created within the action.
  • The screenshots show an example of creating a “Current Date” expression and using that as the Input Variable.
• U_Table and Column - this allows you to pick the table and column that will be updated by the action.

Note: The Input Variable option takes priority over Input Value.

• If you populate both, the data from Input Variable will always override the hard-coded Input Value.

---

The other options in the Update U_table action are similar to other action nodes and work as you are already familiar with:

• Add to Collector Time Usage (True/False) - Whether you want this action to be added to collector time usage
• EventCode - A unique event code to identify the action node. This cannot be changed.

---

New Expressions

To go along with the Update U_table Action Node, we have also added three new Expressions to Action Designer

• Current Date
• Current DateTime
• Current Time

Similar to the other expressions, these new ones all calculate the current value at the time the action runs and do not rely on any hard-coded values.

---

Additional Notes:

• The Update U_Tables action can only be used with account-linked or debtor-linked tables.
• The Update U_Tables action can only update a single column in a single U_table at once. If you wish to update multiple columns and/or tables within a single action, you can do so by using multiple Update U_Tables Action Nodes.

New

Fixed an issue with processing scheduled credit cards.

In some cases, when the overnight process could not connect to the credit card processor, the PDC payments would get completed and marked as DENIED. In this case the PDC payments will not be completed and will be properly processed the next time the overnight process runs.

Fixed

Fixed an issue where, if two consent records were created at identical times, Beyond would always pull the first of the two when grabbing consent.

Fixed

Fixed an issue where launching a second Beyond session would interfere with print beyond letters.

Fixed

Fixed an issue where communication history was not properly linking or purging.

Fixed