Sample Overview

/wp-content/uploads/2015/06/clipboard1_716632.png

Key points

1. in Component.js, the following line is mandatory:

/wp-content/uploads/2015/06/clipboard2_716642.png

It is used to ensure all the source code of standard My Opportunity application are loaded with the path passed via fregisterModulePath method and stored in folder with structure as below ( Observed in Chrome development tool )

/wp-content/uploads/2015/06/clipboard3_716643.png

2. in the source code automatically generated via WebIDE wizard, the standard Opportunity component is loaded with code below,

via function sap.ui.component.load:

/wp-content/uploads/2015/06/clipboard4_716644.png


Through my testing, I find it is not necessary, so I just comment it out ( red part ) as below, and use jQuery.sap.require to load the standard component instead ( green part ).

/wp-content/uploads/2015/06/clipboard5_716645.png

3. The hidden of “Participants” tab is achieved via viewModifications as displayed below:

/wp-content/uploads/2015/06/clipboard6_716646.png

The id “salesTeam” could be found in S3.view.xml of Opportunity project:

/wp-content/uploads/2015/06/clipboard7_716647.png

4. If you deploy the extension project to ABAP repository and configure it as Fiori launchpad tile, the index.html is not needed when you access your extension project via launchpad. However if you would like to test your extension project locally in WebIDE by selecting

“index.html” and click Run button in toolbar, then line 30 below is mandatory. It has the same purpose as the line mentioned in keypoint #one.

/wp-content/uploads/2015/06/clipboard8_716648.png

How to ensure your view modification take effect

Enter you extension project, now you could not see Participants tab in UI, and you could also observe the corresponding log in Chrome console.

/wp-content/uploads/2015/06/clipboard9_716650.png

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply