Audit Entity Changes (both for the master entity and for detail entities)

By lef on 14 May 2010
Tracing data updates requires some custom patterns. It should be simpler to trace end user operations to support security audits.
Ricardo Casaca19 May 2010
Something like a right click on the Entity -> Audit Entity, and a additional entity would be automatically added as a subnode.

Entities
 - Customer 
      - Fields
              - ID
              - Name
              - ....
      -Audit (Entity)

Laurentiu LAZAR18 Jan 2011
An "framework" for recording sensitive operations: edit, delete. When and who do it.

Merged from 'Audit Trails' (idea created on 2011-01-18 15:21:30 by Laurentiu LAZAR), on 2015-09-03 09:55:38 by Engineering Team
Mazen Moussa11 Apr 2013
Excellent Idea !! This is important to have

Merged from 'Audit Trails' (idea created on 2011-01-18 15:21:30 by Laurentiu LAZAR), on 2015-09-03 09:55:38 by Engineering Team
José Antunes3 May 2013
This would simplify a whole bunch of code, just like the multi-tenant implementation on OS 7+

Nice one!

Merged from 'Audit Trails' (idea created on 2011-01-18 15:21:30 by Laurentiu LAZAR), on 2015-09-03 09:55:38 by Engineering Team
Ricardo Camacho18 Aug 2010
Instead of the current system of audit actions that you can embed on your code, why not have the concept of audit built-in to the components (actions, queries and whatnot), defined by properties (IsActive, Label, etc...) and controlled by an eSpace global setting (AuditMode).

This way during development you can easily audit your entire application without having to change the processes within the eSpace for debugging only.

It could also be configured to generate a streamlined log file for the application.

Merged from 'Built-In Audit Capability' (idea created on 2010-08-18 11:07:03 by Ricardo Camacho), on 2015-09-03 09:56:09 by Engineering Team