Fiori DocManager - SAP Fiori Launchpad Plugin (cloned) (cloned)

deployment guide for docmanager fiori plugin (v3 0) topic description plugin features required back end product sap s/4hana fps 2021 and above s4 core 106 or above (for draft mode support) required back end ecm components sap transport (ecm) add on minimum ui5 version requirements sap ui5 1 114 11 description attachments are an integral part of business applications and processes in sap s/4hana, the docmanager fiori plugin is offered as a central unified solution for uploading attachments across applications the applications can integrate operations such as upload, download, delete and access to virtual links the docuflow docmanager fiori plugin is a reusable component that can be integrated to any standard sap fiori object based app e g purchase order based application to enable attachment capabilities in sap s/4hana implementation information sap transports contact account manager or versafile point of contact implementation information installation & configuration the app consists of front end components (such as the user interfaces) and back end components (such as the odata service) the back end and front end components are delivered as sap transports and have to be installed in a system landscape that is enabled for sap fiori front end components • sap bsp application /dflow/fiodocman • icf path /sap/bc/ui5 ui5/dflow/fiodocman • ui5 component dflow\ fiori plugin docmanager component • package /dflow/docuflow fio docmanager back end components (abap) • odata service – external service name – /dflow/fiori docmanager srv technical service name /dflow/fiori docmanager srv 0001 version – 0001 package – /dflow/docuflow fio docmanager • plugin definition – navigate to transaction /ui2/flp conf def to define properties for your plugin as shown in screenshot below (taken care by transports so more of validation) properties below property definitions explained are key to the overall functioning of the plugin component (these entries are delivered with package please consult your product support contact for any questions ) • badge max value = badgemaxvalue \ the maximum number to display in the buttons' badge if the number of attachments is greater than the maximum number, the maximum number followed by a plus sign will be displayed • display badge = displaybadge \ controls whether or not to display a badge next to the plugin button with the number of attachments • display type = displaytype is linked to the appearance or user experience of the plugin which basically is defaulted to ‘dialog’ but alternatively ‘popover’ is supported too • draft enabled = draftenabled \ this property is used to control the availability of draft feature in general enabling/activating the plugin (customizing) /ui2/flp cus conf → to make your plugin available in specific clients property values providing values to the property defined is performed in this transaction these values govern the app behavior and shouldn’t be changed without consulting product support values are case sensitive too • ui adaptation the docmanager plugin was developed to replace sap’s standard attachment services ui, addressing its limitations and offering additional functionality to prevent users from seeing the default “attachments” tab in fiori apps, use the key user adaptation approach to hide the standard “attachment” feature wherever docmanager is enabled our solutions team will help adapting apps during implementation but for further details please refer to standard sap guide here to learn more about pre requisites and approach • plugin activation control in addition to the core ecm configurations in order for the fiori plugin to work we also deliver an configuration cluster /dflow/fdmcfg that can be accessed via t code /dflow/sys > menu path > configure > “attachment services” > “fiori options” to control the plugin activation per any standard or customer fiori apps and along with other additional technical details our solutions team works with customers to identify potential sap business processes to be enabled and accordingly help populate required information based on your sap s/4hana version below is a sample entry for activating docmanager plugin for business partner app validation checklist validate customers s/4hana and fiori versions for compatibility and support import docmanager related transports into development environment activate (if needed) sicf services for odata and plugin validate entries for fiori docmanager plugin definition and activation entries in sap fiori launchpad customizing identify and enable plugin to desired sap standard fiori apps support customers to complete ui adaptation on standard sap fiori apps to hide “attachment” tab launch and validate fiori docmanager plugin on all respective standard fiori apps technical considerations – hdm dependancies docmanager plugin works in absence of hdm functionality however if hdm is enabled below matrix will help clarify any limitation towards support for draft mode in fiori apps technical considerations – standard fiori apps only limitation with standard fiori apps would be with support for draft mode attachment feature as the plugin only supports sap standard fiori apps that are built using bopf framework that provides the ability to handle drafts learn more here https //experience sap com/fiori design web/draft handling/#top about sap draft handling concept and dependencies urls are well formed and provide required information like semantic object, action and object keys for the plugin to support effectively business objects that are single valued e g purchase order number or multi valued object keys e g purchase requisition item must be coded into url with appropriate key value pairing e g purchaserequisition='1000489',purchaserequisitionitem='00030', recommendation when customers leverage fiori docmanager plugin, we recommend to hide the standard "attachments" tab in sap fiori apps to ensure the users are not storing attachments using standard sap options "attachments" tab can be hidden using fiori " key user adaptation " as explained here click here technical considerations – custom fiori apps custom apps must have a valid semantic object and action associated with it custom apps must be associated to a bor business object (standard or custom) to associate with archivelink document types custom apps built using sap’s standard guidelines for handling draft will be able to take advantage of draft mode support in docmanager plugin ( learn more https //experience sap com/fiori design web/draft handling/#top about sap draft handling concept and dependencies ) custom apps built using non standard sap fiori floorplans need to be reviewed and tested on a case to case basis provided other points above meet the requirements to conclude, this page is updated from time to time and any discrepancies found please reach out to your customer success contact