Creating a DocManager Rule

to create a docmanager rule, enter transaction /dflow/sys and choose the menu path configure >api rules >docmanager parameter description sample value object type the sap business object that is relevant to this docmanager rule this and document type make up the unique rule key bkpf document type the archivelink document type configured in oac2 that is relevant to this docmanager rule this and sap business object make up the unique rule key for link creation, and entry in oac3 must exists for these two and the configured cont rep id below (and in the gimmal link enterprise base product and oac0) zwfinvsp01 en dm store new sfo enable services for object (sfo or gos) for sap to cms business document storage true or false en dm link ex sfo enable link existing document via drag and drop from cms to sap via ole (future use) off en sl cs cb enable sapink content server callback if enabled, for content server "create" saplink will create cmsid< >sapdoc mapping and will execute metadata transfer or other docmanager rules if configured en sl cs move enable sapink content server callback file mover if enabled, for content server "create" saplink will move from a content server dropzone (via a re store) to a final location this allows for a full feature set even though a document is stored via content server, such as folder creation, dynamic location, external bpm and task creation, etc in short everything that a document stored via ecm can do (metadata and viewing is handled above with en sl cs cb) en dm sl cr link enable saplink create link which automatically creates archivelink links for cms inbound to sap processing requests this is used with cms m data key or s link cust class/method to determine the sap key to link to (ie must match exactly archivelink object id) true or false en sl wfconnect enable workflow connect to trigger sap workflow code free (and fill workflow containers with metadata from cms) for cms inbound to sap processing requests true or false en sl custom enable custom abap code for cms inbound to sap processing requests (code is contained in link cust class/method) true or false en dm sl v1b enable passing of csm inbound to sap processing requests to gimmal link v1 true or false allow sl nocont for repositories that support contentless records, enable this to allow these to send inbound to gimmal link sap saplink requests true or false en dm publish enable sap to cms outbound saving of message output data with metadata true or false en dm custom enable custom api usage for sap to cms outbound processing (code is container in your own z namespace abap) true or false en migration enable docmigrator for this rule true or false hide att list hide this sap business object/doctype combination on the gimmal link enterprise sfo/gos attachment list menu for existing links true or false hide act list hide the activity list tab on the sfo/gos attachment list menu to prevent showing activity for this sap business object/doctype true or false cms profile determines which configured cms profile in gimmal link sap to utilize combination of cms profile and cms tag determine the api destination and thus load across an rfc destination gimmal demo cms use tag determine which configured cms profile in gimmal link sap to utilize combination of cms profile and cms tag determine the api destination and thus load across an rfc destination gimmal demo cont rep id determines which configured repository in gimmal link sap to utilize for sap to cms processing zf cms type determines which cms types to use for gimmal link sap to cms outbound processing (typically create) filenet document class for create, defaults to the “document” document class if unspecified documentum object type for create, defaults to the “dm document” class if unspecified box metadata template for create, defaults to creating a document with no metadata template if not specified sharepoint on prem/sharepoint m365 content type for create, defaults to creating a document of content type document if not specified accountspayable cms location specifies where the content resides for gimmal link enterprise sap to cms outbound processing (typically create) cms location allows environment variable usage in short these allow for different values based on your sap system id (ex dev / qa1 / prd) please refer to the gimmal link enterprise installation and base configuration guide under “environment variables” for detail on how to configure and utilize filenet if unspecified documents are left unfiled documentum if unspecified documents are stored in root of the user’s cabinet box best practice folder number/id for the exact folder location can be specified if unspecified documents are stored in the configured root folder of the enterprise connector relative folder names can be used with a / being the root if a root folder is configured for the box cms in the enterprise connector all relative folder locations will be relative to the root folder configured relative folder names are not recommended for performance reasons sharepoint on prem/sharepoint m365 optional sub site url (added on to repository url) with mandatory document library specified last 5523993 own folder determines whether a file is stored in the cms location (not enabled), versus when enabled the enterprise connector will check if there is a folder with the name “sap \<sapkey>” if there is one (as a subfolder to cms location), the file is stored there otherwise it will create one automatically and store the file there true or false link folder if own folder is enabled, whether to create an archivelink link to the folder vs the file linking to a folder, when viewed from sap, will show the folder view and all of it’s contents linking to a file will bring up the box preview of the file being viewed true or false cms m data key for inbound from cms to sap processing requests for “en dm sl cr link” (ie automatic link creation), if an sap key does not need to be formatted or retrieve and is an exact match in your cms system to the archivelink key required (with formatting/padding, etc ), you can specify that property name here otherwise, you must use a s link cust class/method to determine the sap key to link to invoicesapkey s link cust class for inbound from cms to sap processing requests for “en dm sl cr link” (ie automatic link creation), if an sap key sneed to be formatted or retrieve or is not an exact match in your cms system, you can compile the sapkey here (either with the metatata or sap lookup) otherwise, you must specify the key in the cms m data key field to determine the sap key to link to refer to the gimmal link enterprise developers guide for more information on how to program these class/methods /dflow/cl docmanager helper s link cust method see above “s link cust class” saplink example en md trans map applicable to both inbound and outbound processing patterns, this no code option generates metadata mapping from sap to your cms system if enabled, a metadata map must exist under the configure >metadata mapping on the gimmal link sap system dashboard true or false en md trans cus applicable to both inbound and outbound processing patterns, this code option generates metadata mapping from sap to your cms system if enabled, the below metadata class/method must be specified true or false metadata class refer to the gimmal link enterprise developers guide for more information on how to program these class/methods /dflow/cl docmanager helper metadata method see above “metadata class” metadata example description english description for cosmetic reasons on the overall system “fi invoice processing”