We Need Auditor NOW! How Long Will It Take Us to Install and Set It Up?

Written By Pam Rasmussen,
Technical Support at Rockton Software

As the primary support person at Rockton Software (http://www.rocktonsoftware.com), I often get asked how long it takes to set up Auditor. The installation of Auditor happens fairly quickly—a matter of minutes for each server or workstation where you are installing it. The part that takes a bit longer is the pre-planning of what you want to track. To help expedite this process, it is helpful to have a good understanding of the different types of audits available.

There are three types of audits in Auditor by Rockton Software, here is a description of each:

Window Field Audit:
Using a wizard, this setup provides a simple way for the non-technical person to setup fields to audit with or without notes at the window level. An audit at the window level will track any change made to a window, not necessarily the database. For instance, it will track changes to a window field after the user tabs off of it, before the Save button is clicked.

Table Audit:
At the table level, table fields that are set up to be audited are tracked when a data change occurs within Dynamics GP application, regardless of the window in which the change was made. A typical scenario would be on a maintenance window after the Save Button is clicked. Once this table save occurs, the audit is triggered and those changes are tracked.

SQL Audit:
The SQL audit level requires a thorough understanding of how SQL tables are setup and used. This type of auditing allows audits to be tracked in Microsoft Dynamics GP as well as other applications. The audits are tracked once the changes are made to the SQL database. NOTE: With SQL audits the user will not have the option to track the “Why” (reason code/note) a change took place. Auditor will capture this change at the point when the data in the database has been changed. SQL audits place triggers on the database and capture when the data is being changed regardless of who changed it.

Once you determine the type of audit(s) you would like to set up, it is just a matter of deciding if you want to use a specific method or grouping to create your Audit Groups (i.e., Accounting, Financial, HR, etc.), and which forms, tables, and fields you want to audit.

You can also decide if the User is required to enter a note when they make a change on a field. With a note required, you will not only know who made the change, but why they made it. You can also assign an E-Signature to a field so that when it is changed, an approval is required before that change is saved. These are both great features to use when you have payroll changes, name changes, and anywhere else where you want to know why a change is made or not allow a change until it has been approved by your predefined approvers.

Knowing what you want to audit and how, is key!

Watch an Auditor Demo to learn more!