8. Debugging an App and adding Menu Path

Appgyver is a Low-code no-code platform with which you can build apps quickly.

You can refer to my bog Appgyver- Introduction where I tried to put some introduction and SAP’s acquisition of Appgyver.

In the previous blogs I have explained how you can get onboarded in Appgyver, what are the main constitutes of the Appgyver IDE – Composer Pro, We then created our first App in Appgyver, added some validation logic, then we worked on the data source and variable to build a working app. Also, we integrated the app with BTP by using an OData Service exposed from SAP BTP using Cloud Application Programming (CAP). After this we tried to incorporate some mobile native features in the app.

In this chapter we will discuss some essential features which is necessary in order to build productive apps.

Debugging

To build a complex production ready app, you may face issues where you need to go deep and find bugs. For this a debugger is necessary.

You can follow the standard tutorial to see how to launch the debugger

How to launch debugger

Few things to note here. When you launch the debugger you can see the variable values live.

Especially the data variable and page variable values are very important to look out for.

You can also track the events and even replay them

Also you can get more diagnostics from console log

Menu and Navigation to multipage apps

So far our app is only having a single page. If you noticed that there is a menu home icon which was attached already in the app.

Let’s add another page and add a navigation menu.

To do this click on the navigation tab

And update the Menu accordingly. First we want to update the menu text to ‘Home’ instead of ‘Empty Page’

Now add another page ‘Second Page’

Go back to navigation tab and add a menu path.

Let’s run the project.

Navigation

< Prev   |   Root   |   Next >