Enter a unique configuration name. Used to identify a configuration by name throughout the system. (It is a good practice to include the document type to be part of the configuration name.)

A flag indicates that the configuration is enabled. If the configuration is not enabled no transfer jobs will be generated for documents matching the configuration settings. It might be helpful to control SAP testing.

Indicates if the current configuration is used for the barcode scenario.

Depending on this type the processing of the Messaging Service is controlled. It also determines which additional configuration items are available (workitem or barcode) later.

Initial transfer state for a document ready for SAP assignment.

This is the initial status of a transfer job. The status tells the Messaging Service that there are unprocessed documents.

Default value: START

Value: NOSTART if registration should be delayed. Transfer jobs later can be activated for processing by a Messaging Service client command.

This is the name of a content repository.

This is the content repository name by which the data in ImageMaster is accessible for a SAP System.

Here SAP document type for the SAP BAPI (name of the SAP API) call is defined. The value can be provided as fix or attribute value (read at runtime from the document attributes).

SAP assumes that documents linked with this type contain files of this mime type.

Name of the SAP interface is used for barcode transfer.

Used this to make the BAPI call. The customer may change the name in case of customization in SAP so it must be configurable. Default value is BAPI_BARCODE_SENDLIST for barcodes.

The selection controls the component checks for the document. This includes the mime type and compId check for the content objects in an ImageMaster document.

Used to ensure that the SAP document type selected (which maps to a real mime type and will be sent to SAP) conforms to the mime types in the content objects of the linked document. The check ensures that the mime type information is the same within all content objects. This check also enables the compId check which ensures a valid SAP component ordering.

• MIMETYPE: Check that the mime types in the binary objects (files) in the document map to this mime type and that they are all the same within a document. Ensure that compIds in the content objects are “data” or “data1 – dataN”.

• NONE: no checks at all

If the check is disabled viewing problems in the SAP GUI might occur for registered documents.

This is ImageMaster document type.

This parameter controls if a document being archived is checked to be a SAP document. It also provides the selectable index fields for the SAP Inbound scenario. The combination of Source Document Type and Logical System is unique.

Index field contains the barcode value.

Mandatory in barcode configurations to tell the Messaging Service in which attribute to find the barcode value. It is also a mandatory field in the SAP BAPI call.

The document has been archived on this date.

Mandatory parameter of the SAP BAPI call and contains the archive date of the document – actually the document attribute from where to get the value.

Choose an index field from the list (e.g. Supplier) which contains the selection criteria.

Specify an operator for the condition from the list. The following operators are available: equal, not equal, less, less equals, greater, greater equals, empty, not empty, includes, starts with.

Provide the value / placeholder that the document index field value should match.

ImageMaster multi-value fields are not supported. The first value will be taken.

Select to make the corresponding term ineffective.

Select to make the condition term case-insensitive.