![]() Hence, I created an Adaptation project using the Web IDE. However, for further personalization, I chose to adapt the project. Now, we have the copy of standard app with customizations ready for use. So, I did the event binding using the “attachSelectionChange” method. Now, the challenge with Fiori Elements List report was that I did not find a way to find event handler for the event “onSelectionChange” declaratively. In order to show the exact number of entries selected by user, I had to somehow trigger the event handler for the table on Select all. Additionally, I made the info tool bar as sticky to ensure that message is displayed, when user scrolls the entries in the table. The object infoToolbar’s method insertContent shall be used to include the text to be shown to the users. The static id of the list report table can be pulled up from the Elements tab of the browser in which app is tested. The approach to include an information toolbar on the table was as follows: However, the intention was to display to users the number of entries selected for the operation. The info toolbar was not requested by the client. The parameters are passed using the parameters “key” and “descriptionKey”. So, on the separate fragments for value help, valuehelpdialog control is included with method handlers for “ok”, “cancel”, “afterClose”. Now, on click of the button the popup opens up.Īdditional to the popup, I made use of the ValueHelpDialog control inside the help fragment, to provide the standard help framework. Now that the fragment is created we shall invoke the fragment in the event – method handler using the fragment load method. In my project, I maintained fragments in a separate folder under ext folder. Prior to invoking a popup, we need to create fragments for the same. Once we have the custom button, the relevant event method is also available in the controller. ![]() It can used especially when the there is a need to update table records and ensure that changed data is immediately visible to users. ("") ĭetour: The extensionAPI is used to refresh the list report table. In my project, have synchronously loaded the modules “ExtensionAPI” and “ushell”. In continuing the same definition, to define the modules I made the use of. The generated custom controller is defined using sap.ui.controller. We will be using the same controller throughout the project to implement our customizations to the Fiori elements – List report app. In the process of creating the custom button, a controller is created by the wizard. To add a custom button to the table, we discussed the steps in the part 1 of the blog, by using the extension wizard on the project. In this blog, we will look into the points 6 to 11. Point 1 to 5 are covered in the Part 1 of the blog.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |