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

Added the Partially Delivered status when setting up communication triggers in actions.

New

Interest calculation will now support custom interest calculation days.

The system now supports customizable interest calculations through System Generation Flag 73, which allows you to define the number of days used in interest calculations. Instead of the standard 360 or 365, you can now specify any value greater than 1 including decimals (e.g., 365.5 or 366).

Changed

Processing scheduled actions on consumers with no active accounts no longer forces an error in the Action Queue.

Action triggers from the Consumer Portal may schedule actions on consumers with all inactive accounts. Previously these actions would get an error and would have to be taken care of manually.The logic to select the main driving account for scheduled actions that did not have a main driving account specified has changed. Before this change an active account with the highest balance was selected as the main driving account if no account was specified at the time the scheduled action was created.Now if there is no driving account selected and no active accounts on the consumer, the main driving account selected is the account with the most recent date of last activity. The date of last activity is the most recent date between the date of referral and the date of last payment.

Changed

Fixes an issue in the PDC tab that prevented payment reversals when the reversal did not occur on the due date.

Fixed

Fixed an issue with communication triggers to support multiple status-based triggers for outbound message templates.

Fixed

QwikClient can now enter a consumer email address during account placement.

Changed

Fixed an issue where the help file was missing from viscept client manager.

Fixed

Fixed an issue that was preventing multi-select copy from working on history comments.

Fixed