Agnostic Guides
Solution Guide

DocManager

6min

DocManager is the central component, actioned by “rules”, that enables and controls most Gimmal Link processing in both directions inbound and outbound from SAP.  This includes enabling further Gimmal Link Enterprise add-on’s that might leverage DocManager such as Custom API Usage, DocMigrator, WFConnect and Publisher for example.  It also allows you to specify what metadata is transferred in both directions, as well as viewing capabilities, options, and link management.

Inbound to SAP DocManager processes

  1. SAPLink Create Link
  2. SAPLink Workflow Connect (WFConnect)
  3. SAPLink Accounts Payable
  4. SAPLink DMS
  5. SAPLink Custom Processing (class-method ABAP)

Note that all inbound to SAP DocManager processes require a rule in the Gimmal Link Enterprise Enterprise Connector to determine what content or events in your content management system are relevant to Gimmal Link Enterprise processing. Refer to the SAPLink section of this document for more information.

Outbound from SAP DocManager processes:

  1. Store New and Assign
  2. Publisher
  3. Custom API usage
  4. DocMigrator

Outbound from SAP DocManager processes requires only base installation and configuration. Please keep in mind however as you add outbound DocManager processes to consider load balancing the volume for performance reasons. Refer to the Gimmal Link Enterprise Installation and Base Configuration Guide for more information for information on these considerations.

Note that you can also use Gimmal Link Enterprise to store business documents to non-Gimmal Link Enterprise Content Servers. Simply configure the repository ID and relevant DocManager rule within Gimmal Link Enterprise for a consistent user interface for all your storage, linking, and viewing.

DocManager SFO/GOS Interface and Viewing

Below are some of the advantage to using the Gimmal Link DocManager SFO/GOS interface:

  1. Enhanced link attributes
  2. Link Attributes for older systems with no implementation of table TOAAT
  3. Delete Link Management via Gimmal Link Enterprise Link Manager
  4. Multiple file / drag & drop that also support SAP GUI for JAVA
  5. Virtual Link Manager to view links from connected SAP records without the duplication of link entries
  6. Activity Logging and Viewing
  7. Allows storage/linking/viewing to both Gimmal Link and non-Link connections
  8. Advanced viewing options to show and hide SAP DB notes, SAP DB attachments, as well as all ArchiveLink attachments
    1. The "hide" option is very useful for in-flight migrations for example
  9. Advanced BADI options for a wide variety of customizing options
  10. Allow "Notes" to be created in your external repository instead of your SAP database
  11. Supports Viewing attachments by auto-group via classification, Gimmal Link flow, or file extension

Configuration

DocManager leverages standard SAP ArchiveLink and therefore entries for specified Document Types must exist already in OAC2, and have their link entry with SAP Business Object configured in OAC3.

Additionally, with Gimmal Link Enterprise ECM it is highly recommended that you clear/disable the value in OAG1 "Always Copy Document Class from Document Type". This allows you to use the "*" in the OAC2 document class column whilst at the same time letting Gimmal Link add the appropriate file extension (ie: document class) in the Reserve field of the SAP ArchiveLink table (eg: PDF, XLSX, etc).

Configuring DocManager requires the below components:

  1. Creating a DocManager Rule
    1. Required for both inbound and outbound
  2. Enabling Store New and Assign / Attachment List Menu Path
    1. Required if you choose to use the Gimmal Link DocManager SFO/GOS dialogue window for either document linking, viewing, storage to non-Gimmal Link Enterprise repositories, or usage of Gimmal Link Enterprise Link Manager
  3. SAPLink / Inbound to SAP Processing
    1. Required for inbound processing only
    2. Configured at the Gimmal Link Enterprise middleware level
  4. Delete Link Management via Gimmal Link Enterprise Link Manager
  5. Attachment List Options
  6. SAP Logon Security Configuration

Note on ArchiveLink Doctypes

When creating document types in OAC2, consider the following:

  1. Doctypes drive SAP create and viewing authorization
  2. For Link Enterpise ECM or Content Server with Callback/Callback File move enabled: Doctypes drive location and metadata of document in SharePoint (and optional folder creation)
    1. Reminder: Native Content Server (without Link Enterprise Callback File Move) uses repository ID for location.
  3. If storing through content server AND viewing through content server (vs. any source of storage and viewing with ECM), you must create a document type for every file type/extension/mime-type ie: pdf, xls, xlsx, doc, docx, etc - which can result in a LOT of doctypes.
    1. This can be avoided by using an * in OAC2 and ensuring URL viewing is used.
      1. No further config required when using ECM to view via URL, however for content server basic Content Server Callback must be configured/enabled.



PREVIOUS
Viewing and Attachment List Options
NEXT
Creating a DocManager Rule
Docs powered by Archbee