Menu
This skill should be used when testing "FLP navigation", "semantic object deep links", "tile-based navigation", "WorkZone frame switching", "cross-app navigation", or "browser history" in SAP Fiori Playwright tests.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
This skill should be used when "bridge injection fails", "control discovery returns empty", "window.__praman_bridge is undefined", or "UI5 module loading times out". Covers the 3-tier getById resolution, polling mechanism, and manual bridge diagnostics.
This skill should be used when an agent needs to issue "playwright-cli" commands, "run-code" browser scripts, "snapshot" accessibility trees, or manage "session state" with state-save/state-load. Mandatory reading before any CLI interaction with SAP apps.
This skill should be used when testing "Fiori Elements" apps, "List Report", "Object Page", "Analytical List Page", or "Overview Page". Covers SmartFilterBar, SmartTable, ObjectPageLayout, DynamicPage patterns, and the FE test library API.
This skill should be used when testing "OData V2" or "OData V4" service calls, "reading model data", "intercepting batch requests", "seeding test data", or "verifying CSRF tokens" in SAP Playwright tests.
This skill should be used when implementing "SAP login", "IDP redirect chains", "SSO configuration", "certificate-based authentication", or "BTP SAML2/IAS" in Playwright tests. Covers basic form auth, Office 365 SSO, API keys, multi-tenant, and mTLS.
This skill should be used when "finding UI5 controls", "interacting with controls", "asserting control state", or working with "selector syntax", "SmartField inner controls", or "custom matchers". Covers id, controlType, properties, bindingPath, ancestor selectors and core Praman fixture methods.
| name | navigation |
| description | This skill should be used when testing "FLP navigation", "semantic object deep links", "tile-based navigation", "WorkZone frame switching", "cross-app navigation", or "browser history" in SAP Fiori Playwright tests. |
| version | 0.1.0 |
SAP Fiori Launchpad uses hash-based routing: #SemanticObject-Action?param1=value1¶m2=value2. Entity deep links append the path: #SemanticObject-Action&/EntitySet('key').
Use the ui5Navigation fixture for all navigation:
navigateToApp(semanticObjectAction) -- navigate by semantic object + action string (e.g., 'PurchaseOrder-manage')navigateToTile(tileTitle) -- find and click a tile by its visible titlenavigateToIntent(intent, params?) -- navigate with explicit intent object { semanticObject, action } and optional parametersnavigateToHash(hash) -- navigate to an arbitrary FLP hash (useful for deep links with entity keys)navigateToHome() -- return to the FLP home pagenavigateBack() -- trigger browser back navigationsearchAndOpenApp(searchText) -- use FLP search to find and open an appgetCurrentHash() -- return the current FLP hash for assertionsAlways call ui5.waitForUI5() after every navigation to wait for the target app to stabilize.
| Semantic Object + Action | App |
|---|---|
PurchaseOrder-manage | Manage Purchase Orders |
PurchaseOrder-create | Create Purchase Order |
SalesOrder-manage | Manage Sales Orders |
SalesOrder-create | Create Sales Order |
Supplier-display | Display Supplier |
Material-display | Display Material |
BusinessPartner-manage | Manage Business Partner |
JournalEntry-display | Display Journal Entries |
For SAP Build Work Zone (standard or advanced edition), initialize the WorkZone handler before navigation:
await btpWorkZone.init();
await ui5Navigation.navigateToApp('PurchaseOrder-manage');
Work Zone wraps apps in iframes. btpWorkZone.init() handles frame switching automatically so subsequent ui5 calls target the correct frame context.
When a test navigates between multiple Fiori apps (e.g., from a List Report to an Object Page to a related app), call ui5.waitForUI5() after each transition. The hash changes but the page may not fully reload -- UI5 handles routing internally.
Navigate directly to a specific entity:
await ui5Navigation.navigateToHash("#PurchaseOrder-manage&/PurchaseOrder('4500001234')");
Use deep links to skip the List Report and test Object Pages directly. This reduces test execution time and isolates Object Page tests from filter/search behavior.
Refer to examples/ for complete navigation patterns.