Failures in DNA batch automation
During the normal course of software development, application integration issues are common and often the cause for project implementation delays. Batch processing in DNA can have inconsistencies after a new release of DNA, System Update (SU), new SQT, etc. Changes to a test, QA, or a production environment can have a negative impact on institution testing and handling of upgrades:
- Batch processing issues in test environments can delay implementation of new releases into production
- As new DNA applications are implemented, IT Operations must ensure they are also implemented in production
- Senior IT Operations personnel are often needed to track and troubleshoot time-consuming (and avoidable) batch scheduling issues
Find differences between Fiserv DNA environments
Proactively manage differences between DNA batch environments
(Click image to enlarge)
Parameters exist:
- in both environments, however they have different default and/or required values
- in one DNA environment but not the other
Applications exist in one DNA environment, but do not the other, i.e. different Application Numbers
SQT Applications exist in one DNA environment, but not the other i.e. different Application Numbers
Benefits – Complement your current batch solution
AccurSee DNA to DNA provides significant benefit to institutions:
- Find differences in your test and QA environments and improve the quality of your production applications
- Learn daily whether changes made to DNA will affect your batch processing in test and production environments
- Eliminate run-time errors, speeding up the DNA development and testing phase
- Reduce the amount of time IT Operations personnel spend troubleshooting DNA job changes