On the ABAP platform, plug-ins can be activated via user-role assignment. This allows
you to activate specific plug-ins only for specific user groups.
Prerequisites
The role-based plug-in activation only works with the dynamic page processing of the SAP Fiori
launchpad HTTP handler, which is registered on the ICF node
/sap/bc/ui2/flp). For more information, see SICF Services and Customize the Launchpad URL.
Procedure
- In the launchpad designer, in a catalog, create a target mapping with the intent
Shell-plugin and the following configuration:
Table 1:
Field
|
Value
|
Semantic Object
|
Shell
|
Action
|
plugin
|
Application Type
|
SAP UI5 Fiori App
|
Title
|
Enter a meaningful title for your plug-in.
|
URL
|
Enter the the root path to the location where the
Component.js file is located,
without the file name itself.
|
Component
|
Enter the name of the component which is used for loading
and instantiation. This is the name of the component's
module without .Component. For more details
on this, see Components.
|
Information
|
Optional: Enter a description of your plug-in.
|
Device Types
|
All device types must be selected.
|
Parameters
|
Define parameters that you want to pass to the plug-in component by entering a name and
a default value for each parameter.
|
Note
As target mappings with the intent Shell-plugin have
a special meaning, they do not appear in standard services such as the
TargetMappings feed,
resolveLink, or
getLinksForSemanticObjects. These target mappings
are only visible in the SAP Fiori launchpad designer.
- In Role Assignment (transaction
PFCG), assign the catalog to a
role.
- If you have not already done this, assign the role to the respective
users.