DocManager Metadata maps

as a more powerful option to using the metadata map configuration, class/method metadata maps allow you to compile the sap data via abap that will update your cms documents (if configured) for outbound gimmal link storage and mass metadata push/updates example method /dflow/cl docmanager helper=>metadata example the below example is provided with the gimmal link enterprise product signature type parameter description sample value importing iv sap object the sap business object associated with this process bkpf importing iv doctype the archivelink document type to use for linking documents with this process zinvoice01 importing iv sapkey the unique identifier of the sap records the link will be created to 300019000000002013 importing iv arc doc id the unique identifier of the cms document {83281172 dd17 4b8a 8913 9e5e69ba3125} exporting et metadata this is the resulting table of key (case sensitive cms property name) value (sap data) pairs of the sap data to update the cms document with that you must fill with your abap code notes if you want to update a multi line property (only supported in documentum and filenet cms systems), place an x in the field zmulti for box cms systems 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 gimmal 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 to assist with the date format for filenet and documentum, you may choose to utilize the gimmal link enterprise helper method ‘/dflow/cl utilities helper=>format date’ to format a system date field to the format desired