Create a User Interface with CAP (SAP HANA Cloud)

1. From the previous tutorial we have a .env file in the /db folder. This file contains the connection details to the SAP HANA Cloud instance and it was created when we performed the bind operation from the SAP HANA Projects view.

   

2. We can use this same configuration information from Cloud Foundry to start the CAP service layer and connect it to SAP HANA as well. Use the command cds bind -2 MyHANAApp-dev:SharedDevKey to tell CAP to bind to this same HANA Cloud HDI service instance that we bound to earlier in the SAP HANA Projects view.

   

3. Run the command npm install to install any Node.js dependent modules needed by the Cloud Application Programming Model.

   

4. Our project is setup for real XSUAA security and we will use that later in this tutorial. But for now we want to test without configuration of the necessary authentication and authorization setup. To do so, open the package.json file in the root of your project. Change the cds.requires.auth property from xsuaa to mocked so we can test with mock authentication.

   

5. Now issue the command cds watch --profile hybrid. This will start the CAP service locally and use the binding configuration to connect to our remote HANA database instance. Once started you will see a dialog with a button that says Open in New Tab. Press this button to test the CAP service in a new browser tab.

   

   If you accidentally close this dialog, you can always open the running services via View > Command Pallette and then choosing Ports: Preview and choosing the running service from the list

6. You should see the list of entities you exposed.

   

7. You can click on the entities to see the values in a JSON format being served from the SAP HANA Cloud database.

   

1. Choose the $metadata option from the Welcome page and you can see a technical description of the service

   

2. You can use different methods in the OData v4 services you have created. Go back to the welcome page for the service and click Interactions_Items. Different versions of the Cloud Application Programming Model preview page do different things at this point. Some add a $top limit to the generated URL for `Interactions_Items` automatically. Other and perhaps newer versions do not. Have a look at the end of the URL when it opens. If it ends in `?$top=11` then add the following to the URL:

   URL Copy

   &$search=DE

   Otherwise add the following to the URL:

   URL Copy

   ?$search=DE

   

3. You can find out more about OData V4 at the OData organization and the documentation for SAPUI5.

You will use an Application Router module. This was generated into a project using the initial wizard. This module is very important as it will become the entry point for your application. Every request coming to this module will be routed into the different backend services.

1. You should see a folder named app/router in the root of your project.

   

2. Since the web module will be receiving the requests and routing them into the proper processing backend services, such as the OData service you have just tested, it will also be responsible for enforcing authentication.

   These routing logic is done by an application called approuter. You can see the Node.js module being called as the starting script for the web module as defined in the file package.json.

   

3. We need to install the approuter dependency now as well. From the terminal change to the app/router folder and issue the command npm install

   

4. The approuter will scan the file xs-app.json to route patterns in the request to the right destinations. The xs-app.json that was generated by the wizard is ready to use real security settings, but our project isn’t that far along yet. Therefore, let’s change the configuration to temporarily disable the security checks.

   Replace the content of xs-app.json with the following content

   JSON Copy

   {
   "authenticationMethod": "none",
   "routes": [
       {
       "source": "^/app/(.*)$",
       "target": "$1",
       "localDir": ".",
       "cacheControl": "no-cache, no-store, must-revalidate"
       },
       {
       "source": "^/appconfig/",
       "localDir": ".",
       "cacheControl": "no-cache, no-store, must-revalidate"
       },
       {
       "source": "^/(.*)$",
       "target": "$1",
       "destination": "srv-api",
       "csrfProtection": true
       }
   ]
   }

   

5. Among other information, this configuration is declaring that requests containing the pattern ^/(.*)$ are routed to a destination called srv-api. This destination was defined by the wizard in the mta.yaml file and points the service layer of our CAP application.

We want to create a Fiori UI for our CAP service. We will use the wizards to generate most of the UI.

1. From the top menu select View -> Command Pallette. Then type fiori into the search box. Select Fiori Open Application Generator.

   

2. Select Worklist Page as the template and press Next

   

3. At the Data Source and Service Selection screen, choose Use a Local CAP Project. Select your project as the Choose your CAP project. Select CatalogService (Node.js) as your OData service. Press Next

   

4. Choose Interactions_Header as the main entity, ITEMS for the Navigation entity, leave the YES value for the “Automatically add table columns to the list page and a section to the object page if none already exists?” option and press Next

   

5. In the Project Attributes screen, match to the values shown in the following screenshot and press Finish

   

6. The new project structure and content should look like This

   

7. From the terminal you should still have your cds watch --profile hybrid still running (if not restart it). This command watches for changes so your application is already to test with the new UI. Open the browser tab where you were testing it previously.

8. The CAP test page now has a link to the newly generated application.

   

9. Clicking that link will launch the generated Fiori UI for the CAP service.

   

10. If you wish you can open another terminal instance and change to the Application Router folder (cd app/router/). Then run the command npm start. This will run the Application Router which you can test from its own port (5000). Nothing will really look different at this point, but you are passing all requests through the Application Router now. This will become important once we add security to our service and want to test it locally using the Application Router.

