Audit Entity Changes (both for the master entity and for detail entities)
1336
Views
16
Comments
On our RadarOn our Radar
Backend
Tracing data updates requires some custom patterns. It should be simpler to trace end user operations to support security audits.
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
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
Merged this idea with 'Built-In Audit Capability' (created on 2010-08-18 11:07:03 by Ricardo Camacho)

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.


Merged this idea with 'Auto History / Audit log table create with each every new entity' (created on 10 Aug 2020 11:34:55 by Meer Imtiyaz)

Hi,

Can it be possible to auto manage history (create/Update action) of each and every created entities. And also has ready only access to that auto history entity.

Now,  we are creating history entity for each and every business entities. So,  this should be auto manage by OutSystems itself.




This comment was:
- originally posted on idea 'Auto History / Audit log table create with each every new entity' (created on 10 Aug 2020 by Meer Imtiyaz)
- merged to idea 'Audit Entity Changes (both for the master entity and for detail entities)' on 16 Aug 2020 00:57:17 by Justin James

+1



This comment was:
- originally posted on idea 'Auto History / Audit log table create with each every new entity' (created on 10 Aug 2020 by Meer Imtiyaz)
- merged to idea 'Audit Entity Changes (both for the master entity and for detail entities)' on 16 Aug 2020 00:57:17 by Justin James

+1 this would be a useful requirement in some enterprise environments that require extensive history/logging for auditing purposes. 



This comment was:
- originally posted on idea 'Auto History / Audit log table create with each every new entity' (created on 10 Aug 2020 by Meer Imtiyaz)
- merged to idea 'Audit Entity Changes (both for the master entity and for detail entities)' on 16 Aug 2020 00:57:17 by Justin James

https://www.outsystems.com/ideas/7622/


https://www.outsystems.com/ideas/5223/



This comment was:
- originally posted on idea 'Auto History / Audit log table create with each every new entity' (created on 10 Aug 2020 by Meer Imtiyaz)
- merged to idea 'Audit Entity Changes (both for the master entity and for detail entities)' on 16 Aug 2020 00:57:17 by Justin James
Merged this idea with 'Field level Auditing' (created on 19 Aug 2020 09:12:19 by Munjal Subodh)
2018-09-17 17-54-14
Munjal Subodh

It would be great if (from a development perspective) there would be a flag per field in every entity where we can just turn or off auditing for that field.

A lot of our competitors have this.

Right now, when we define attributes for an Entity, we have metadata about it like Label, Data Type, Is Mandatory. We can have one more entry in there called "Is Audited".  If that flag is turned on, the system would automatically monitor any changes to that field and log who did it and when.

At the Entity level, we can have "Audit Creation" and "Audit Deletion" flags.

The logging should be intelligent - instead of "changed from 1 to 2", it should do the lookup and say "changed from Red to White".

On the consumption side, there should be an easy way to get the Audit logs per Field/Entity.

For any serious enterprise application, this is a needed functionality that people end up implementing themselves and wasting a lot of time on boilerplate code. Having something like this would increase how fast the applications can be rolled out.


PS I looked at this idea but I am not sure if its the same as what I am proposing:

https://www.outsystems.com/ideas/135/audit-entity-changes-both-for-the-master-entity-and-for-detail-entities?IsFromAdvancedSearch=True



This comment was:
- originally posted on idea 'Field level Auditing' (created on 19 Aug 2020 by Munjal Subodh)
- merged to idea 'Audit Entity Changes (both for the master entity and for detail entities)' on 24 Aug 2020 03:53:42 by Justin James

Great Idea



This comment was:
- originally posted on idea 'Field level Auditing' (created on 19 Aug 2020 by Munjal Subodh)
- merged to idea 'Audit Entity Changes (both for the master entity and for detail entities)' on 24 Aug 2020 03:53:42 by Justin James

Maybe something like this forge comp? Made by @Stuart Harris himself :) which is also in this discussion section


https://www.outsystems.com/forge/component-documentation/11115/objectdiff-o11/0