Forum Discussion
What specifically do you need to audit? Are you trying to track individual field changes or just that a record was updated? Pipelines works much the same way as Automations, slightly different syntax.
For example if you have a Project Status Field that you want to audit changes to, you can use as an example {{a.project_status}} and {{a.$prev.project_status}} and you could create a log entry in a table that shows the new and old status along with who changed it and when.
Unfortunately Audit Logs given how far and wide they could/would be used if they were a standard feature make them something you'll have to handle on a case by case basis. I do various audit logs where I do the above and set conditions to see first if each field changes between its current and previous value, and it they're different I create an audit entry logging the old and new, who changed it, and when they changed it.
------------------------------
Chayce Duncan
------------------------------
- mragans1 month agoQrew Member
Any chance you could share some instructions on this? "I do various audit logs where I do the above and set conditions to see first if each field changes between its current and previous value, and it they're different I create an audit entry logging the old and new, who changed it, and when they changed it."
- Denin1 month agoQrew Captain
See this video (start at 18 minutes):
Recreating Automation Use Cases in Pipelines
Walks you through using Pipelines to create an audit log, and having specific triggers. Comparing field values could be a matter of adding some filter logic in the Pipeline.