C_FIORD sample questions & answers

Fjordline Maritime Logistics, a vessel-scheduling operator based in Oslo, Norway, is starting a new freestyle SAPUI5 application that dispatchers open from the SAP Fiori launchpad to plan port calls. The frontend team wants a maintainable structure: the framework should load first, and then a single declarative entry point should own the application's configuration, routing metadata, and model setup, so that new views can be added later without rewiring startup logic. A junior developer has instead placed all initialization in an inline script on the shell HTML page — creating the root view, registering routes, and instantiating models line by line — and the lead reviewer has flagged that this will not scale as more object pages are added. The team asks how the initialization should be organized so that one component, rather than page-level script, owns the application lifecycle.

Which approach best structures the application's initialization?

Cooperativa AgroVerde, a grain-trading cooperative in Curitiba, Brazil, is extending a SAPUI5 application that lets field agents review delivery contracts. A developer must display a table that lists every harvest line item belonging to a single selected contract. The contract header is already shown on the page, and the OData model exposes the line items as a collection associated with that contract. The developer needs the table's rows to repeat automatically, one row per line item, and to refresh whenever a different contract is opened. In an early attempt the developer bound the table to a single line-item entry, and only one row appeared regardless of how many items the contract held. The team wants the row set driven by the collection so the table population stays declarative rather than built in controller code.

Which binding approach correctly populates the table rows from the contract's line-item collection?

Kyomi Precision Instruments, a measurement-device manufacturer in Kyoto, Japan, runs a SAPUI5 quality-inspection app on the SAP Fiori launchpad. Inspectors open a worklist and then navigate to the detail page of one specific inspection lot. The URL must be bookmarkable so a supervisor can reopen the exact lot later, and pressing browser Back must return to the worklist. A developer configured the detail route with a fixed pattern that always points to the same lot, so every navigation and every bookmark resolves to that one record instead of the lot the inspector selected. The team needs the route to carry the selected lot's identifier so navigation targets the correct object and deep links reopen it reliably.

How should the detail route be configured so navigation and bookmarks resolve to the selected inspection lot?

Karoo Retail Group, a grocery chain headquartered in Cape Town, South Africa, needs a new application for merchandisers to browse purchasing documents and open any one to see its details. The requirements match a standard pattern: a filterable list of documents and a details page per document, with SAP's standard Fiori look, responsive behavior, and no unusual custom interactions. The backend already exposes an OData service, and the team wants to minimize hand-written UI code and long-term maintenance. One developer proposes building the entire UI as a freestyle SAPUI5 app with custom views and controllers for the list and the detail page. The lead asks whether a more standardized, metadata-driven approach would deliver the same result with far less custom JavaScript.

Which development approach best fits this standard list-and-detail requirement?

Stauffen Automotive Systems, a components supplier in Stuttgart, Germany, has two SAPUI5 apps on its SAP Fiori launchpad: a supplier-scorecard app and a separate purchase-order app. From the scorecard, buyers need a link that opens the purchase-order app already showing orders for the selected supplier. A developer implemented the link by hard-coding the other app's current URL into the scorecard, and it worked in the developer's system. After the purchase-order app was reassigned to a different launchpad configuration, the link began opening a page that no longer existed. The team follows SAP Fiori guidelines and wants cross-app navigation that stays valid when target apps are re-catalogued, rather than a fixed address embedded in the source app.

Which navigation approach aligns with SAP Fiori guidelines for opening the other launchpad app?

Maple Ridge Health Network, a hospital group in Toronto, Canada, uses a standard SAP Fiori elements application for managing procurement requests. A local requirement asks for an extra validated field on the object page that is specific to the network and not part of the delivered app. The team must keep the ability to take future updates to the standard application without re-applying their change by hand, and their SAP Fiori guidelines discourage altering delivered source. A developer proposes copying the app's original view and controller files and editing the copies directly to insert the field. The lead wants an approach that adds the field through a supported extension mechanism so the base app stays untouched and upgradable.

Which approach adds the required field while keeping the standard app upgradable?