Deployment Targetsfor SAPUI5 apps from BAS include:

SAP BTP(via HTML5 App Repository or MTA).

SAPUI5 ABAP Repositoryon an on-premise or S/4HANA backend system.

SAP Deployment Guide:

“Deployment to ABAP repository or HTML5 App Repository on SAP BTP is supported. SAPUI5 Java repo is deprecated.”

Fiori Launchpad is not a deployment target but a UI layer.

SAPUI5 supports differentbinding types:

Property binding: binds individual attributes (e.g., text="{/name}").

Aggregation binding: binds lists or tables (e.g., items="{/products}").

Element binding: binds a control and its children to a specific path (bindElement("/product")).

SAPUI5 Developer Guide:

“Supported binding types include Property, Aggregation, and Element binding.”

Structure/Combination are not valid SAPUI5 binding categories.

Thei18n.propertiesfile holds thetranslation keys and valuesfor different languages. Demonstrating localization involves:

Showing these files with translations like i18n_fr.properties or i18n_de.properties.

SAPUI5 dynamically picks the language based on browser settings.

SAPUI5 Localization Guide:

“Translation values are maintained in i18n.properties files. The framework selects the appropriate version based on the user’s language preference.”

The other choices (e.g., preview frame or project.json) don’t expose actual translation content.

The #COLLECTION type with parentId defines:

Asection("Personal data") containing asubsection("address").

FieldGroup address contains fields like Street and City.

SAP CDS Facet Documentation:

“Use type: #COLLECTION with nested FIELDGROUP_REFERENCE to define section/subsection hierarchies.”

It doesn’t split into two separate sections in the body or header.

TheODataModelsupports data binding to back-end OData services and includes fullserver-side capabilities:

Sorting,filtering,paging, andbatchingare natively processed by the server via query options ($orderby, $filter).

This offloads processing from the client and ensures efficient data handling.

SAPUI5 SDK - ODataModel (v2andv4):

“The ODataModel provides advanced features like server-side sorting and filtering using standard OData query options.”

In contrast, JSONModel, ResourceModel, and XMLModel are client-only and lack these features.

ResponsiveFlowLayoutallows content towrap and flowaccording to screen size and available space:

Preferred for building responsive UI layoutswithout tables.

Supports multiple rows and automatic adjustment of elements.

SAPUI5 Layout Control Reference:

“ResponsiveFlowLayout arranges controls in rows, wrapping them depending on the available width.”

Grid layout is rigid, and Vertical/Horizontal layouts are not responsive.

To add afilter field, use:

UI.SelectionFieldannotation in the CDS view.

OPA5 (One Page Acceptance)testing framework is used for:

End-to-end integration testingof SAPUI5 apps.

Verifyingnavigation, routing, and view transitionsusing test cases written in Given-When-Then format.

SAPUI5 Testing Guide:

“OPA tests simulate full user interactions, including navigation, and validate that applications behave as expected.”

QUnit is for unit tests. Sinon is a mocking library. Mock server simulates backend but doesn’t test navigation logic.

Groupsare optional in SAP Fiori 3 and newer versions:

Used tovisually organize tiles.

Tiles/apps can still be accessed via theApp Finderif the catalog is assigned.

SAP Fiori Launchpad Admin Guide:

“Groups are optional. Users can use App Finder to launch apps directly from catalogs.”

Other steps like creating catalogs and target mappings are essential for app accessibility.

Tile visibility in Fiori Launchpad depends on:

Target Mappingsbeing defined.

The tile being part of aGroupassigned to the user.

OData service authorizationsbeing present (no access = no launch).

SAP Fiori Launchpad Troubleshooting Guide:

“Missing target mapping, group, or backend authorization will prevent tile visibility even if the catalog is assigned.”

PFCG and catalog issues alone won't prevent the App Finder from showing all apps.

In QUnit:

TheActis the operation you’re testing — in this case, pressing a button (press("1")).

Arrangeis setting up the object.

Assertis comparing the output.

QUnit Testing Concepts:

“Act corresponds to executing the logic you want to test (e.g., method calls).”

SAP Fiori elements provide:

Design compliancewith SAP Fiori UX guidelines.

Reduced costby minimizing custom code.

Thesap.m.FacetFiltercontrol fires:

confirm: when filters are applied.

reset: when the user clears filters.

SAPUI5 API Reference - FacetFilter:“Events include 'confirm', 'reset', triggered by user interactions.”

listFilter/oninit are not defined FacetFilter events.

To build aWorklist-style app using SAP Fiori elements:

UseApplication Generatorto select List Report and modify it.

In themanifest.json, modify routing and filter bar settings.

Use @UI.hideFilterBar: true annotation in thebackend CDS viewto suppress the filter bar.

SAP Fiori Elements Implementation Guide:“@UI.hideFilterBar is used to hide the SmartFilterBar if a minimal worklist-style view is intended.”

StandardSAPUI5 controller lifecycle eventsinclude:

onInit()

onAfterRendering(): triggered after the view is rendered.

onExit(): when the controller is destroyed.

SAPUI5 SDK - Controller Lifecycle:

“Use onAfterRendering to manipulate HTML elements. Use onExit for cleanup operations.”

Options A and B are not standard lifecycle hooks.