In this lesson you
- Marked a document for manual rebuild, with a reason and a note
- Uploaded the author's rebuilt file as a new version
- Returned it to remediation, with only real work left
Transcript
A picture of a table
When a document needs rebuilding. What do you do with a document Proof can't fix in place? This schedule is an example. Its table is a picture. Someone pasted a screenshot instead of the table itself. Proof can describe a picture. It can't turn one into a real table, the kind with headers a screen reader follows from cell to cell. That takes the source file, the Word or InDesign file the PDF was made from. So the work has three moves. Park the document, bring in the rebuilt file, and put it back to work.
Park it
Why park it at all? While it waits for the author, nobody should spend time on it, and automation shouldn't either. Parking it also tells the right people that it's stuck, and why. To park it, open the version menu at the top of the document, and choose Mark for manual rebuild. The window asks why, so the right people see it. A reason is already chosen. The document needs to be re-authored at the source. Here it fits. The other reasons cover cases like a fix that didn't take, or a question only the author can answer. The note is for whoever picks this up. Replace the default text with what you saw. Then choose Escalate. The document is now marked Escalated. The note says who marked it, the reason, and your note. Automation and batch programs will skip it until it comes back. The note also says whether anyone was emailed, and that it's listed under Escalated, on Review. If your team can't rebuild it, Have Ockem do this asks Ockem's experts for a quote to remediate it. Auto-Certified or Assured explains that service.
The rebuilt file
Now for the rebuilt file. When it comes back from the author, open the version menu, and choose Upload new version. The window says what will happen. The file replaces the current version as version two, earlier versions stay in the history, and Proof checks it again. Pick the rebuilt file, and choose Upload. If the new file's words differ a lot from the old one, Proof asks whether it's a different document. For a rebuild, choose Replace this document. The schedule is a real table now. Pictures and tables has nothing left to answer.
Back into the work
Last, put it back into the work, with Return to remediation. Upload the rebuilt file first, as we did. Returning a document that's still broken just sends it back into the queues. Confirm, and it goes back to the working queues. Automation and batch programs can pick it up again. It's still unassigned. Only the Reading step is left, with two checks to review. Now you can park a document that can't be fixed in place, bring in its rebuilt file, and return it to the work.
Recap
That's the end of this lesson.
Maple Ridge Community Health, its documents and its people are fictional, made for these lessons.