I think that there's a better way to do this. If I were setting up the application, I would have a Documents table and a Reviews table. The Document record would hold any specific information, file attachments, Assigned Reviewer, etc. The Review records would be your checklist. Each Review record would represent a single pass in the process. So, in this setup, the process would work like this:
- User creates a Document record and completes the necessary fields, including the Assigned Reviewer, before saving.
- The Assigned Reviewer would see the new Document record on their Dashboard (in a report) and would view the record.
- The Assigned Reviewer would select a button to create a new Review record and complete the checklist as you've outlined.
- The Assigned Reviewer would change the Status on the Document record, indicating it is ready to be Audited
- An Auditor pulls up the Document record and then the completed Review record.
- The Auditor selects a 'Start Audit' button (this would really just be a copy button that's be set to bring over all the original values) and begins their work.
The process would need some tweaking, I'm sure, but this would give you the ability to track 1st review vs the Audit and maintain an accurate history of the process for each Document. This would also allow you to have a single document go back and forth multiple times if necessary.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 /
http://datablender.io/------------------------------
