The data location identifier determines about the kind of value that is mapped and where this is located in the ImageMaster document data model. For example, if you want to access an attribute with an invoice number in the document type “Customer”, select “attribute” as data location and specify the name of the attribute, e.g. “CustomerID”. This extracts the value of the attribute “CustomerID” for the document revision currently processed, and transfers this value via the mapping process.
Figure 446: Data location identifier with specified mapping
|
Data location |
Description of the associated mapping |
|---|---|
|
fix |
a fixed value A constant value as specified by the configuration is set. |
|
attribute |
a customized attribute (of an ImageMaster document revision) The value is transferred from the attribute of the specified name, which must exist in an ImageMaster document revision (in the given ImageMaster source document type). |
|
attribute_system |
a system attribute (of an ImageMaster document revision) The value is transferred from the system attribute of the specified name, which exists in an ImageMaster document revision (in the given ImageMaster source document type). In contrast to normal attributes that are customized, system attributes with predefined names always exist: revisionId, documentId, creationTime, modificationTime |
|
attribute_sap |
an SAP attribute (of an ImageMaster document revision) SAP attributes always exist for any SAP document type in ImageMaster like: content repository, (SAP) document ID, logical system |
|
attribute_bin |
a customized content property (of an ImageMaster document revision) The value is transferred from the property of the specified name, which must exist in the first content object in an ImageMaster document revision (in the given ImageMaster source document type). An ImageMaster document revision supports multiple content objects. In such a scenario you must ensure that the first object really is the desired one. |
|
attribute_bin_system |
a binary object property (of a binary file in an ImageMaster document revision) The value is transferred from the property of the specified name, which exists in the first binary object in an ImageMaster document revision (in the given ImageMaster source document type). A binary object always exists if a file was successfully archived in ImageMaster: fileSize, fileName, mimeType, hashDigest, hashAlgorithm, creationTime, modificationTime An ImageMaster document revision supports multiple binary objects. In such a scenario you must ensure that the first object really is the desired one. |
|
Table 256: Data location identifier and mapping description |
|