SAPUI5 Interview Questions

Q1. What is SAPUI5?

A. Just like any other HTML5 client-side rendering library SAPUI5 is also one. SAPUI5 strictly follows RIA (Rich Internet
Application) standards. It is based on JavaScript which provides a lightweight programming model for desktop as well as mobile
applications.

Q2. Why SAPUI5?

A. As HTML5 world is the new age front technology across all aspect of internet applications SAP was kind of trailing in this
age because SAP was using age old WebDynpro for building SAP Web Applications which lacks in rich and user friendly UI.
SAP identified this and came up with its own custom HTML5 library i.e. SAPUI5.

Q3. Explain Navigation concept in SAPUI5.

A. SAPUI5 uses two mechanism for navigation in applications those are EventBus and Routing where latter supersedes since
SAPUI5 1.16. sap.ui.core.routing is the class used for the routing.
We define routing in components metadata in routing key.

Q4. What is Component?

A. Component or Component.js is the first point of our application or we can say bthat it serves as index which encapsulates all
our applications details i.e. view names, routing details, main view, applications type(Full Screen or SplitApp), application
service configuration etc..

Q5. When and How to use formatter in SAPUI5?

A. We need to use formatter when we need to perform some changes on the back end property data on the front end.
we can use formatter while data binding to a property like as follows:
oControl = new sap.ui.commons.TextField({
value : {path : /path, formatter : function(oEvent){
return Value:+oEvent;
}}});

Q6. What all design patterns are recommended/available in SAPUI5?

A. SAP recommends following application design patterns keeping in mind design consistency of the applications:
1. Master Detail
2. Master-Master-Detail
3. Full Screen
4. Full Screen-Full Screen-MasterDetail (Multi Flow)

Q7. What all types of data models available in SAPUI5?

A. As SAPUI5 follows MVC(Model-View-Controller) there model plays crucial role in the framwork. SAPUI5 has following
predefined four data models available:
1. JSON Model Client-side model, supports two way binding.
2. XML Model Client-side model and intended for small data sets this is very rarely used model.
3. Resource Model This is also client side model used to maintain resource bundles, specially texts.
4. ODATA Model This is most important model of the four provided. This is server side model, supports two way binding
ODATA model currently supports ODATA version 2.0.

Q8. What all types of views are available in SAPUI5?

A. There are following predefined three types of view available in SAPUI5:
1. JSON view
2. JavaScript View(JS View)
3. HTML View

Q9. What are the Lifecycle methods of SAPUI5 views controller?

A. There 4 four Lifecycle methods available in every SAPUI5 views controller. These are onInit(), onExit(), onAfterRendering(),
onBeforeRendering(). onInit is called when a view is instantiated and its controls (if available) have already been created; onExit
is called when the view is destroyed; used to free resources and finalize activities; onAfterRendering when the view has been
rendered and, therefore, its HTML is part of the document; onBeforeRendering is called before the controller view is re-rendered
and not before the first rendering.

Q10. What is the main difference between OData Model and JSON Model?
A. The JSON model is a client-side model and, therefore, intended for small datasets, which are completely available on the
client.The OData model is a server-side model: the dataset is only available on the server and the client only knows the currently
visible rows and fields.

Q11. What are SAPUI5 Fragments?

A. Fragments are very light weight UI controls and part of another UI. Fragments are not completely like views but they act like
a view. Fragments are defined similar like views and are names like myFragment.fragment.xml.

Q12. Does Fragment have its own controller?

A. Fragments are created without controllers, they dont have their own controllers they share controller of the view which is
invoking it.

Q13. In how many ways you can bind data to your controls?
A. We can bind data to any controls using three methods, Property, Element and Aggregation binding.

Q14. What is SAPUI5 Bootstrapping?

A. SAPUI5 Bootstrapping means loading and initializing SAPUI5 in any HTML page. The most important library or resource
loaded in SAPUI5 bootstrap is sap-ui-core.js. Apart from this theme for the application, SAPUI5 libraries etc are declared in
the bootstrapping

Q15. What is Metadata Annotations?

A. The service metadata document describes the structure of all resources in the service. This structural metadata makes it easy to
understand a service. We can explore service metadata at the address $metadata relative to the service root.

Q16. What are common Metadata Annotations?

A. Following are some of the service metadata annotations which are common and a front end developer must know these in
order to understand the service and integrate it:
-edm:EntityContainer
-edm:EntitySet
-edm:EntityType
-edm:Property
-edm:NavigationProperty
-edm:AssociationSet