IBM Datacap, Version 8.1            

Updating the application

You configured the PageID ruleset to use multiple page identification techniques that are implemented in a cascade fashion. To demonstrate manual page identification by using AIndex, you are going to remove the text matching and pattern matching functions and send any batch with unidentified pages to AIndex.

However, if you are using AIndex for manual page identification you must run the manual page identification task after you create a structured batch. You need to move the branching function out of the PageID task and into the CreateDocs task. You also need to make sure that each unidentified page is a separate document, which requires an update to the document hierarchy.

Updating the PageID ruleset

  1. In the Datacap Studio window, click Connection Wizard at the upper right.
  2. Select the TravelDocs2 application, click Next, enter the admin password, and click Finish.
  3. Select the PageID ruleset and click Lock/Unlock rulset for editing.
  4. Expand the PageID ruleset and the PageID rule.
  5. Remove the Identify using Text Match function and the Identify using Pattern Match function.
  6. Expand the Identify Manually function and remove the Task_NumberOfSplits action and the Task_RaiseCondition action.
  7. Change the parameters on the rrSet action as shown in the following table.
    Library Action Parameter
    rrunner rrSet varSource = Yes

    varTarget = @B.ManualID

  8. Click Save. Then, click Lock/Unlock ruleset and choose Publish ruleset. The PageID rule should look like the following example.

Updating the Document Integrity ruleset

The CreateDocs task profile includes two rulesets: CreateDocs and Document Integrity. Because you need to branch to AIndex after you create the structure batch, you add the branching function to the Document Integrity ruleset.

Previously, you used the Document Integrity ruleset to raise a branch condition if the batch had structural problems that required manual fixup. You are going to modify this ruleset to raise the branch condition if the batch contains any pages that require manual identification.

  1. Select the Document Integrity ruleset and click Lock/Unlock rulset for editing.
  2. Expand the Document Integrity ruleset, the Batch Document Integrity Check rule, and both functions.
  3. Remove the CheckAllIntegrity action from the first function and replace it with the following action.
    Library Action Parameter
    rrunner rrCompareNot object1 = @B.ManualID

    object2 = Yes

    Attention: This action returns False if the batch variable ManualID is Yes, which causes the rule to start the Batch Route To Fixup function. The PageID rule configures this variable to Yes if the batch includes pages that failed fingerprint matching.
  4. Click Save. Then, click Lock/Unlock ruleset and choose Publish ruleset.

Updating the Document Hierarchy

  1. In the document hierarchy pane, click Lock DCO for editing.
  2. Expand the Document Hierarchy so that you can see the Other page and the Air Ticket page.
  3. Right-click the Other page and choose Manage variables. Then, set the Order value to -1 and click Done.
    Attention: Setting the Order value to -1 causes the CreateDocs action to create a new document for each page of type Other.
  4. Expand the Air_Ticket page.
  5. Right-click the Vendor_Logo field and choose Manage variables.
  6. Click New, type Required, and press Enter.
  7. Set the value of the Required variable to 1 and click Done.
  8. Click Save changes and then click Unlock DCO.

Changing the branch condition

  1. Open the Taskmaster Web and click the Administrator tab.
  2. Click Workflow tab, expand Main Job, expand CreateDocs, and select the Document Integrity Failed condition.
  3. Click the down-arrow beside the Child Job field and choose ManalPageID Job.
  4. Click Apply and then click Done.


Feedback

Last updated: November 2013
dcadg561.htm

© Copyright IBM Corporation 2013.