DocManager

docmanager is the central component, actioned by “rules”, that enables and controls most docuflow processing in both directions inbound and outbound from sap this includes enabling further docuflow 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 saplink create link saplink workflow connect (wfconnect) saplink accounts payable saplink dms saplink custom processing (class method abap) note that all inbound to sap docmanager processes require a rule in the docuflow enterprise connector to determine what content or events in your content management system are relevant to docuflow processing refer to the saplink section of this document for more information outbound from sap docmanager processes store new and assign publisher custom api usage 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 docuflow installation and base configuration guide for more information for information on these considerations note that you can also use docuflow to store business documents to non docuflow content servers simply configure the repository id and relevant docmanager rule within docuflow 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 docuflow docmanager sfo/gos interface enhanced link attributes link attributes for older systems with no impleementation of table toaat delete link management via docuflow link manager multiple file / drag & drop that also support sap gui for java virtual link manager to view links from connected sap records without the duplication of link entries activity logging and viewing allows storage/linking/viewing to both docuflow and non docuflow connections advanced viewing options to show and hide sap db notes, sap db attachments, as well as all archivelink attachments the "hide" option is very useful for in flight migrations for example advanced badi options for a wide variety of customizing options allow "notes" to be created in your external repository instead of your sap database supports viewing attachments by auto group via classification, docuflow 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 docuflow 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 docuflow 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 creating a docmanager rule required for both inbound and outbound enabling store new and assign / attachment list menu path required if you choose to use the docuflow docmanager sfo/gos dialogue window for either document linking, viewing, storage to non docuflow repositories, or usage of docuflow link manager saplink / inbound to sap processing required for inbound processing only configured at the docuflow middleware level delete link management via docuflow link manager attachment list options sap logon security configuration note on archivelink doctypes when creating document types in oac2, consider the following doctypes drive sap create and viewing authorization for docuflow ecm or content server with callback/callback file move enabled doctypes drive location and metadata of document in sharepoint (and optional folder creation) reminder native content server (without docuflow callback file move) uses repository id for location 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 this can be avoided by using an in oac2 and ensuring url viewing is used no further config required when using ecm to view via url, however for content server basic content server callback must be configured/enabled