020: Recycling-Heroes - Launchpad Integration (Contact)

Table of contents

• Introduction
• IAM App
• Business Catalog
• Business Role
• Space
• Page
• Display
• Summary

Introduction

In the last video, we deployed the application to the system and made it available. However, we still can't access it in the Launchpad and therefore can't assign a user. Therefore, in this episode, we'll look at how to make the assignment, define pages and spaces, and make the application available to the user.

 

IAM App

After deployment, we now have the BSP application and the Launchpad App Descriptor Item available, which we now need for further installation. In the first step, we define an IAM app. This is an additional artifact that we need for authorization. We assign the app a name, a description, and a type. Since this is an external Fiori application, we select the "External App" type.

After creating it, we assign the Launchpad configuration. This contains the application configuration and the navigation configuration for the Launchpad. If you don't know this entry by heart, you can call Content Assist using CTRL + 1. In addition to the Launchpad configuration, the object also authorizes the service required for execution, and additional authorization objects can be assigned.

Finally, we save the object; activation is not necessary here. To make the application and configuration available in the Launchpad, you must run "Publish Locally." This can take some time.

 

Business Catalog

Once we've completed this step, we can't yet authorize the IAM app; instead, we need a Business Catalog. This bundles various apps into a package, and later we can combine various Business Catalogs into a role for the user.

In this example, we can create a new Business Catalog directly from the IAM app and assign the app to it. To do this, click on the corresponding link in the object to start creating the catalog. Here, we need a name and a description. We usually use a BC at the beginning of the name to distinguish between the business catalogs. Once we've created the object, we still need to define the assignment. Basically, all the relevant information is pre-filled, and we only need to define the package. Once the two objects have been created, we can make the assignment directly, as we won't need it any further. In the business catalog, we now also click "Publish Locally" so that the catalog is available in the Launchpad. This may take a while.

Once the catalog is published, we check the Apps tab. Our app has now been assigned to the catalog via the assignment. If a user receives the catalog, they can use the specified apps and other objects.

 

Business Role

We cannot assign a business catalog directly to a user; instead, we always need a business role. To do this, we go to the "Maintain Business Roles" tile in the system's launchpad and check whether there are already roles with ZRH. We create a new role with a description using the "New" button. The business role ID can be changed at any time later if you need to adjust it. In the first step, we create a role for the admin. This role can run all applications with all permissions, which is enough for us to start with.

In the Business Catalogs section, we now assign our catalog to the role. We start the search using "Add" and can also restrict the search to the catalog name. We can assign the catalog with "Apply" and then continue working in the pop-up window. With "OK" the catalog is added and editing is completed. We can then switch directly to Business Users and enter our own user so that it receive permissions for the new role. Finally, we need to switch to "General Role Details" and set "Write, Read" to "Unrestricted". so that the role also receives the necessary change permissions. This is especially necessary later, when we work with permissions and boundaries. Finally, we can create and assign the role with "Save."

To test the new permissions, we first need to log out of the system and log back in again so that the new permissions take effect. To integrate the app into our homepage, we switch to the App Finder via the menu. There we can search for the new application and add the application where we need it using the plus symbol. Finally, we call up the application and immediately see the data.

 

Space

To prevent users from always having to search for the application using the App Finder, we want to set up a corresponding space directly for them. To do this, we switch to the "Manage Launchpad Spaces" application. There, we can create a new space in the system using the "Create" button. The ID is not necessarily relevant for the display; the title is especially important later. To keep things simple, we'll leave the title and description the same and add a little more to the description. For the transport, we need a customizing transport. If you don't have one yet, you'll need to switch applications again to create one in the system.

Since we don't have a page yet, we'll check the box here to define a page along with the space. The applications will be assigned to the pages later and displayed in groups accordingly. The page title will be relevant later, when we have assigned more than one page to a space. We create the two objects using "Create."

To assign our application right away, we'll add the new space to our business role. To do this, switch applications again and go to the role's edit mode using "Edit." We can now switch to the "Launchpad Spaces" tab and add our new space. To do this, we'll switch from "Use Space Template" to "Use Space" in the popup, since we defined our space manually in the Launchpad. We can then search for our space in the list and select it. Don't forget to save the changes so that they take effect.

 

Page

To edit the page, we open the "Manage Launchpad Pages" application and go to our new page ZRH_CORE. We can edit the page using "Edit." Let's give our new space a name, which will then appear as the heading on the page.

Since we've already assigned the space to a role, we'll receive suggestions for applications from the corresponding roles, which we can now assign. This ensures that we only include applications that are included in the assigned roles. Using "Add," we can define the size of the tile added to the space. Using "Save," we'll save the new tile. We save the current state of the page and are done with it for now.

 

Display

To see the new space, we need to log out and log back in so that the changes, structures, and permissions take effect. If the space is not yet visible, we can add it via the menu. To do this, go to "All Spaces" and search for our space and pin it again.

Our application should now be visible in the space. We can now start this as well and are thus finished integrating it into the Launchpad.

 

Summary

In this episode, we looked at how to package the application into an IAM app and assign it to a business catalog. We then assigned this to a role and defined a space and a page for it. Finally, every user with this role receives the appropriate permissions and should receive the space as standard access.

This brings us to the end of this episode. Thank you for watching, and see you next time.

 

YouTube
Video