Save documents only if they pass the workflow

ECM
,
1

I’m working on a workflow to scan in training records for our system. The workflow does OCR on the document, does some datalink queries to pull in data based on this OCR stuff, then changes the title and a few other fields based on the data.

However, the content ends up being saved into the folder (based on content type) before the workflow even starts. I’d love for the operator to scan things in, have the workflow run, then only save the documents after verifying or editing content fields (we have a few errors from the OCR that pop up about 10% of the time right now).

I can’t find any documentation on how to do something like this. Is it possible? If so, where should I be setting that up?

2

ECM has to store the document immediately once it’s given control and responsibility for that document - otherwise where is it? The default locations set up in the Content Type editor is what it uses. Or it goes in the default top-level ‘folder’ (not really a folder) that we call The Void.

You should make the first action of your workflow move the document to a ‘queue folder’ of your making. That way the document will be segregated from all approved/finished documents, but still be visible and manageable to admins.

1 Like
3

You should be able to assign a starting folder in the Content Type for these documents you’re processing. If you leave the starting folder parameter as blank, then it goes into The Void, as @MikeGross described it lol

1 Like
4

Are there any tasks besides “approval” that I can set in the workflow to have the operator confirm things look good, then move it to the final destination as the last workflow step? I don’t see anything like a “confirm content” or something like that, but that’s all I really need.

5

Using the assumption you don’t want to use the User Approval task, I can think of a few other methods. In no particular order:

  1. Display Message - Add a display message and the only option is to click Submit to proceed.

  2. User Verification - Provide the user with a binary decision of two options and move the workflow in the corresponding direction based on the option selected.

  3. User Prompt (True/False) - Have the user select a checkbox and then Submit to proceed.

  4. Branching - This isn’t a task but instead allows the user to select the branch you want to allow them to choose. This displays as a blue button for each branch option available to the user.

2 Likes