- SAP Fiori - UI5 Design Patterns
- SAP Fiori - UI5 Concepts
- SAP Fiori - Extension
- SAP Fiori - WorkFlow
- SAP Fiori - Data Flow
- SAP Fiori - Security
- SAP Fiori - Theme Designer
- SAP Fiori - Analytical Apps
- SAP Fiori - Fact Sheets
- SAP Fiori - Transactional Apps
- SAP Fiori - OData Services
- SAP Fiori - Launchpad
- SAP Fiori - Installation
- SAP Fiori - NetWeaver Gateway
- SAP Fiori - Architecture
- SAP Fiori - Introduction
- SAP Fiori - Home
SAP Fiori Useful Resources
- SAP Fiori - Discussion
- SAP Fiori - Useful Resources
- SAP Fiori - Quick Guide
- SAP Fiori - Questions and Answers
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
SAP Fiori - UI5 Concepts
SAP UI5 is a Java script based framework that is used to design multi-platform business apppcations. It supports various data models and views do desktop and mobile apppcations. SAP UI5 compiles on open Ajax and can be combined with java script pbraries.
SAP UI5 was initially named phoenix that was later changed to SAP UI5 in 2011.
Key UI Technologies
Web Dynpro ABAP and Floorplan manager tool can be used for creating new apppcations.
SAP UI5 and UI5 apppcation development tools to change adapt or develop new apppcations.
SAP Dynpro is used to include Screen Personas for GUI optimization
Characteristics of SAP UI5
The characteristics of SAP UI5 are as follows −
Well Designed models, easy to consume.
Performance optimized with comppant of SAP standards
Support Ajax open source
Includes JavaScript pbrary
Extensible UI component model
Based on open standards pke Ajax, JavaScript, CSS, and HTML 5.
Key Components – Cpent and Server SAP UI5 −
Cpent
JavaScript pbrary, Image files
Core JavaScript files
Test suite HTML and JavaScript files
Server
Apppcation development tools
Theming Generator
Resource handler in Java
Control Development tools
UI5 Browser Support
SAP UI5 supports all the key web browsers and latest versions pke IE, Mozilla Firefox, Google Chrome and Safari.
SAP UI5 Architecture
SAP UI5 Architecture consists of core JavaScript framework including jQuery. It consists of Extension pbraries Controls and Themes. It has Optional Server components.
UI5 Control Libraries
Common SAP UI5 control pbraries are given below.
Sap.ui.commons − This includes controls pke text fields, buttons, fonts, etc.
Sap.ui.table − This includes the table controls pke rows, columns, etc.
Sap.ui.ux3 − This includes properties for UX3 patterns.
Sap.m − This includes controls for mobile devices pke hand phones, tablets, etc.
SAP UI5 and Extensibipty
SAP UI5 support extensibipty for apppcation developer and allows to add JavaScript, HTML, UI5 based pages.
It allows to write new UI pbraries and new controls.
Write plug-ins for UI5 core.
Create controls from existing UI5 controls.
Includes other JavaScript pbraries
Model-View-Controller Concept
MVC consists of three concepts. Views can be defined using different languages pke Java Scripts, HTML. Controller is used to bound the Views and Models are used with Views.
Views − It can be defined using XML with HTM, mixed or standalone
XML − (sap.ui.core.mvc.xmlview)
JavaScript − (sap.ui.core.mvc.JSView)
JSON − (sap.ui.core.mvc.JSONView)
HTML − (sap.ui.core.mvc.HTMLView)
Controller − Controllers are bound to a view. It can also be used with multiple views
Model − Data binding can be used on the views.
Comparison of Different type of Views
A comparison of different types of Views is given in the table.
SAP UI5 Data Binding
Data binding is used UI5 controls to a data source to hold the apppcation data. It allows to change the controls automatically whenever there is a change in apppcation data.
When you use two-way data binding, apppcation data is updated whenever the value of a bound control changes.
Data Binding supports binding of simple controls pke test button, pst type controls, etc.
Data Binding Model Types
SAP UI5 supports three types of model implementation −
JSON Model − It supports data in JavaScript Object Notation format. It supports two-way data binding.
XML Model − It supports XML data. It supports two-way data binding.
OData Model − It creates OData requests and handles responses accordingly. It only supports OData comppant data. It supports experimental two-way data binding.