1. The Fiori application template wizard already created an annotations.cds file with some basic annotation entries for your application. This is how the preview that we used in the last step already had partner and country_code fields in the output.

   

2. Let’s now extend the wizard generated annotations to include more fields in our application. With a few lines of annotations we can reshape the entire UI.

3. Replace the annotations.cds with the following content:

   CDS Copy

   using CatalogService as service from '../../srv/interaction_srv';
   
   annotate service.Interactions_Header with @(
   UI.HeaderInfo                : {
       Title         : {
           $Type: 'UI.DataField',
           Value: partner,
       },
       TypeName      : 'Incident',
       TypeNamePlural: 'Incidens',
       Description   : {Value: country.descr}
   },
   UI.HeaderFacets            : [{
           $Type             : 'UI.ReferenceFacet',
           Target            : '@UI.FieldGroup#Admin'
   }],
   UI.FieldGroup #GeneratedGroup: {
       $Type: 'UI.FieldGroupType',
       Data : [
           {
               $Type: 'UI.DataField',
               Label: 'Partner',
               Value: partner,
           },
           {
               $Type: 'UI.DataField',
               Label: 'Country',
               Value: country_code,
           },
           {
               $Type                  : 'UI.DataField',
               Label                  : 'Country',
               ![@Common.FieldControl]: #ReadOnly,
               Value                  : country.descr,
           },
       ]
   },
   UI.FieldGroup #Admin       : {Data : [
       {
           $Type : 'UI.DataField',
           Value : createdBy
       },
       {
           $Type : 'UI.DataField',
           Value : modifiedBy
       },
       {
           $Type : 'UI.DataField',
           Value : createdAt
       },
       {
           $Type : 'UI.DataField',
           Value : modifiedAt
       }
       ]
   },
   UI.Facets                    : [
       {
           $Type : 'UI.ReferenceFacet',
           ID    : 'GeneratedFacet1',
           Label : 'General Information',
           Target: '@UI.FieldGroup#GeneratedGroup',
       },
       {
           $Type : 'UI.ReferenceFacet',
           Label : 'Interaction Items',
           Target: 'items/@UI.LineItem'
       }
   ],
   UI.LineItem                  : [
       {
           $Type: 'UI.DataField',
           Label: 'Partner',
           Value: partner,
       },
       {
           $Type                  : 'UI.DataField',
           Label                  : 'Country',
           ![@Common.FieldControl]: #ReadOnly,
           Value                  : country.name,
       },
   ]
   );
   
   annotate service.Interactions_Items with @(
   UI.HeaderInfo                : {
       Title         : {
           $Type: 'UI.DataField',
           Value: text,
       },
       TypeName      : 'Interaction Item',
       TypeNamePlural: 'Interaction Items'
   },
   UI.FieldGroup #GeneratedGroup: {
       $Type: 'UI.FieldGroupType',
       Data : [
           {
               $Type: 'UI.DataField',
               Label: 'Text',
               Value: text,
           },
           {
               $Type: 'UI.DataField',
               Label: 'Date',
               Value: date,
           },
           {
               $Type: 'UI.DataField',
               Label: 'Price',
               Value: price,
           },
           {
               $Type: 'UI.DataField',
               Label: 'Currency',
               Value: currency_code,
           }
       ]
   },
   UI.Facets                    : [
       {
           $Type : 'UI.ReferenceFacet',
           ID    : 'GeneratedFacet1',
           Label : 'General Information',
           Target: '@UI.FieldGroup#GeneratedGroup',
       },
       {
           $Type : 'UI.ReferenceFacet',
           Label : 'Item Translations',
           Target: 'texts/@UI.LineItem'
       }
   ],
   UI.LineItem                  : [
       {
           $Type: 'UI.DataField',
           Label: 'Text',
           Value: text,
       },
       {
           $Type: 'UI.DataField',
           Label: 'Date',
           Value: date,
       },
       {
           $Type: 'UI.DataField',
           Label: 'Price',
           Value: price,
       },
       {
           $Type: 'UI.DataField',
           Label: 'Currency',
           Value: currency_code,
       }
   ]
   );
   
   annotate service.Interactions_Items.texts with @(UI: {
   Identification : [{Value: text}],
   SelectionFields: [
       locale,
       text
   ],
   LineItem       : [
       {
           Value: locale,
           Label: 'Locale'
       },
       {Value: text}
   ]
   });
   
   annotate service.Interactions_Items.texts with {
   ID @UI.Hidden;
   };
   
   // Add Value Help for Locales
   annotate service.Interactions_Items.texts {
   locale @(
       ValueList.entity: 'Languages',
       Common.ValueListWithFixedValues,
   )
   }

   Show all 181 lines Show less

4. Run the application again and you will new functionality including value help for country and currency as well as the ability to see and maintain the translatable text element.

   

Congratulations! You have created your first, full application.

Now it is a good time to commit your application into the local or remote Git.