Approval Workflow for Data Changes
I am looking for best practices on how to create an approval process which determines whether proposed changes to data values in a record should be committed or rejected. example process: A user...
Forum Discussion
Here's the outcome I'm trying to achieve:
1. User edits any field on a record, that causes a the 'record status' field on that record to flip to 'Awaiting Approval'
2. Approver reviews the change and then changes the 'record status' field on that record to either approved or unapproved.
The challenge I'm having is any of the methods I have tried for item #1, is then getting triggered again when the approver changes the 'record status' field to either approved or unapproved.
A few things I've tried
1. User edits any field on a record, that causes a the 'record status' field on that record to flip to 'Awaiting Approval'
2. Approver reviews the change and then changes the 'record status' field on that record to either approved or unapproved.
The challenge I'm having is any of the methods I have tried for item #1, is then getting triggered again when the approver changes the 'record status' field to either approved or unapproved.
A few things I've tried
- Quick base actions at the table level don't allow me to edit a record in the same table as the field being changed
- Automation- I can't figure out how to have the field update (record status) occur on the record which had a field changed
- Form Rules- this approach works but then can't figure out how to have the approver updates occur differently. I assume a 2nd form is needed for the approver updates but then its a matter of understanding how do I ensure a user in the approver role only ever sees the 'Approver Form' if that user is also in other roles which are directed to see the 'main' form (which has the form rules to update 'record status' upon save)