CMS_API_DELETE

functionality description filenet notes documentum notes box notes o365/sharepoint notes iv cmsprofile required determines which configured cms profile in docuflow sap to utilize combination of cms profile and cms tag determine the api destination and thus load across an rfc destination iv cmstag required determine which configured cms profile in docuflow sap to utilize combination of cms profile and cms tag determine the api destination and thus load across an rfc destination iv repository required determines which configured repository in docuflow sap to utilize object store docbase default is the only store/repository supported since box currently doesn’t support the notion of different repositories site, site collection iv type optional what cms type to delete document class object type metadata template content type iv use mapping optional use mapping of iv type to cms type in enterprise connector if cms used if archivelink doctype name to cms type mapping is required iv ids table of file id's (or folders id's if supported by your cms) iv location optional (mandatory for o365/sharepoint only and not used in any other cms system) specifies where to delete the document from not utilized not utilized not utilized this is required and is the document library for documents originally created by docuflow, this is stored at the time of create in a docuflow table in the scenario that the config changes and thus can be used for subsequent deletes et return table that indicates a success of an error the type field will contain an ‘s’ or ‘e’ respectively and the message field will contain information in the case of an error ct custom future use