Content Mapping

Defines a mapping between an OXI object type and a Grooper Content Type for import.

Remarks

The Content Mapping object is used to associate a specific OXI transaction or page type (such as BATCH_TICKET, PERSONAL_CHECK, etc.) with a target Grooper Content Type. This mapping determines how imported OXI objects are classified and processed within Grooper, ensuring that each item is assigned the correct Content Type for downstream extraction, validation, and workflow.

Purpose and Usage

• Use Content Mapping to control how OXI batches, transactions, and pages are converted into Grooper Batch Folders and Batch Pages.
• Each mapping links an OXI type to a Grooper Content Type, enabling accurate classification and data extraction.
• Multiple mappings can be defined to support all OXI types expected in your import batches.

Configuration Guidance

• For each OXI type you expect to import, create a mapping and select the corresponding Grooper Content Type.
• Review your OXI export process to identify all possible types and ensure each is mapped.
• Use the property grid to add, edit, or remove mappings as your import requirements evolve.

Best Practices

• Keep mappings up to date with any changes in your OXI export configuration or Grooper Content Types.
• Use descriptive Content Types to clarify the role of each mapping in your import workflow.
• Test imports with sample OXI batches to verify that all types are correctly classified and processed.

Example Scenario

• Map the OXI type PERSONAL_CHECK to a Grooper Content Type called "Personal Check".
• Map the OXI type BATCH_TICKET to a Grooper Content Type called "Batch Ticket".

Properties

Name	Type		Description
Oxi Type	OxiElement	►	The OXI transaction or page type to map. Requiredtrue DefaultBatch Can be one of the following values: Name Value Description Batch 0 The page starts a new batch. None 1 No page type. Transaction 2 The page starts a new transaction. BATCH_TICKET 3 The page is a batch ticket. PERSONAL_CHECK 4 The page is a personal check. BUSINESS_CHECK 5 The page is a business check. MONEY_ORDER 6 The page is a money order. STUB 7 The page is a check stub. PAGE 8 The page is a generic page. ENVELOPE 9 The page is an envelope. CHECK_LIST 10 The page is a check list. CASH 11 The page is currency CUSTOM_PAGE1 12 Custom page type 1. CUSTOM_PAGE2 13 Custom page type 2. CUSTOM_PAGE3 14 Custom page type 3. The 'Oxi Type' property specifies the OXI object type (such as BATCH_TICKET, PERSONAL_CHECK, etc.) that this mapping applies to. This value is matched against the OXI file during import to determine which Grooper Content Type should be assigned. Select the OXI type that corresponds to the transaction or page you want to map. Each OXI type should have a unique mapping to a Grooper Content Type. Example: Set 'Oxi Type' to PERSONAL_CHECK to map all personal check pages to the appropriate Content Type.
Target Content Type	Content Type	►	The target Grooper Content Type to assign to imported items of this OXI type. EditorContent Type Editor Requiredtrue The 'Target Content Type' property determines which Grooper Content Type will be assigned to items imported with the specified OXI type. This controls classification, extraction, and downstream processing for the imported content. Select a Content Type that matches the structure and business requirements for the OXI type. The selected Content Type will be used for all items of the mapped OXI type during import. Example: Map the OXI type BATCH_TICKET to a Content Type called "Batch Ticket" to ensure correct classification.

See Also

Content CategoryContent ModelDocument TypeForm TypePage Type

Used By

OPEX Import