SAP C_FIORD_2502 Exam Dumps

Extension points allow app developers to inject custom UI or logic into standard apps:

Custom column: Add additional columns to tables.

Custom section: Extend the Object Page with new sections.

Custom action: Trigger application-specific actions.

Field/Table building blocks are reusable constructs, not extension points per se.

In QUnit:

The Act is the operation you're testing --- in this case, pressing a button (press('1')).

Arrange is setting up the object.

Assert is comparing the output.

QUnit Testing Concepts:

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

In PFCG, to authorize access to Fiori apps:

Assign the catalog to the Menu tab of a role.

The user must be assigned the role.

SAP Authorization Guide:

''Fiori Catalogs must be added in the PFCG Menu tab to include corresponding apps in user authorization.''

Authorization tabs are used for backend authorizations, not app tiles.

In a hub deployment:

UI5 app code (HTML/CSS/JS) is deployed on SAP Front-End Server (FES).

Business logic (OData services) remains on Back-End Server (BES).

SAP Fiori Deployment Guide:

''FES hosts the UI components and handles UI5 resource loading. BES contains the application data logic.''

Web Dispatcher only routes traffic. XS Engine is for HANA-native apps.

View Replacement is the most invasive extensibility technique used when extension points aren't sufficient. It includes:

Building a completely new XML view and mapping it via sap.ui.viewReplacements in the manifest.

Assessment that the available extension hooks (like controller or fragment replacements) don't fulfill the requirement.

SAP Extensibility Guide:

''Use view replacement only if the application cannot be extended via extension points or controller hooks.''

Replacing individual controls (C, D) aligns more with control replacement, not full view substitution.