ScottPugh
7 years agoQrew Cadet
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 wants to add a new 'product' record to the products table. The user populates all fields and clicks 'Save' instead of actually committing this record to the products table I would first like another user (the approver) to either approve or reject the record. If approved the record gets committed, if the approver rejects a record they should be able to add a comment as to why its rejected (thus maintaining a record of the rejection with comment).
Similar capability must be available if a user attempts to edit an existing record. For example, user tries to change the color field in a product record. Before the change is made an approver must approve or reject the change (similar flow to above)
Thanks for the help.
example process:
A user wants to add a new 'product' record to the products table. The user populates all fields and clicks 'Save' instead of actually committing this record to the products table I would first like another user (the approver) to either approve or reject the record. If approved the record gets committed, if the approver rejects a record they should be able to add a comment as to why its rejected (thus maintaining a record of the rejection with comment).
Similar capability must be available if a user attempts to edit an existing record. For example, user tries to change the color field in a product record. Before the change is made an approver must approve or reject the change (similar flow to above)
Thanks for the help.