Versions Compared

Old Version 1

changes.mady.by.user Charles Evans (Unlicensed)

Saved on

compared with

New Version 2

changes.mady.by.user Hannah.Dela

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Image Modified

Exit

Button to return to Fiori (or FAB) Launchpad

home

sap-icon://home

Image Modified

Home

Application help (provided by the developer)

message-information

sap-icon://message-information

Image Modified

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

  1. FAB generates the GET_ENTITY_SET method in the Data Provider Class for you automatically, with a built-in CASE 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 relevant WHEN of the CASE statement. The GET_ENTITY_SET method should therefore simply act as a switching mechanism to direct the processing to the relevant method.

  2. We recommend naming your Entity with the singular version of the noun (like Customer or Company) and the Entity Set as the plural (Customers or Companies). An acceptable alternative would be using the pattern EntitySet, for example, CustomerSet or CompanySet instead.

  3. 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 Guidelines

The 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:

Application

Description

FAB My Forms

This is a dynamic My Forms app that is built in the FAB Launchpad and can be deployed to clients without a standard Fiori Launchpad.

The settings of this app can be configured in transaction /n/IQX/FAB_CONFIG → App Configuration. For more information,see documentation App Configuration.

FLP Dynamic My Forms

App Name: IQX_MY_FORMS

This is a dynamic My Forms app that can be deployed in the standard Fiori Launchpad. For easier deployment of changes, it is advisable to use this app for clients requiring enhancements or customizations of the My Forms app.

FLP Standalone My Forms

App Name: IQX_FLP_MY_FORMS

This is a standalone My Forms app that can be deployed in the standard Fiori Launchpad. For better performance, it is advisable to use this app for clients who do not require enhancements or customizations of the My Forms app.