Running a batch through the workflow

Now that you have completed updating auto fingerprinting to use FPXML, you can test it by running a batch through the workflow.

1. Start Taskmaster Web and log in to the TravelDocs application.
2. On the Operations tab, click VScan, browse to the location of the image files, click open and click Scan. When the task completes, click OK and Done. Then, click OK and Stop to return to the Operations tab.
3. Click Upload. When the task completes, click OK and Stop to return to the Operations tab.
4. Start Taskmaster DotScan, log in to TravelDocs, and select the PageID shortcut. When the task completes, click OK and exit from DotScan.
5. In the Taskmaster Web Operations tab, click the ManualPageID shortcut and wait for the page images to load. Then, scroll to the bottom and set the page type for the last page to Air_Ticket.
6. Click Done and then, click OK and Stop.
7. In the Operations tab, click the CreateDocs shortcut. When it completes, click Stop.
8. Start Taskmaster DotScan, log in to TravelDocs, and select the Profiler shortcut. When the task completes, click OK and exit from DotScan.
9. In the Taskmaster Web client, check the Job Monitor. You can see the result of the split, where the child job is pending for the Supervisor Verify task (row 1 below) and the main job is pending for the Main Verify task (row 3 below).
   
10. On the In the Operations tab, click the Supervisor Verify shortcut to open the pending batch. The Airline #4 page is displayed.
11. Define the zone for each field as you did earlier (see Running a batch through the workflow).
12. Click Submit and then, click OK. In the background, Taskmaster runs the AutoFingerprint ruleset to create the new fingerprint and the fingerprint XML file. Then, click OK and Stop.
13. In Windows Explorer, open C:\Datacap\TravelDocs\fingerprint and locate the most recent fingerprint. You can see a .cco, a .tif, and a .xml file for the new fingerprint. For example:
    
14. Open the fingerprint XML file in a text editor. Here is an example:

    <S>
    	<P type="Air_Ticket">
    		<V n="HostID">Air_Ticket</V>
    		<V n="HostName">Flight</V>
    		<F type="Outbound_From">
    			<V n="Position">649,488,1046,537</V>
    		</F>
    		<F type="Outbound_To">
    			<V n="Position">1052,486,1477,545</V>
    		</F>
    		<F type="Outbound_Date">
    			<V n="Position">182,484,386,541</V>
    		</F>
    		<F type="Return_From">
    			<V n="Position">646,619,1023,674</V>
    		</F>
    		<F type="Return_To">
    			<V n="Position">1053,621,1475,671</V>
    		</F>
    		<F type="Return_Date">
    			<V n="Position">188,617,360,675</V>
    		</F>
    		<F type="Airfare">
    			<V n="Position">1374,884,1513,928</V>
    		</F>
    		<F type="Taxes">
    			<V n="Position">1391,936,1509,981</V>
    		</F>
    		<F type="Total_Cost">
    			<V n="Position">1387,989,1522,1037</V>
    		</F>
    	</P>
    </S>

    Attention: If you run another batch through the workflow, it runs from end to end with no branching or splitting because the Airline #4 page is now in the fingerprint library. This time recognition task profile uses the zone position information from the fingerprint XML file.