We are building application in Ignition Perspective 8.1 for Pharm Industry.
One of the regulation demands is Audit trail with current value, previous value and reason of change.
Another demand is to have user access log. User access log will log the user log in/out activity, invalid passwords and etc.
How can it be done?
If you have something prepared module for this this demand?
One starting point would be evaluating our Audit Log and Profiles functionality…
I’m interested in this too, I’m using the Audit Log but I wonder how to manage the previous value.
Any help about this?
Previous value is currently not recorded which is a major issue for these types of industries, and just a pain for other industries. I have a feature request for this here which would be super simple to add:
There’s really no workaround for this at the moment that I would consider bullet-proof if you’re using bi-directionally bound numeric display components. You could technically create your own View template and not use bi-directional bindings, which would handle the writing of the value as well as inserting of the audit log record, but in this case you would end of with 2 records in the audit log, one with previous value and one without
“Reason of change” would be far more difficult to add generically, and would mostly likely need to be done by the integrator to implement that functionality.
Yes, this is a big issue because now what I do is enable history for the setpoint tags (thousands) so I can show in the chart the previous values and how they have been changed. Obviously this is a waste of space of database and a lot of work for a simple things that could be done automaticly in the audit events.
You’re almost right (custom view/template) except that you can update a field. That’s what I was pointing in this doc:
A common example of extending the Ignition audit trail is recording when a user has changed the value of a setpoint from an HMI. For this action, a text input component would be configured within a template. Using event handlers on this component, a script is utilized to detect when the value of the text field is changed. When the value is changed, a query is executed to insert an entry into the audit database table. All fields can be filled in to match built-in audit events, including the current user, current host name, and timestamp. In this example, the “action” field can be populated as “setpoint change”, and the “value” field can be populated with the old and new values for the setpoint. With this configuration completed inside a template, it can be reused throughout the project without extra configuration or testing.
See § audit trail: 21 CFR Part 11 Compliance with Inductive Automation’s Ignition Platform | Inductive Automation
But I’m sure that IA will fulfill this request. Maybe something for the ideas.inductiveautomaiton.com portal…