SAPLink / Inbound to SAP Processing

unsupported in s3 saplink is the inbound processing from your content repository to sap this can be leveraged to execute a number of docuflow delivered functions in sap or your own custom logic thus, why we call saplink the "do anything pipe" into sap there are three components involved in saplink processing ensure the cms document class/object type/metadata template has the required fields for saplink processing configuration a "rule" in the enterprise connector middleware this determines what content is to be processed, when, and what (if any) metadata is to be transferred what is processing is dependent on the cms system being used (outline more below) configuration of a corresponding docmanager rule in sap that matches the document type configured in step 2 this determines what action is to be performed in sap (link a document, trigger custom code, start accounts payable workflow, etc ) note the docuflow system account specified in the middleware must have access to the transaction /dflow/docuflowgtw in its security profile to execute inbound to sap jco calls please refer to the section "create sap system account" in the base installation and configuration guide the inbound processing rule determines what is to be processed what metadata is to be sent to sap how to configure a saplink rule in enterprise connector load up in the browser the onfigurator https //localhost 82/box under "mappings" click inbound to sap hover over each of the input boxes in the ui to look at sample values for each input box click save restart the docuflow service notes the docmanager rule in sap determines what action is to be performed in sap for each item "found" from a saplink rule in the connector each request is processing and calls a docuflow bapi within the sap, which then reads the docmanager rule configuration found for that doctype there can only be one archivelink document type and sap business object combination ever configured in the docmanager configuration, thus avoid sharing document types across sap object (to avoid an inbound collision) docuflow will then execute the configured action and pass back a return, either an error or success in the case of a success, the trigger property is set too false to prevent a re processing of that item found in the case of an error, the error property, if relevant to your cms system, will be updated in both scenarios, the docuflow username and time stamp fields are updated upon a success saplink, metadata can also be enabled to be transferred back to your cms system rule config what is to be processed inbound to sap entries search for documents that meet specific criteria and send the information to sap for processing if processing completes successfully, the trigger property is adjusted so that the document is not processed again if the processing were to fail by default, the processing is tried again in order to not retry failed documents, adjustments can be made to the filter string to omit documents that were in error setting description sample value(s) enable inbound to sap if checked, configuration for inbound to sap is enabled and can be configured for inbound to sap processing sap the sap system to send document metadata too sap dev ed1 cms the cms system to get document metadata from trigger data type data type by which the saplink rule is triggered task and sign task type only applicable for box workflow tasks boolean, timestamp, task and signtask sap repo the sap archivelink repository that should be associated with this metadata being passed zc sap type the sap archivelink document type associated with this metadata being passed zcontract cms repo the content management system object store or repository for box implementations, use “default” default cms type the content management system document class, object type or metadata template to look for the requested metadata in scmcontracts interval the inbound to sap process searches for documents matching the configured criteria and then sends the information to sap this interval determines how often the underlying content management system is searched for box implementations, setting this value less than 5 minutes has no value 10 trigger prop the content management system property or attribute associated with when to trigger sending information to sap by default, docuflow sets this property to true or false based on the result of a saplink call to sap these values can be manipulated via the config properties file with the below entries saplinkfalse value=\<value> (for success) saplinkerror value=\<value) (for error) docuflowsaplinktrigger saplinkfalse value=donotprocesssuccess saplinkerror value=donotprocesserror type the trigger property or attribute type boolean triggers happen when the boolean property or attribute is set to true timestamp triggers happen when the configured date/time property or attribute has no value currently, box and m365 implementations only support boolean trigger types (even though in box the type is single value dropdown text and sharepoint is single line of text) boolean error prop if an error happens while trying to process a particular file you can optionally store the error information in the content management system docuflowsaplinkerror type the error property or attribute type boolean error types are only set to true if an error happens timestamp error types only set a date/time stamp when an error happens string errors put as much of the error as they can into the configured error property or attribute this is the preferred configuration currently m365 implementations only support string (single line of text) and box supports text string max an optional setting to limit the number of entries returned when searching for documents a setting of 0 has no limit 0 filter an optional (with filenet and documentum and implementations but required for box) filter string to finely tune what is searched for in the underlying content management system refer to the where clause documentation for working with the search utility in the appendix for help configuring a filter clause for documentum and filenet filter clauses you must start with and or or since the documents are already being searched for by the configured trigger type so this additional filter logic needs to be added on with and or or notations some examples are and \<insert error property name> is null (which omits documents that have already errored when using a string based error property) or lastmodifier <> ‘\<insert docuflow filenet username>’ (which handles updates to documents as well as the first time they are created) or lastmodifier <> ‘\<insert docuflow filenet username>’ and \<insert error property name> is null (which omits error documents and also handles updates to documents) or r modifier <> ‘\<insert docuflow documentum username>’ (which handles updates to documents as well as the first time they are created) or r modifier <> ‘\<insert docuflow documentum username>’ and \<insert error property name> is null (which omits error documents and also handles updates to documents) for box implementations you must enter in a filter clause which is the input to the metadata search web service for box (box example) search api mdfilters=\[{"templatekey" "scmcontracts", "scope" "hi enterprise","filters" {"docuflowsaplinktrigger" "true"}}] \&limit=50\&offset=0 (box example) metadata query {"from" "enterprise 761921826 metadatatemplate","query" "docuflowsaplinkenabled = \ value","query params" {"value" "true"},"ancestor folder id" "131865107948"} (filenet example not including documents in error) and docuflow saplinkerror is null (sharepoint example) fields/sapfacility eq 'complete' and fields/docuflowsaplinktrigger eq 'true' location an optional location to further limit where documents are searched for this is only possible with filenet and documentum implementations and not possible with box and sharepoint implementations order by an optional order by clause to order the returned results make sure to include the metadata being ordered by in the metadata comma separated list this is only possible with filenet and documentum implementations and not possible with box and sharepoint implementations sourcetriggerproperty an optional property or attribute associated to trigger when sign task is completed (box sign) middlewareoriginaldocid lineitemcolumn an optional property which is referred to csv file containing line item information (reference to a csv file) sub if enabled sub folders will be searched for more information refer to the search utility in the appendix for help this is only possible with filenet and documentum implementations and not possible with box and sharepoint implementations rule config what metadata is to be sent to sap what metadata is sent from your repository to sap is determined by the metadata column setting description sample value(s) metadata the comma separated list of metadata to send to sap in the specified order title,contract,name rule config sign task sign task config setting description sample value(s) sourcetriggerproperty the content management system property or attribute associated to trigger when the sign task is completed middlewareoriginaldocid