Skip to Content
Product Information

Simplifying application generation for SAPUI5 freestyle and SAP Fiori elements apps

With the latest release of SAP Fiori tools, we now have a single project generator that supports both SAP Fiori elements and SAPUI5 freestyle applications. This marks the beginning of our journey to harmonize the development experience between SAP Fiori elements and SAPUI5 freestyle. Developers can now use:

  • a project generator that can create either type of application using SAP Fiori tools and support adding deployment configuration
  • the popular preview feature that was previously only available for SAP Fiori elements
  • the same process and commands for all SAP Fiori applications regardless of whether you are deploying an SAP Fiori elements app or SAPUI5 freestyle applications

 

 

There is now a single tile in our project generator for both SAP Fiori elements and SAPUI5 freestyle apps.

 

Our vision is to harmonize the development experience with one common approach and set of tooling for building SAP Fiori apps. Our first step was to simplify the selection of SAP Fiori elements floorplans in the project generator to provide a similar development experience regardless of whether you are developing an OData V2 or OData V4 application (more on SAP Fiori elements support for OData V4).

 

SAP Fiori tools is available in SAP Business Application Studio and Visual Studio Code. The expanded support for SAPUI5 applications will roll out in a phased approach. The new application generator is available today. The existing project generator for in SAP Business Application Studio will be deprecated. Click here for more information on using SAP Fiori tools.

 

We are also taking another step forward to with the migration command supporting both type of applications.

This is the command to migrate your project.

 

Outlook*

We plan to deliver additional functionality in SAP Fiori tools, focusing on

  • Wizard to create view and controller
  • Previewing applications with remote reuse library reference
  • Project validator

 

Check the SAP Fiori roadmap section ‘SAP Fiori elements and SAP Fiori tools’ for more details.

 

* Kindly note that this is the current state of planning and can be changed by SAP at any time without further notice.

 

For SAP UX Engineering, Ashley Tung

8 Comments
You must be Logged on to comment or reply to a post.
    • Hi Jeroen,

      A ui5-deploy.yaml file should be created under the generated project folder. Insider the ui5-deploy.yaml file, there is a customTask 'deploy-to-abap'. The deploy config information such as client, package, and transport are listed under this custom task.

      • So the deploy works fine. I wonder though why there is an archive.zip file in the root of my project files. Shouldn't that be in the /dist folder? Currently, I have added this to the .gitignore list because I don't think it should be synced with the repository.

        • Hi Jeroen,

          After running npm run build, the dist folder is created.

          And when triggering npm run deploy, the underlying execution actually triggers the deploy command provided by @ui5/cli. It archives the dist folder archive.zip file and uploads it to ABAP backend. The dist folder is also deleted by ui5 cli. 

          It seems we missed archive.zip in the generated .gitignore file. Thanks for letting us know. I have reported this to our PO.

  • I also notice that BAS does not seem to have a validation scheme for ui5-deploy.yaml (it has red markings in several places). I know it works because I've tested the deploying. Perhaps you could fix this, so developers don't get worried :).