Skip to Content

Shell Plugin for a SCP CF FLP Site

I have created and deployed a Shell Plugin (using an MTA app) for Fiori Launchpad on SCP Cloud Foundry. This MTA app has another UI module and other CAP modules as well.

When I access the approuter URL, the plugin loads successfully. This result should prove that there is nothing wrong with the code so far.

Now I created a new FLP site using the 'Portal' service. My aim is to load the Shell Plugin when this FLP site loads. To achieve this I went to 'Content Manager' of this site, created a new 'App' with Shell-plugin as Semantic Object-action. Assigned this app to a catalog and also to 'Everyone' role.

However, when I load the FLP site the plugin does not load. There are no errors either in the dev-tools. I did not find any documentation on how to configure a Shell Plugin to an FLP site.

The only documentation I found is here which is a scenario of the multi-tenant application.

Any help is appreciated.

Add a comment
10|10000 characters needed characters exceeded

  • FYI - I had to convert comments into answers and answers into comments in this question thread. Therefore you might have received some weird notifications.

    Please assure that you use the "comment" field if you have an additional question or want to leave a comment. If you want to provide an answer, use "Your answer" field.

    Thank you,

    Svea

Related questions

4 Answers

  • Best Answer
    Posted on Jul 24 at 08:03 AM

    So here is the answer if anyone is having the same question.

    SCP Portal Service provides two launchpads.

    • Local Fiori Launchpad: Only UI5 apps within the subaccount can be configured here.
    • Central Fiori Launchpad: External (to subaccount) UI5 apps can also be configured (via Content Provider concept)

    Central Fiori Launchpad

    If you are using a Central Fiori Launchpad (cFLP), i.e. by creating a FLP Site using the 'Site Manager' of the Portal service, the Shell Plugins are NOT yet supported. The advantage of cFLP is that it has a dedicated UI for managing the content (Apps, Catalogs, Groups), so that even non-developers can manage the content. Other significant advantage is that you can even subscribe to external content providers and configure those apps in the cFLP. (that is why called central ).

    But, if your shell plugin is coming from a different subaccount (not the subaccount where cFLP is hosted), then you can subscribe to that content provider and add the shell plugin to your cFLP site. IMO, this is useful only in a SaaS (multi-tenant) use case.

    Local Fiori Launchpad

    You can have a Local Fiori Launchpad on CF-SCP by having a 'Fiori Launchpad Site' module (can be part of your MTA app, or a separate dedicated MTA app) and deploying it to CF-SCP. Within this module, in CommonDataModel.json, you can configure the FLP content (only by a developer). A Shell plugin works well in this scenario. You can add other subaccount deployed UI5 apps, by adding corresponding html5-apps-repo service as service binding to the launchpad module (type com.sap.portal.content).

    Thanks to Jhodel (@jhodel18) for connecting and brainstorming.

    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 22 at 10:54 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 27 at 07:53 AM
    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Jul 26 at 04:33 AM
    -1
    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.