Forum Discussion
BlakeHarrison
Qrew Captain
Tracy -
Can you explain your use case a bit? I'm trying to understand why you would want to do this because I have to think there's a better way.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
Can you explain your use case a bit? I'm trying to understand why you would want to do this because I have to think there's a better way.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------
TracyHimes
5 years agoQrew Member
We audit documents using a checklist to document results.
Field 1 would be the actual document we are reviewing. We document if it was found=Yes, not found or incomplete=No or simply N/A if not a required document.
Field 2 represents if the validation is complete or not. Yes/No/N/A.
So the user fills out the checklist, sends the results to the assignee. The No responses would need to be addressed. They fix the issue and send the auditors back the results/response.
The reviewer goes back in the QB checklist to update field 2 from "no" to "yes" to show the validation is complete. However, we want Field 1 to remain the original response of "no" so we can track the audit findings.
(Excuse my title of this post)
------------------------------
Tracy Himes
------------------------------
Field 1 would be the actual document we are reviewing. We document if it was found=Yes, not found or incomplete=No or simply N/A if not a required document.
Field 2 represents if the validation is complete or not. Yes/No/N/A.
So the user fills out the checklist, sends the results to the assignee. The No responses would need to be addressed. They fix the issue and send the auditors back the results/response.
The reviewer goes back in the QB checklist to update field 2 from "no" to "yes" to show the validation is complete. However, we want Field 1 to remain the original response of "no" so we can track the audit findings.
(Excuse my title of this post)
------------------------------
Tracy Himes
------------------------------
- BlakeHarrison5 years agoQrew CaptainI 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.
------------------------------
Blake Harrison
bharrison@datablender.io
DataBlender - Quick Base Solution Provider
Atlanta GA
404.800.1702 / http://datablender.io/
------------------------------- TracyHimes5 years agoQrew MemberThank you
I have what I need. I appreciate everyone's help! :)
------------------------------
Tracy Himes
------------------------------