Caspio makes it quick to build an approval. A record is submitted, a manager reviews it, a status changes, an email goes out. If you have built a few of these, you know how well it works.
Then someone asks a question the status column cannot answer: which version of the contract did the manager actually approve, and could you show it to an auditor?
What a Caspio app does well
An application on Caspio is very good at the workflow around a document: who submitted it, who needs to approve it, what stage it has reached and who gets told. It is also easy to attach a file to a record, so the file and the record travel together.
Where it gets harder
A file field is designed to hold a file, not to keep a controlled history of one. Depending on how an app is built, the answers to a few simple questions can range from yes, to probably, to we would have to check:
- If someone uploads a corrected version, is the earlier one still there?
- Can you show which version was in place on the day something was approved?
- Is there a trustworthy account of who changed what, and when?
- If a file is replaced or a record is deleted, can you get it back?
None of this is a criticism of Caspio. It is a different job from running the workflow, and it helps to treat it as one.
Keep the workflow in Caspio and put the control in a separate layer
This is how we approach it at After Premise. The approval stays in Caspio, next to your data, where it belongs. The documents go under control alongside it.
With APDocs, you map your Caspio columns once. APDocs adds a few control fields to your table, including a simple yes/no trigger column. Your workflow sets that column at the right stage, for example when a document is approved. APDocs then pulls the document from the attachment field and stores it in secure cloud storage. It writes a controlled link back to the Caspio record, along with a viewer link that shows every revision from inside your application.
Nobody leaves Caspio, and nothing has to be rebuilt.
What that gives you
Every revision is kept. The history is a hash-chained, tamper-evident audit trail, so you can show what was current on any given day and see who changed what. Records and audit history are backed up continuously and can be restored to any point in the last 35 days.
In practice that means no uncontrolled edits, and no panic when an audit or a customer asks you to prove a document was current.
Four questions to ask of any Caspio document process
Which version was approved? Could you show it six months from now? What shows that nobody changed it afterwards? And if the application had a bad day, where would your documents be?
If the answers are unclear, that is the gap, and it is a straightforward one to close.
After Premise is a Caspio Silver Partner. If you build on Caspio and would like to talk this through, see our Caspio page and the APDocs page for more.
Your documents, understood, not just stored.
