Fixed an issue where consent wasn't being properly updated as "revoked" when a consumer opts out from a QwikFlow Text Message.

Fixed

Fixed an issue when saving an advanced query with the type system query.

Fixed

Fixed an issue with the Communication Vendor Export system query to no longer have a WHERE condition for an account number greater than or equal to zero.

Fixed

Fixed an issue when using the Employee Logout option in the STING did not properly close the session.

Fixed

Fixed an issue where the file name was empty when sending a delimited file from a scheduled query to a Remote Client Vault.

Previously when saving a file to a Remote Client Vault with a scheduled query, it was not using the provided file name.This has been resolved and the entered file name is being honored.

Fixed

Fixed an error when saving contact preferences for the first time on a consumer.

Previously, duplicate contact preference records may have been entered. This is now resolved to ensure a single record is created.

Fixed

Added the ability to reset consent and also preserve consent when using the Update Consent action event in actions.

We are adding the ability to reset consent in the event it is granted/revoked when it should not have been. This will all be done by utilizing the Update Consent action node in either schedule queries or from the action line. This feature is to be used with extreme caution.

Update Consent Actions

Preserve Revoked and Opted-Out

The Update Consent action event now has a new property to prevent consumers with existing Revoked or Opted-Out consent to be preserved and not overwritten. The Preserve Revoked And Opted-Out flag on the action event can be set to True so that any existing consent that is already set as Revoked or Opted-Out will not be changed.

Reset Consent to Not Set

Also with the Update Consent action event you can reset consent back to Not Set. A new drop down value is available for each of the different communication methods, phone calls, text messaging, and sending email.



Consent Screen

The Consent Screen has been updated to show None if no consent has been gathered for a consumer. If you reset a consumer’s consent using the Update Consent action event, this will show as Not Set. Also when viewing consent history if you reset consent to Not Set, you will see that change.

New

Added System Queries that will allow for specialized queries that are created and can be configured to fit customer needs.

DAKCS is rolling out a new category of queries known as System Queries. These queries are specially crafted by DAKCS and come with predetermined order and formatting.

The purpose behind System Queries is to facilitate the use of DAKCS's upcoming Vendor Integration tool. By implementing these queries, DAKCS aims to streamline collaboration with vendors and offer a foundational structure for interactions with these vendors.

Although these queries come with a set structure, users have the liberty to add fields to the end of the list, according to their needs, and do a save-as with the modifications for their use. This customization option ensures that users can adapt their data files for vendor communications, tailoring the information sent as necessary. However, any changes made will necessitate coordination with the vendor regarding the data layout requirements.

New

Fixed an issue with the Request Document Signature action event where it could show duplicate Flow Documents to choose from.

Fixed

Fixed an issue with Action Queue Maintenance not updating its status icon in the tab.

Fixed

Fixed an issue with Action Queue Maintenance where a permissions error would show when it shouldn't.

Fixed

Fixed an issue with Report Designer where it would crash when you cancel pulling the data for the report.

Fixed

DAKCS Communication Service

DAKCS Communication Service is now available to sign up for and start using. To use the service Beyond 3.1.1 is required and you also will need to obtain access to the DAKCS Hub. In the following notes, we will introduce you to the new features available within the DAKCS Communication Service. 

DAKCS Communication Service is a new and modern application that allows customers to communicate with consumers via email and SMS text. Communications are currently limited to predefined templates created in the DAKCS Hub and initiated by actions in Beyond. 

DAKCS HUB

Once logged into the DAKCS Hub, there will be some new menu options available for you to choose from. There will be a Communication group with Templates, and under Reports, you will see Communication History and Text Message Responses.



Templates

Once Templates is selected you will then have the ability to add a template using the  ADD TEMPLATE button. You will then have the option to select email or text.



Text Template

Selecting the Text Template will take you to the setup screen which will show a sample cell phone with a message and footer option. 



There is also a section on the right that has the template name, and section Fill Points that will embed data from the account in Beyond into the text message.



Once the template is saved you will then be presented with what the text message will look like to the consumer.



Email Template

When selecting to set up an email template you will be shown a sample email template with a subject line, body, and footer.



Similar to the text template you will have a selection of Fill Points that can be used to embed Beyond data. 



There is also an additional feature available in the email template that allows for Validation Information to be sent as an email. You will also be able to flag an email template as a Validation Notice which updates Beyond with the same logic as a mailed Validation Notice.



