IBM Datacap, Version 8.1

Examination of page and field status values

The validation rules affect the status that Taskmaster assigns to the status variable for each page and field. To see the page status, open Profiler.xml in the application's most recent batch folder.

The Profiler.xml file includes the status of each page in the batch.

<D id="20100323.007.01">
   <V n="TYPE">Car_Rental</V>
   <V n="STATUS">0</V>
   <P id="TM000001">
      <V n="TYPE">Rental_Agreement</V>
      <V n="STATUS">1</V>
      etc.
   </P>
   <P id="TM000002">
      <V n="TYPE">Optional_Insurance</V>
      <V n="STATUS">0</V>
       etc.
   </P>
</D>
<D id="20100323.007.02">
   <V n="TYPE">Car_Rental</V>
   <V n="STATUS">1</V>
   <P id="TM000003">
      <V n="TYPE">Rental_Agreement</V>
      <V n="STATUS">1</V> 
       etc.
   </P>
</D>
 etc.
<D id="20100323.007.04">
   <V n="TYPE">Flight</V>
   <V n="STATUS">1</V>
   <P id="TM000006">
      <V n="TYPE">Air_Ticket</V>
      <V n="STATUS">1</V> 
       etc.
   </P>
</D>
etc.

A status of 0 indicates that there are no problems, and a status of 1 indicates that a problem exists. The three problem pages that are shown in the preceding have Status = 1 for different reasons. To see the nature of the problems, review the individual page files: tm000001.xml, tm000003.xml, and tm000006.xml.

TM000001

The following example shows a portion of the tm000001.xml page file:

<?xml-stylesheet type="text/xsl" href="..\..\dco.xsl"?>
<P id="TM000001">
<F id="Pickup_Date">
   <V n="TYPE">Pickup_Date</V>
   <V n="Position">189,403,567,465</V>
   <V n="STATUS">0</V>
   <C cn="7" cr="200,416,220,440">84</C>
   <C cn="4" cr="218,415,226,430">114</C> 
   <C cn="10" cr="218,423,230,438">117</C>
   etc.
</F>
<F id="Pickup_Location">
   <V n="TYPE">Pickup_Location</V>
   <V n="Position">195,537,558,592</V>
   <V n="STATUS">0</V>
   <C cn="10" cr="203,549,216,570">66</C>
   <C cn="10" cr="219,555,234,570">111</C>
   etc.
</F>
<F id="Return_Date">
   <V n="TYPE">Return_Date</V>
   <V n="Position">580,403,942,465</V>
   <V n="STATUS">0</V>
   <C cn="6" cr="593,416,604,438">70</C>
   <C cn="6" cr="606,423,615,438">114</C>
   <C cn="7" cr="619,416,621,438">105</C>
   <C cn="10" cr="625,434,630,441">44</C>
   <C cn="10" cr="690,416,691,438">32</C>
   etc.
</F>
etc.

All of the fields in TM000001 have Status = 0 (OK), but the pickup date and return date fields have low confidence characters. By default, any character with a confidence level below 8 is considered low confidence and is displayed to an operator for verification.

TM000003

The following example shows a portion of the tm000003.xml page file:

<?xml-stylesheet type="text/xsl" href="..\..\dco.xsl"?>
<P id="TM000003">
<F id="Pickup_Date">
   <V n="TYPE">Pickup_Date</V>
   <V n="Position">0,0,0,0</V>
   <V n="STATUS">0</V>
<F id="Pickup_Location">
   <V n="TYPE">Pickup_Location</V>
   <V n="Position">0,0,0,0</V> 
   <V n="STATUS">0</V>
</F>

Because you only defined recognition zones for the first fingerprint of each page type, TM000003 has no data that is associated with any of the fields. Page TM000003 is the rental agreement page for Car Rental #2 and has no recognition zones. Fix this problem and then run the batch again.

TM000006

The following example shows a portion of the tm000006.xml page file:

<?xml-stylesheet type="text/xsl" href="..\..\dco.xsl"?>
<P id="TM000006">
etc.
<F id="Airfare">
   <V n="TYPE">Airfare</V>
   <V n="Position">359,805,527,854</V>
   <V n="STATUS">1</V>  
   <V n="MESSAGE">Failed By Calculate Action On Field &apos;TM000006&apos;.</V>
   etc.
</F>
<F id="Taxes">
   <V n="TYPE">Taxes</V>
   <V n="Position">359,861,525,905</V>
   <V n="STATUS">1</V> 
   <V n="MESSAGE">Failed By Calculate Action On Field &apos;TM000006&apos;.</V>
   etc.
</F>
<F id="Total_Cost">
   <V n="TYPE">Total_Cost</V>
   <V n="Position">361,912,527,961</V>
   <V n="STATUS">1</V>  
   <V n="MESSAGE">Failed By Calculate Action On Field &apos;TM000006&apos;.</V> etc.
</F>
</P>

In TM000006, the Calculate('Airfare' + 'Taxes' = Total_Cost') validation action failed. Since Taskmaster cannot know which of the field values is incorrect, it flags all fields.

Feedback