...
We recommend the following with regards to icon usage:
Where? | Icon Name | Icon | Suggested tooltip |
---|---|---|---|
Button to exit from an App | system-exit sap-icon://system-exit | Exit | |
Button to return to Fiori (or FAB) Launchpad | home sap-icon://home | Home | |
Application help (provided by the developer) | message-information sap-icon://message-information | More information |
JavaScript variables
We recommend naming your variables using descriptive names, and using the following guidelines:
Type | Naming Convention | Example |
---|---|---|
JavaScript Object | oObjectName | oCompany |
Integer | iIntegerValue | iCount |
Float | fFloatValue | fTotalValue |
Array | aArrayName | aCustomers |
Boolean | bBooleanValue | bVisible |
OData Sets
FAB generates the
GET_ENTITY_SET
method in the Data Provider Class for you automatically, with a built-inCASE
statement to deal with the Entity Sets that the code needs to handle. While it is tempting to keep all logic (for every Entity Set) in this method, it is not considered good (OO) practice - it is hard to maintain, difficult to find code and the method does not conform to the principle of "do one thing, and one thing well".
Instead, we recommend that you code the logic for every Entity Set in its own (appropriately named) method, and simply call these methods under the relevantWHEN
of theCASE
statement. TheGET_ENTITY_SET
method should therefore simply act as a switching mechanism to direct the processing to the relevant method.We recommend naming your Entity with the singular version of the noun (like
Customer
orCompany
) and the Entity Set as the plural (Customers
orCompanies
). An acceptable alternative would be using the patternEntitySet
, for example,CustomerSet
orCompanySet
instead.Please remember to implement manual pagination of the Entity Set for performance reasons when the method could return a large volume of data.
...
For OneList and FAB Product developments in the IQX systems, specify the Jira Ticket and the Jira Version in the attributes of the transport. These request attributes are used in querying and identifying the related transports via SE03 for the product packaging.
Attribute | Description |
---|---|
Z_JIRA_TICKET | Jira Ticket |
Z_JIRA_VERSION | Jira Version |
...
Excerpt | ||||||||
---|---|---|---|---|---|---|---|---|
| ||||||||
My Forms GuidelinesThe My Forms App enables users to view and process workflows of all the requests raised in Fiori. There are different versions of the My Forms app that can be deployed based on the client setup and requirements:
|