• Open Audit works great

    By larry j lizzard 2 decades ago

    Dear Chad,



    Thank you very much for creating this Open Audit. We have 20 people who do data entry every day, and we were never able to see on FIELD level who had made mistakes. We could see on DOCUMENT level who was the last editor, but when we tried to train people to improve their entries, until now it wasn't possible to pinpoint the one who made the mistake.



    We have a great developer who knows Java, Lotusscript etc., but he never thought this could be (easily) possible.



    The screenshow is great, the setup instruction could be improved. What I did.



    1) put the template .ntf on your server



    2) create a Open Audit database from that template. I just called it Audit Log (for Db X). Configure the ACL so users can access the database.



    3) copy to the database you want to be audited (Db X):

    • Open Audit Configuration form
    • Admin\Open Audit Config view
    • (Open Audit Config) hidden view
    • Open Audit subform
    • Domino Extended, Open Audit, Open Audit UI Automatic script files



      4) add the Open Audit subform to the Form in your database that you want to be audited



      5) Set the parameters in the Open Audit Configuration form in your Db X so that it knows what to audit and where to write the audits to (in my case to the database Open Audit Log (for Db x).



      That's all!



      Thanks again Chad (and Open NTF people)!

    • Thanks and

      By Chad Schelfhout 2 decades ago

      Thanks for the feed back. The screen show needs to be updated so I will expand on the steps to implement open audit.



      I agree with all of your steps if you are looking for the subform implementation which has some potential holes where a audit will not be created. If you are looking for most reliable implementation then I would recommend "manual" implementation as defined on the Developer Implementation tab of the Using this Database page of the template.