The following data is available for output from your solutions. Most of the variables listed here are used in XML output for example.
Specification |
|
|
The GUID of the specification. |
|
The system date and time when the specification was created. |
|
The system date and time when the specification was modified last. |
|
The name of the specification. |
CompoundDocument/Batch |
|
|
The name of the specification that the compound document, or batch, is based on. |
|
The compound document, or batch, GUID. |
|
The system date and time when the compound document, or batch, was created. |
|
The system date and time when the compound document, or batch, was modified last. |
Members |
|
|
The number of members included in the compound document/batch. A member can be a document or a compound document for example. |
Document |
|
|
The name of the document specification the document is based on. |
|
The name of the queue, if any, that the document belongs to. |
|
The document GUID. |
|
The system date and time when the document was created (scanned/read from file). |
|
The system date and time when the document was last modified. |
|
The number of appendices the document has. |
|
|
|
The sender of the email. This attribute is only available if the input source is email. |
|
The recipient of the email. This attribute is only available if the input source is email. |
|
The subject of the email. This attribute is only available if the input source is email. |
|
Additional recipients of the email. This attribute is only available if the input source is email. |
|
The message body of the email. This attribute is only available if the input source is email. |
Pages |
|
|
The number of |
Page |
|
|
Specifies whether the page is an appendix. |
|
The page number within the document. |
|
Specifies whether the page is flipped. |
|
Specifies whether there is a file associated with the page. |
|
The original path and file name of the page's source file. |
|
The current path and file name of the page. |
|
The page number within a multi-page file such as a multi-TIFF file. This value is set to zero if the file does not have multiple pages. |
|
|
|
Describes additional information that can be necessary when accessing the file, for example, the PDF version. |
|
The endorser made by the scanner. |
|
The page number within the batch. |
|
The location of the original file (before it was enhanced). |
Fields |
|
|
The number of |
Field |
|
|
The name of the field specification the field is based on. |
|
The number of the field. |
|
The value of the field (as a string). |
Scan |
|
|
The name of the specification. |
|
The GUID of the specification. |
ScannerName |
The name of the scanner. |
|
The resolution of the scanner in dots per inch. |
|
The brightness of the scanner. |
|
The manufacturer of the scanner. |
|
The contrast of the scanner |
|
The number of bits used to define each pixel. |
|
A description of the scanner. |
|
The driver used to run the scanner. |
AuditTrail |
|
|
The number of member |
Records |
|
|
The user who performed the production task or made the change. |
|
The system date and time when the change was made. |
|
The production task being performed at the time the change was made. |
Details |
|
|
The number of member |
Structs |
|
|
|
|
|
|
|
|
The current value of the parent of the current |
|
The value prior to the change. |
|
|
|
All data from the Invoice extraction, which contains
|
|
Describes a collection of fields. Contains elements. |
|
Describes a field. Note: Date fields are formatted YYYYMMDD. |
|
Contains elements. |
|
Describes a table. Contains elements. |
|
Contains remarks that users added to invoices. elements that describe system fields. One example of this is |
|
Describes a supplier or buyer. |