Using Controller Extensions

In your Display Customers app, you may want to notify the user if there are any bookings with the status New. To do this, you will display the corresponding message above the Own Bookings table on the object page.

In the previous exercise, you have already created a custom section and added the Table building block to it. Now, you will add a message strip to the table. You will also see an option to add a message to the whole object page.

The table displaying the customer's bookings uses paging to restrict the data exchange load: only the first ten lines are loaded. This means you cannot analyze all the bookings on the UI side; this should be done in the back end instead. To do this, you will create a function import in the back end.

You will first add a controller extension to your customer app using the Page Map.

Next, you will extend your CAP service with a new function. It will check the back end for any bookings with the status New for the selected customer.

After that, you will be able to call this function in your front end using the controller extension. If there are any bookings with the status 'new', a message strip will be shown above the table, displaying a warning.

Finally, you will add an information message to the whole object page, in case there are any bookings with the status New.

This exercise contains a simulation displaying all the steps. You can follow the simulation with your own trial account.

ExerciseStart Exercise

1. Add a controller extension to your app.

   1. Open the object page of the Display Customers app and switch to SAP Business Application Studio.

   2. Open the webapp folder and select Show Page Map>Object Page>Add Controller Extension.

   3. Add PassengerOPExtend as the controller name.

   4. You have now added a new controller extension.

2. Extend your CAP service with a new function.

   1. Open schema.cds and paste the following code snippet into the file:

      Code snippet

      Copy code

      type BookingData: {
        HasNewBookings: Boolean
      }

      Expand

      This adds a new type BookingData in your data model.

   2. Open travel-service.cds and add the following function definition to it:

      Code snippet

      Copy code

      // Function import used in Controller Extension 'PassengerOPExtend.js' to calculate booking data
      function getBookingDataOfPassenger(CustomerID: String) returns my.BookingData;

      Expand

      This adds a new function getBookingDataOfPassenger.

   3. Open travel-service.js and add the following code snippet:

      Code snippet

      Copy code

       /**
         * Function import handler: getBookingDataOfPassenger
         * @param CustomerID
         * @returns BookingData
         */
        this.on('getBookingDataOfPassenger', async (req) => {
          const { CustomerID } = req.data
          const allCustomerBookings = await SELECT `BookingStatus_code as status`.from (Booking) .where `to_Customer_CustomerID = ${CustomerID}`
          const bookingData = {
            HasNewBookings: false
          }
          bookingData.HasNewBookings = allCustomerBookings.some((booking) => {
            return booking.status === 'N';
          })
          return bookingData
        });

      Expand

      You have added the implementation of the getBookingDataOfPassenger function.

      It takes CustomerID as a parameter and checks the data base for bookings with the status New per Customer.

3. Add a function to the controller extension.

   1. Open the controller extension file PassengerOPExtend.controller.js and add the following code snippet:

      Code snippet

      Copy code

      
      sap.ui.define(['sap/ui/core/mvc/ControllerExtension',"sap/ui/core/message/Message","sap/ui/core/MessageType",
      ], function (ControllerExtension, Message, MessageType) {
      'use strict';
      
      
      return ControllerExtension.extend('sap.fe.cap.customer.ext.controller.PassengerOPExtend', {
      // this section allows to extend lifecycle hooks or hooks provided by Fiori elements
        override: {
        /**
        * Called when a controller is instantiated and its View controls (if available) are already created.
        * Can be used to modify the View before it is displayed, to bind event handlers and do other one-time       initialization.
        * @memberOf sap.fe.cap.customer.ext.controller.PassengerOPExtend
        */
          onInit: function () {
          // you can access the Fiori elements extensionAPI via this.base.getExtensionAPI
            var oModel = this.base.getExtensionAPI().getModel();
          },
          routing: {
            onAfterBinding: async function (oBindingContext) {
             
            } 
          }
        }
        });
      });

      Expand

      You have added the onAfterBinding function of the routing object (class sap.fe.core.controllerControllerextensions.Routing).

   2. Add the following code snippet to the onAfterBinding function:

      Code snippet

      Copy code

       onAfterBinding: async function (oBindingContext) {
              const
              oExtensionAPI = this.base.getExtensionAPI(),
              oModel = oExtensionAPI.getModel(),
              sFunctionName = "getBookingDataOfPassenger",
              oFunction = oModel.bindContext(`/${sFunctionName}(...)`),
              oBookingTableAPI = oExtensionAPI.byId("fe::CustomSubSection::Bookings--OwnBookingsTable"),
              oWarningMessage = new Message({
                type: MessageType.Warning,
                message: await oExtensionAPI.getModel("i18n").getResourceBundle().getText("bookingsNew")
              }),
                oInfoMessage = new Message({
                  type: MessageType.Info,
                  message: await oExtensionAPI.getModel("i18n").getResourceBundle().getText("bookingsAttention")
                });
                // Request OData function with current CustomerID
                const oCustomer = await oBindingContext.requestObject(oBindingContext.getPath());
                oFunction.setParameter("CustomerID", oCustomer.CustomerID);
                await oFunction.execute();
                const oContext = oFunction.getBoundContext();
                if (this.message !== undefined) {
                  oBookingTableAPI.removeMessage(this.message);
                } 
                if (oContext.getProperty("HasNewBookings")) {
                  this.message = oBookingTableAPI.addMessage(oWarningMessage);
                  oExtensionAPI.showMessages([oInfoMessage]);
                }
              }
      

      Expand

      You have added some code to onAfterBinding. With this code, you have accessed the back-end function getBookingDataOfPassenger in the SAPUI5 OData V4 Model, got the table API of the table building block, and created a warning message.

      You have also created a message of type Info. If the HasNewBookings parameter of the back-end function is true, the info message is added to the whole object page using the object page controller's extensionAPI.

   3. Open the i18n file in the file explorer and add the following code snippet:

      Code snippet

      Copy code

      #XMSG: Warning message on object page
      bookingsNew=There are new bookings that have not yet been accepted.
      
      #XMSG: Info message on object page
      bookingsAttention=Some bookings require your attention

      Expand

      You have just added the warning and the information message texts to the i18n.properties file.

   4. Switch to the app window. You can see the warning message for Theresia Buccholm's bookings as some of these have the New status. You can also see an info message in the object page header.