Reports

There are currently 2 reports available in the DAKCS HUB for data about the DAKCS Communication Service. We have provided a Communication History report and a Text Message Responses report. These reports are just a few quick reports that you can use, as well as being able to create reports inside of Beyond. 



The Communication History report will allow you to see all outgoing communications that you have sent to consumers. You will have the opportunity to filter and export the report with data that you may want to see. Such as a report of what emails you have sent and the statuses of those messages.



The Text Message Response report allows you to pull all incoming text messages that a consumer has sent you your designated 10 DLC. 



Beyond

In Beyond you will be able to send communications via actions, set up action triggers, and view Communication History. 

Communication History

When an account is pulled up there is a new option in the History screen. CH, Communication History, located to the left of TH. This will allow a user to view all communications sent from the DAKCS Communications Service. This data is all quarriable by using the COMMUNICATIONHISTORY@ table, which makes creating a report easy. 



Users will have the ability to either right-click, view detail, or double-click an individual communication and view the exact message that was sent to a consumer or what the consumer's text response was. This will provide essential audit information for scenarios where the template may be changed over time.



Actions

Inside Action Designer, there is a new Send Communication Message Node. The Decision node has also been updated to allow you to make decisions based on the Communication History fields.

Send Communication Message

This action node will allow you to send the templates by either the action line or by scheduled queries. Just like many other action nodes you can allow for a collector to have a user interface where they can select what template to send or set the action to send a specific template. 



Decision Node

We have expanded the Decision node to allow you to make decisions on data that is stored in Beyond for the Communication History. You can select the table and field you want the system to look at, and then select the constant value which will provide a list of available items such as Status’.



Action Triggers

There is a new Communication trigger available, that will allow you to set up action triggers based on certain events that happen with emails and text messages. You can trigger off whether the message was outbound or inbound. 

If the message was outbound you will have the option to select a specific template that was sent, as you may want to run a different action on the different messages being sent to consumers.

New

Added the ability to update the social security number to a new value from the return data from IDI reports.

To enable this feature from the main menu go to Reports & Analysis → DAKCSNet Statistics/Reports → DAKCSNet Utilities. In the Update Setup tab be sure to choose the Interactive Data drop down option. If you want to enable the social security number to be udpated from IDI reports, you can select Update the SSN option in each of the following:

• Deceased Setup



• Bankruptcy Setup



• Credit Header Setup

New

Fixed an issue when resubmitting a signature request on a credit card or ACH payment showing as an error when it shouldn't be.

Fixed

Added TLS 1.3 support to Beyond and Beyond applications.

• To use TLS 1.3, your workstations must be running Windows 11 or Windows Server 2022.

New

Fixed an issue where accounts with a date of service after the bankruptcy filing date were incorrectly being updated from BANKO results.

Fixed

Fixed an issue where switching users onto another database in Beyond would not properly clear a lock on a debtor if one was locked while the switch was performed.

Fixed

Added an option for masked account number and masked master number when selecting a system variable within flow documents.

New

Changed the QwikFlow document editor to allow formatting of an embedded field.

The new flow document field formatting option is used by navigating to the flow document screen.

Main Menu -> System Administration -> QwikFlow -> Flow Documents

From the Flow Documents screen, either select an existing flow document and click the “Edit" button or click “Add" to create new flow document. This will bring up the edit window. Navigate to the tab labeled “Email" in this window.



Click the “Edit" button beside either the “Email Body" or “Email Footer" selection to open the document editor screen. In this window, click the “Insert Field" button near the bottom left to open the Insert Field window.





The new formatting option is shown at the bottom of the Insert Field window. To use formatting, you must first select a table and a field for the data you want to insert and then check the checkbox “Add Formatting". Once checked, the format dropdown will allow a format to be selected . The available format options are not configurable at this time; only the listed format(s) are available to be used.

Once a format has been selected, press “Ok" to insert the data into the flow document. When the document is sent in an email as part of a QwikFlow, the embedded data will be shown in the chosen format.

Changed

Changed Screen Designer to display the "last modified date" and "last modified by" columns when opening an existing screen.

Changed

Fixed an issue with QwikFlow where, if an email was sent by the QwikFlow that bounced and the flow was setup to send a sting letter in the fallback logic, the letter code 000 would be requested instead of the correct sting letter.

Fixed

Fixed an issue where not all comaker records were being purged for a master during a purge.

Fixed