The process of implementing auditing starts with application development. Whether you have an existing application, a new application, or have not yet implemented your own auditing solution, it all starts in the same place. How effective and valuable your application auditing will be at the production site lies in balancing application changes and functionality.
As an application developer, you must do certain things to audit-enable your OpenEdge application. Specifically, you must:
Document your applications tables and fields so that audit policies can be generated at the production site
Document the application-defined events that are coded within your application so that they can be configured at the production site
Supply an application event definition file for all of the application-defined events used within your application so that those events are registered and can be enabled at the production site
Write ABL and SQL report queries for the tables, fields, and application events contained within your application
Document your applications tables and fields so that audit policies can be generated at the production site
