The fingerprint XML file
You can move the zone position information of a fingerprint out of the document hierarchy and into a separate fingerprint XML (FPXML) file.
Document hierarchy XML:
<F type="Pickup_Date">
<V n="ID">0</V>
<V n="TYPE">Field</V>
<V n="STATUS">0</V>
etc.
<V n="Pos556">183,402,535,463</V>
<V n="Pos558">568,331,967,389</V>
<V n="Pos560">1199,389,1600,448</V>
</F>
<F type="Pickup_Location">
<V n="ID">0</V>
<V n="TYPE">Field</V>
<V n="STATUS">0</V>
etc.
<V n="Pos556">180,528,532,589</V>
<V n="Pos558">573,448,967,502</V>
Fingerprint XML file:
<S>
<P type="Rental_Agreement>
<V n="HostID">226</V>
<V n=HostName">Car_Rental</V>
<F type="Pickup_Date">
<V n="Postion">183,402,535,463</V>
</F>
<F type="Pickup_Location">
</V>
<V n="Postion">180,528,532,589</V>
</F>
etc.
Although the total number of files is increased because each fingerprint now has a TIFF file, a CCO file, and an XML file, this approach has several benefits:
- The document hierarchy XML file remains small.
- Overall performance can increase.
- It eliminates possible contention if multiple users attempt to add fingerprints simultaneously.
Attention: These benefits apply to applications that use
dynamic, action-based fingerprint generation, because Datacap Studio writes to the document
hierarchy and the fingerprint XML file when FPXML is enabled.