SAP Fiori Elements using CAP Model – Introduction
In the past weeks, I’ve been working on a demo project about SAP Fiori Element using CAP Model. It all started when I was exploring the capabilities of the new SAP Fiori Tools to help aid in SAP Fiori Element app development. Then I realized that there are not that many references of SAP Fiori Element app that uses CAP Model — I guess this is not surprising as CAP is relatively a new programming model. So I decided to come up with a comprehensive example that showcases a real-world scenario.
The demo project is patterned after the SAP Tutorial — Create a List Report Object Page App with SAP Fiori Tools, but using the North Wind Service data model. I enjoyed developing this demo app, and I must say, the CAP framework exceeded my expectations. I hope you will find this demo project useful.
As a teaser, here’s the screenshot of the List Report page:
Blog Post Series
- SAP Fiori Element using CAP Model – Introduction
- SAP Fiori Element using CAP Model – List Report App
The Goal: No-Code Challenge
Let’s get into a more detailed explanation by first discussing SAP Fiori Elements. In the official documentation of SAP Fiori Elements extension, it is mentioned there that only use app extensions if the desired behavior cannot be produced by annotations and setting the manifest file. So for this reason, I avoided getting into app extensions.
Here’s the screenshot of the Object Page:
The Demo Project
The demo project is a mono repo that hosts both the SAP Fiori Element List Report app (generated by SAP Fiori Tools) and CAP-based backend service.
The repository can be accessed through the GitHub repository below:
Please refer to the README.md file on how to install and test the app.
Here’s the screenshot of the Object Page showing the Monthly Revenue Bar Chart:
Inspired by the Devtoberfest 2020 event, I have turned this demo project as an opensource demo project where anybody is welcome to contribute for any scenario or behavior that is still not catered.
It can be a contribution that is riding along with the no-code challenge or expanding in other areas like Fiori Element API Extension scenarios together with CAP Model backend service.
Try it yourself and I hope you will have fun building your own app (like I did!) using these frameworks.
The fun doesn’t stop here. In fact, we are just getting started. In my next blog post, I will try to decompose the project into smaller pieces so that it will be easy for consumers who are new to Fiori Element or CAP Model (or both) to understand and replicate the behavior used in the app. So stay tuned!
Appreciate it if you have any comments, suggestions, or questions. Cheers!~