In the previous blog we looked at how to configure an app
using the Fiori configuration cockpit, in this blog we are going to focus on
how to configure catalogs and groups and assign an app to them.
Let's start by looking at a typical workflow of an administrator
creating portal contents for different roles within the organization.
Let’s understand it with the help of an example; I have
picked the roles of a sales manager and sales staff.
1)
Create
Catalogs - The first step would be creating the relevant catalogs – one for
the manager and the other for the staff. The next step would be configuring the
required apps. Let’s say, a staff member would need access to Leave Request app
and a manager would require access to a Leave Request as well as a Leave Approval
app.
2)
Configure
apps and assigning them to Catalog - Once the contents are developed and
ready, an administrator would configure these apps using the Fiori
configuration cockpit and assign these apps to the respective catalogs. The
catalog for the sales manager will have both the apps whereas the catalog for
the sales staff would have only the Leave Request app.
3)
Create
groups - This would follow with the creation of the necessary groups for
each of these roles and the assignment of tiles to these groups.
4)
Assign
Roles to catalog/groups - Once the groups and catalogs have been created
for the sales staff and sales manager, the necessary Cloud Platform roles are
created and assigned to the respective catalogs and groups.
5)
Assign
roles directly to users or groups
- The last step is assignment of the roles to the end users – in this case,
they are sales staff and sales manager.
In the initial blog, where I wrote about how to activate the
portal service in cloud platform, the user which was used to activate the
service would have been automatically assigned the standard role TENANT_ADMIN. This role provides
administrative privileges to a portal administrator. This is a general portal
concept and needs to be followed whether you are an administrator creating a Fiori
launchpad-based site or a freestyle site. If you would like to assign these
privileges to a few other administrators, you would need to add the
TENANT_ADMIN role to their user IDs.
Administrators also have an option to create custom roles,
which can be used within the Fiori configuration cockpit for assignments to
catalogs and groups. Roles can be assigned directly to individual users or to
federated assignments using SAP Cloud Platform groups.
Let’s see all these steps practically.
In the previous blog, we saw how to configure an app in the
“Apps” menu, if you haven’t read my previous blog, please read “How to
configure apps in Fiori Launchpad portal site”.
“es4products” was the app that we had configured in the
previous blog, so let’s start from here.
Now, we need to create a catalog, so click on catalogs,
navigate to the plus icon “+” at the bottom of the master screen and create a
catalog.
Give a proper Catalog Name and Description
And the next tab here is "Apps", so this is where
you go and assign apps to the catalog. Click on the “+” icon and assign
es4products apps to the catalog.
And then the third tab here is "Roles". So again,
you have an option to add the roles which are already available for the Fiori
launchpad site. By default, every Fiori launchpad site has got an
"Anonymous" (any user who's not authenticated can go and access the
contents) and an "Everyone" role (it means all users who are
authenticated get access to those contents.).
Now you can save it, so with this, the catalog has been
created and an app has been assigned to the catalog, now next step is to create
a group.
Click on the groups button and click on the "+"
icon here to create a group here, and give an appropriate name, so let's give
it as "Sales".
Similar to Catalogs, we need to assign the app and roles
here.
Then, we have the roles, here we have defined the “Everyone”
roles to the catalog and the groups. So here we can see all the catalog and
group assign to the “Everyone” role.
Now with this, our basic building blocks have been created
and now we are ready to publish the site. So to publish a site, we would just
use this icon at the top, which will publish the site, and I can just tell it
to open it as well.
So here we go, our app is now published to the Fiori
launchpad portal site.
That’s it for this tutorial blog, stay tuned for more blogs.
This is dummy text. It is not meant to be read. Accordingly, it is difficult to figure out when to end it. But then, this is dummy text. It is not meant to be read. Period.
ConversionConversion EmoticonEmoticon