We have been evaluating ERPNEXT as a potential deployment to one of our clients. We’re impressed by how feature-full it is and the only thing keeping us from moving forward with it is the lack of an Audit Trail. Looking at a previous thread Document status tracking, I see a mention of how to implement it. Are there more examples(detailed if possible) of a successful implementation of this? What is the consensus of how to implement this feature in 2015?
Thanks
@morrismwaura Thanks for your kind words.
Please be specific by “audit trail”. Also check the submit-cancel workflow for important transactions.
@rmehta By “audit trail” I mean a complete history of all the changes made to a certain field etc. That way I can check what the value was one year ago. This is absolutely crucial for a financial application. A complete audit trail would log/record the following info when data is edited:
Date/time.
User.
Action performed.
old value.
new value.
Regards,
Morris
Hello Morris,
Everytime submitted document is amended, it creates new document, with original document id. Check following link for example.
https://kb.erpnext.com/kb/setup/edit-submitted-document
For example, if original Sales Invoice id was SINV00003. If it is amended twice, it’s id will become SINV-00003-2. The naming of Sales Invoice will indicate that it was amended twice. Also you can go back to cancelled SINV00003 and SINV00003-1 to check the difference with respect to original transaction.
The feature is implemented in Frappe 7.3