Extensibility information for SAP Fiori app.
You can extend the app according to your business needs for different aspects. For this purpose, the following extensibility options are available:
To preferred communication method to the contact details, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs:
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include |
Run Time: Superclass and Method to Be Redefined |
ContactDetails.view.xml |
extContactDetailsInfo |
CRM_BUPA_ODATA |
CRMT_BP_ODATA_ADDRESS_INCL |
Superclass: CL_CRM_BP_ODATA_RT_ADDRESS Method: READ_ADDRESSES_FOR_PARTNER |
To <add a customer field to the app, for example>, the following extensibility entities are available on the different layers. You have to extend each of these entities according to your specific business needs:
UI |
Back End/ABAP |
|||
---|---|---|---|---|
View |
Extension Point |
Design Time: Gateway Entity |
Design Time: Extension Include |
Run Time: Superclass and Method to Be Redefined |
<Name of view> |
<Name of extension point> |
<Name of entity, such as Gateway service> |
<Name of extension include> |
Superclass: <Name of superclass> Method: <Name of method> |
Business Add-Ins (BAdIs)
The following Business Add-Ins are available for extensibility purposes:
<BAdI Name 1> (<Technical name>)
You can use this BAdI to...
Extension Includes
In addition to the extension includes described above, the following extension includes are available:
DDIC |
Extension Include |
Use |
---|---|---|
|
<Extension include> |
|
For more information about extension includes, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation .
Extension Points
Extension points that contain specific objects
These extension points allow you to remove or replace an object, e.g. if you want to change the sequence of the object’s default attributes, or add a custom attribute in any place except the very end of the object’s default attributes.
These extension points allow you to add custom attributes at the end of the object’s default attributes
The following extension points are available:
View |
Extension Point |
Use |
---|---|---|
S2.view.xml (overview screen showing list of contacts) |
extListItem |
Allows you to remove or replace the list items in total. |
extListItemInfo |
Allows you to add custom attributes to the list items. |
|
S3.view.xml (contact details screen) |
extContact |
Allows you to remove or replace the header data in total, with the exception of the contact’s name and photo. |
extContactInfo |
Allows you to add custom attributes to the header data. |
|
extContactDetailsTab |
Allows you to remove or replace the information tab in total. |
|
extContactInfoTab |
Allows you to remove or replace the information tab in total. |
|
ContactDetails.view.xml (information tab that is part of the contact details screen) |
extContactDetailsInfo |
Allows you to add custom attributes to the information tab. |
S4.view.xml (edit/create contact screen) |
extContactPicture |
Allows you to remove or replace the photo area in total. |
extContactDataInfo |
Allows you to add custom attributes to the contact’s data. |
If there are additional fields available in the OData service, you can display these fields on the UI. For more information, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation .
UI Controller Hooks
To plug in and execute custom code, the following hooks are available in the controller code:
Controller |
Hook |
Use |
---|---|---|
S4.controller.js |
getCustomProperties in method handleSave |
Allows you to enhance the creationModel model with custom attributes. |
modificationsCheckCustomFields in method modificationsCheck | ||
setCustomProperties in method updateModel |
||
cleanCustomProperties in method cleanModel |
If there are additional UI controller hooks available in the controller code, you can add own code. For more information, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation .
Display of UI Controls
As an example, the following UI controls can be hidden from the app UI:
View |
Control ID |
Use |
---|---|---|
S3.view.xml (contact details screen) |
function |
Allows you to hide the function. |
department |
Allows you to hide the department. |
|
Attachments |
Allows you to hide the attachments tab. |
|
Notes |
Allows you to hide the notes tab. |
|
ContactDetails.view.xml (information tab that is part of the contact details screen) |
mobilePhoneLabel, mobilePhoneInput |
Allows you to hide the mobile phone number. |
phoneLabel, phoneInput |
Allows you to hide the phone number. |
|
emailLabel, emailInput |
Allows you to hide the email address. |
|
addressLabel, addressInput |
Allows you to hide the address. |
|
emptyLabel, emptyInput |
Allows you to hide the empty line preceding the date of birth. |
|
birthDateLabel, birthDateInput |
Allows you to hide the date of birth. |
|
S4.view.xml (edit/create contact screen) |
titleLabel, titleSelect |
Allows you to hide the title. |
functionLabel, functionInput |
Allows you to hide the function. |
|
departmentLabel, departmentInput |
Allows you to hide the department. |
|
mobileLabel, mobileInput |
Allows you to hide the mobile phone number. |
|
phoneLabel, phoneInput |
Allows you to hide the phone number. |
|
emailLabel, emailInput |
Allows you to hide the email address. |
|
birthdayLabel, birthdayInput |
Allows you to hide the date of birth. |
For more information about hiding UI controls, see the extensibility documentation for the respective SAP NetWeaver release on your front-end server at http://help.sap.com/fiori_implementation .
For a general description of the extensibility options and procedures of SAP Fiori apps, see http://help.sap.com/fiori_implementation .