fiori-navigation-patterns
A sample of outbound navigation from a Fiori Elements list report, worked through as the triggers that start it, from semantic links to intent-based buttons, and the context each one carries.
Semantic link, intent-based navigation button and action, direct IBN link, plain URL link and a replaced row click, each with a target app in the same project so the result is visible — then the mapping questions: renaming a field on the way out, what an association passes without one, and hiding actions a semantic object would otherwise offer.
Facts
Where it sits
Who is behind it
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
Before choosing this
Signals
LicenceNo licenseNeither the package manifest nor the repository tree declares a licence
Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.
What it declares
Every artifact
- Type
- Sample
- Origin
- Independently maintained
As a sample
- Form
- A reference application
Connections
Describing a service so a Fiori client renders it without UI code
Download
README
quoted from miyasuta/fiori-navigation-patterns, readFiori Elements Navigation Patterns Showcase
A CAP Node.js + SAP Fiori Elements (OData V4) project that demonstrates outbound navigation patterns from a List Report.
Details
Sources
Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.
Compatibility and provenance
Flavors
“A CAP Node.js + SAP Fiori Elements (OData V4) project that demonstrates outbound navigation patterns from a List Report.” — miyasuta/fiori-navigation-patterns — README
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-fiori-navigation-patterns- JSON
- /artifacts/miyasuta-fiori-navigation-patterns.json
- MCP
- Connecting an agent