CMS_API_UPDATE

functionality description filenet notes documentum notes box notes m365/sharepoint notes iv cmsprofile required determines which configured cms profile in link enterprise 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 link enterprise 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 link enterprise 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 update 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 checkout optional allows you to checkout a document only available in newer versions only available in newer versions not supported iv cancel checkout optional allows you to cancel the checkout of a document this will return an error if the document is already checked out iv location optional (mandatory for m365/sharepoint only and not used in any other cms system) specifies where to document to update resides not utilized not utilized not utilized this is required and is the document library for documents originally created by link enterprise, this is stored at the time of create in a link enterprise table in the scenario that the config changes and thus can be used for subsequent updates iv folder metadata optional if supported by your cms, setting this flag to true will apply metadata at the folder level the id's located in the it ids table will be folder ids applied metadata at the top level folder only applied metadata at all levels of folders it ids table of file id's (or folders id's if supported by your cms) it metadata mandatory metadata to set during updates some metadata cannot be set during update and is only read only (some system properties) updating some system properties in certain repositories may lead to unknown results the link enterprise username and timestamp properties are automatically set as metadata during update if they are configured on the particular cms tab in the link enterprise connector when the same keys are used multi valued properties are set with all of the specified values the zmulti flag is ignored during an update since the same key signifies a multi valued property by default to assist with the date format for filenet, you may choose to utilize the link enterprise helper method ‘/dflow/cl utilities helper=>format date’ to format a system date field to the format desired to assist with the date format for documentum, you may choose to utilize the link enterprise helper method ‘/dflow/cl utilities helper=>format date’ to format a system date field to the format desired currently doesn’t support multi valued metadata where a date field is part of the metadata being sent, the format must be mm/dd/yyyy hh\ mm\ ss a z, where a z = the am/pm and timezone example 12/31/9999 12 00 00 pm mst to assist with the date format for box, you may choose to utilize the link enterprise helper method ‘/dflow/cl utilities helper=> format date plus sys timezone’ to format a system date field to the format desired and also appending the system timezone currently doesn’t support multi valued metadata 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