New features
UI: On-demand Configurations Push (1301394)
In the 2024.04 release of DA in July 2024, we had added the capability for an on-demand method to push Determination configurations to DA. At that time, the UI was very basic. We enhanced this UI under the Enterprise Cloud Determination UI,
Help
menu, then About Determination Anywhere, which everyone can access.
An enhanced dashboard of each, or all, of your DA client deployment instances.
version of the DA app along with updated date-time.
version of the tax content along with updated date-time.
configurations updated date-time.
Sync all configurations
– Select this button to perform a full configuration data push to the DA clients in case there is a need to replace all that data.
This function is only for administrative users, that is users assigned to any of the 2 user roles in Determination – DA Support User and/or DA Tenant Admin
Review changes then sync
– Select this button to review configuration changes you've made for some time, and have queued up, until the last configuration sync to the DA client instances.
This function is allowed for Determination users who have the user role of Power User.
This page provides a high-level display of the different configurations changed up to that point.
If the changes are acceptable to the user to be pushed to DA, then they can submit them.
For the 2 buttons preceding, the DA client instances will pull the data based on the schedule that is configured for them.
The ability to do an ad hoc push of configurations to DA is an optional function that needs to be enabled for your tenant on Determination. By default, this is not enabled in which case each configuration change made will readily sync to DA, without letting you review them. The DA client instances will still pull the data based on the schedule that is configured for them.
Transaction Reversal Captured in NGRA Report (1353258)
DA started supporting reversal of transactions (refund/return of an original invoice) as part of the 2024.04 release. You can find details of the transaction reversal in the
Help section. One open item with the DA reversal thought was, when the original related transaction can't be identified, the newly send reversal transaction was going into a failed queue not appearing in our NGRA reports (this was highlighted in release 2024.06 under the section ‘Recording of Failed Invoices to Datadog (1284558)’).
With this release, if the original invoice is not found, we would add a dummy entry in the audit database invoice table with the reversal information. This reversal will then be reflected asynchronously in the reporting database which the customer can validate in reports.
The preceding steps are now the same as the process that the Enterprise Cloud application follows for a transaction reversal. In both cases, to validate an explicit reversal transaction in the report, a customer can create a custom report, add the “Reversal” column to the template, and get a filtered database by selecting Reversal = “Y”.
DA Hub: Telemetry Capture of Logs (1340161)
The DA Hub was introduced in release 2024.05. With this current release, if DA Hub is an additional component used for a customer’s DA setup, we can capture the following logs for a specific Hub:
Hub transaction data – transaction data that hits the Hub from a DA tax engine client.
Hub tenant data – details related to the sync of configuration data via Hub, such as was it successful, or when was it last synced.
Hub content data - details related to the sync of tax content data via Hub, such as was it successful, or when was it last synced.
Capturing these details will help us troubleshoot any issues. In addition, a plan to enhance the DA Dashboard can include these details from the Hub as well.
Datadog Dashboard & Monitors (1340155)
Dashboards and monitors are now built within TRs internal application Performance Monitoring (APM) tool, Datadog, to understand areas of concern better:
Failed Invoices – DA transactions syncing to the TR audit database could fail for various reasons. These transactions are captured in a database table separately as mentioned in the 2024.06 release note (‘Recording of Failed Invoices to Datadog (1284558)’). However, they had to be manually monitored and filtered to get to the required information. With this release, these errors are now being captured in Datadog, to display the count of invoice objects that are failing and stored in failed sync invoices queue, and create alerts for the TR users to understand if this number hits a predefined threshold.
Delay in audit invoice processing – DA transactions syncing to the TR audit database may not get processed on time, and they may remain in the transaction sync bucket for a long time. With the current release, the Datadog dashboard would display the number of pending invoices in the transaction sync bucket. This helps the TR teams to monitor for invoices that are in the bucket for long and take corrective actions as necessary.
DA Client: Error Logging Improvements (1340162)
To make the troubleshooting process simpler, optimizations have been made in the way error logs are captured from the DA tax engine instances. Only valid errors are now captured as errors, while the others are captured as warnings.
DA App Image Includes Latest Tax Content (1409806)
The DA application images, required to install the application at the client side, would include tax content within it. This way, the entire set of tax content doesn’t need to be synced to the DA instances after app install. However, the version of the tax content would be a bit outdated depending on when the DA app version is released. This caused several hours, in some cases, to be spent on updating the content.
With this release, the DA app image will be regularly updated with the latest tax content being released. So, if the customer is taking the app version released in November 2024 (2024.06), in Jan 2025, the image would contain the latest tax content version released in January. This is achieved by implementing a workflow that checks for updated tax content versions and release a new DA app image whenever new content is released.
The new app image still adheres to the main release cycle app version. So, in the preceding example, the DA app image would still be labeled as 2024.06 but with other labels that identify it as an updated version.