# Perspective Electronic Signature Framework **URL:** \ **Category:** Ignition Exchange\ **Tags:** perspective\ **Created:** [March 2, 2026, 7:12pm UTC](https://forum.inductiveautomation.com/t/perspective-electronic-signature-framework/114272 "2026-03-02T19:12:02Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![jfan](https://avatars.discourse-cdn.com/v4/letter/j/e8c25b/32.png) [@jfan](https://forum.inductiveautomation.com/u/jfan)\ **Post date:** [March 2, 2026, 7:12pm UTC](https://forum.inductiveautomation.com/t/perspective-electronic-signature-framework/114272/1 "2026-03-02T19:12:03Z")
[https://inductiveautomation.com/exchange/2492%3Aoverview?check\_logged\_in=1](https://inductiveautomation.com/exchange/2492%3Aoverview?check_logged_in=1) @Travis.Cox First off, thanks for sharing this Ignition Exchange resource! When I suggested using it for one of our clients, they liked the approach but asked whether there is anything on the backend that can detect manual data updates for audit log events. For example, iFIX has a feature that encrypts the row data into a **MSGID** column. When the message is later decrypted, it can be compared against the row data to determine whether any values were modified after the initial insert. Has anyone used this and done an audit? ---
**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\ **Post date:** [March 9, 2026, 4:53pm UTC](https://forum.inductiveautomation.com/t/perspective-electronic-signature-framework/114272/2 "2026-03-09T16:53:27Z")
Most of the time this is handled in the database by not allowing updates on the table. That would ensure the data cannot be modified. However, it is possible to add a hash or encrypted string in the database that you can compare againt. It is not built-in the audit log, but would be possible to add to a resource like this one. Let me know if you want to dig in further.