SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

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

Last push

Where it sits

Lives in
Demonstrates
Fiori annotationsCAPFiori annotationscapabilityDescribing a service so a Fiori client can render it without hand-written UI code — titles, value helps, hierarchies and visibility expressed as model annotations rather than screen logic.
Flavors

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10
@miyasuta
maintainer

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

Connections1

fiori-navigation-patterns connectionsfiori-navigation-patternsPROVIDES→ demonstrates1demonstrates authoredFiori annotations

README

quoted from miyasuta/fiori-navigation-patterns, read
miyasuta/fiori-navigation-patterns/readme.mdOn GitHub

Fiori Elements Navigation Patterns Showcase

A CAP Node.js + SAP Fiori Elements (OData V4) project that demonstrates outbound navigation patterns from a List Report.

excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub APIdiscovered here, miyasutachecked
github.com/miyasuta/fiori-navigation-patternstree, pushes, contributors, CIchecked
readme.mdquoted, and what the entry declareschecked

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
discovered viaGitHub API · miyasuta
first seen in the atlas
ecosystem and domaincap, ui-and-frontend-bridge
Flavors1
Node.js
“A CAP Node.js + SAP Fiori Elements (OData V4) project that demonstrates outbound navigation patterns from a List Report.” — miyasuta/fiori-navigation-patterns — READMEchecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-fiori-navigation-patterns
JSON
/artifacts/miyasuta-fiori-navigation-patterns.json
MCP
Connecting an agent