Showing posts with label fiori. Show all posts
Creating custom fiori app using SAP RAP

Creating custom fiori app using SAP RAP

Sanjo Thomas•19:44:00

SAP Fiori is a user interface that allows users to interact with SAP systems across different platforms and devices. It is a modern, responsive interface that offers a consistent user experience across different SAP applications. SAP Fiori is built using SAPUI5, a JavaScript-based framework that can be used to build custom Fiori apps.


SAP Rapid Application Development (RAP) is a framework that can be used to build scalable and extensible applications on top of SAP HANA. SAP RAP provides a set of tools and libraries that developers can use to build custom Fiori apps. In this blog we will discuss the steps to create custom SAP Fiori apps using SAP RAP.



Step 1: Define the business requirements

The first step in creating your own SAP Fiori application is to define your business requirements. This includes understanding the business processes that the application will support, the data that will be used, and the user roles that will interact with the application. This information will help define the scope of the application and the features it should contain.


Step 2: Design the app

Once the business requirements are defined, the next step is to design the application. This includes creating wireframes or mockups that illustrate the app's user interface and functionality. The design should be intuitive and easy to use, taking into account user needs and business requirements.


Step 3: Set up the development environment

In order to create your own SAP Fiori apps using SAP RAP, you will need to set up a development environment. This includes installing the necessary software and tools such as SAP Cloud Platform, SAP Web IDE and SAP HANA Studio. You will also need to create a development project and configure the necessary settings.


Step 4: Define the data model

The next step is to define the data model. This includes creating the necessary entities and relationships that will be used to represent the data in the application. The data model should be designed to support business processes and requirements and should be optimized for performance and scalability.


Step 5: Implement the business logic

Once the data model is defined, the next step is to implement the business logic. This includes defining the rules and workflows that will be used to process data and support business processes. Business logic should be designed to be flexible and extensible to adapt to changing business requirements.


Step 6: Implement the user interface

The next step is to implement the user interface. This includes creating the necessary views and controls that will be used to display data and allow users to interact with the application. The user interface should be designed to be intuitive and easy to use, taking into account user needs and business requirements.


Step 7: Test and deploy the application

After creating the application, the last step is to test and deploy it. This includes testing the application to ensure it meets business requirements and is free of bugs and errors. Once the application is tested, it can be deployed to a production environment and made available to users.


In conclusion, building custom SAP Fiori applications using SAP RAP involves several steps, including defining business requirements, designing the application, setting up the development environment, defining the data model, implementing the business logic, implementing the user interface, and testing and deploying. application. Following these steps, developers can create custom Fiori apps that support their organization's business processes and requirements.

Read more
Configure Catalog and Groups in SAP Fiori Portal Sites

Configure Catalog and Groups in SAP Fiori Portal Sites

Sanjo Thomas•08:56:00


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.
Read more