app-to-app-nav-bas
Three generated Fiori apps wired to one cross-app navigation intent: fe-customers declares Customers-display in its descriptor, and fe-orders and freestyle each register that intent in their own launchpad sandbox configuration.
The repository is both halves of a cross-app navigation setup, against the public Northwind OData V2 service. fe-customers declares the inbound intent Customers-display, semantic object Customers with action display, under crossNavigation.inbounds in its manifest.json. fe-orders and freestyle each carry an appconfig/fioriSandboxConfig.json that registers the same Customers-display key against SAPUI5.Component=fecustomers at ../resources/fecustomers. fe-orders came from @sap/generator-fiori-elements and freestyle from @sap/generator-fiori-freestyle, both generated in SAP Business Application StudioSAP Business Application StudioSAP's development environment for business applications, delivered as a cloud service and opened in a browser, where work happens in preconfigured dev spaces.sap official, btp on 12 January 2024 against UI5 1.120.4. The README is one line pointing at the blog post the repository accompanies, so what the steps are for is written there and not here.
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 tutorial's companion code
Connections
Getting apps, cards and pages in front of users in a launchpad
Download
README
quoted from miyasuta/app-to-app-nav-bas, readThis repository is related to the blog post below:
https://blogs.sap.com/2021/05/24/enable-app-to-app-navigation-in-bas/comment-page-1/#comment-702940
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
“**App Generator**<br>@sap/generator-fiori-elements” — miyasuta/app-to-app-nav-bas — fe-orders/README.md
“**App Generator**<br>@sap/generator-fiori-freestyle” — miyasuta/app-to-app-nav-bas — freestyle/README.md
History in the atlas
- form: tutorial
- Staged from the github-orgs sweep of the miyasuta account. ecosystem: ui5 and domain: ui-and-frontend-bridge follow from the three modules being generated Fiori apps whose subject is the navigation intent in their descriptors. demonstrates: capability:launchpad-content rests on that capability's UI5 framing, the intent that navigates to the app; the appconfig/fioriSandboxConfig.json half is the development-time counterpart, and capability:local-development is open to the CAP and ABAP doors only, so no edge was written to it. The flavors rest on the generator each module's own README names. No licence file in the repository, so identity.license is absent.
- First seen.
For your agent
- Ref
artifact:miyasuta-app-to-app-nav-bas- JSON
- /artifacts/miyasuta-app-to-app-nav-bas.json
- MCP
- Connecting an agent