The actual information that can be recorded by the various types of auditing context differs. In all cases except the database transaction context, the application developer is in control of certain information fields; OpenEdge controls the remainder.

The application context and audit event group require an event-context field of character information that also serves as an index to locate certain types of contexts for reporting. Optionally, two additional fields of character information, up to a maximum of 10,000 bytes per field, can be supplied. Each time an application context or audit event group context is begun, a single auditing event record is written to the OpenEdge databases _aud-audit-data table. The application-supplied information is placed into the record with OpenEdge filling in the remaining user, date, context, and UUID (the unique identifier assigned to an OpenEdge database when the database is created) primary index information automatically.

The client session context takes its information from the client-principal objects attributes and creates a record in the _client-session table within an OpenEdge database. The extended user login information is not always necessary for auditing, so recording this information is optional and controlled through database auditing options.