2
 Followers
35
 Likes

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

Backend
On our radar
Tracing data updates requires some custom patterns. It should be simpler to trace end user operations to support security audits.
Created on 14 May 2010
Comments (7)
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)

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
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
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
Merged this idea with 'Built-In Audit Capability' (created on 2010-08-18 11:07:03 by Ricardo Camacho)
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

Audit requirements on a number of projects I have been involved in result in lots of boilerplate code.

It also makes it slow to implement the data layer.

Whereas nowadays it is quick and easy to build auditing in C#.NET development using EntityFramework or NHibernate with additional plugins, that then works for all entities requiring auditing.

So on larger projects, OutSystems becomes less of an attractive option.

I like Richard Casaca's idea of an additional audit entity appearing when selecting to audit an entity.

I think auditing for child entities associated with parent entities would be difficult to implement, as it is not possible to determine if the entity is truly a child entity or just referencing another entity.  However, separate standalone audit tables for the child entities might suffice.


views
487
Followers
2