Everything in the atlas
Type
Domain: UI & Frontend Bridge
Origin
Signals
More: CAP
Group by: Capability
Approuter session held in a bound Redis cache instance
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary Not a descriptor to deploy as it stands: the approuter's `sessionSecret` is written out in `mta.yaml`.
Fiori elements app in the HTML5 Application Repository with cdm.json
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.
MTA deploying CAP, HDI container and a Fiori elements app
CAP and UI5 app for in-place table maintenance with SmartTable
Neither the package manifest nor the repository tree declares a licence.
CAP plugin putting a draft-capable facade in front of imported OData
CAP Node.js runtime
Fiori draft handling and UI-facing behaviour for CAP services
Collaborative draft support for CAP Node.js services
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Convention-based handler layer for CAP with draft lifecycle hooks
Maven bill of materials pinning CAP Java module versions
Simple CDS bookshop model used across CAP explanations
Neither the package manifest nor the repository tree declares a licence.
Common.DefaultValuesFunction pointed at a CAP service function
Mass edit enabled in a Fiori elements list report over CAP
CAP Java draft cancel on composition items as a flag update
Neither the package manifest nor the repository tree declares a licence.
List report inline edit on a draft-enabled CAP service
Neither the package manifest nor the repository tree declares a licence.
Event registration app showing OData V4 draft with UI5 and CAP
CAP plugin generating value help for enum fields from an annotation
Parser for annotations in CDS source
Converter from CDS annotations to their OData form
Programmatic API for reading and writing project annotations
CAP Node.js runtime
Fiori draft handling and UI-facing behaviour for CAP services
Entry point for generating a Fiori application from a template
Wrapper around the CDS compiler for annotation handling
OData annotation features for the @sap/vscode-cds extension
Annotation-driven geocoding, address correction and routing for CAP
Nothing about it is readable from outside the package: there is no repository, no issue tracker, and the npm page carries no readme, so the README, the examples and the changelog can be read only from the tarball or a CDN mirror, and a bug has nowhere to be filed. Provider URLs are called from the plugin with API keys taken from environment variables in a .env file, so on BTP no call resolves through a destination and the keys live in the environment. The npm line stops at 1.0.1 on 3 November 2025; the changelog shipped inside that version is headed v2.1, so the version npm shows and the version the author counts are not the same.
User details and quickview links for createdBy and modifiedBy
Maven bill of materials pinning CAP Java module versions
CDS vocabulary for User-Rendered Patterns display annotations
The declared repository is github.com/your-username/urp-vocab, an unedited placeholder. Three releases, September 2025.
CAP bookshop with Fiori elements UI deployed whole to Cloud Foundry
Neither the package manifest nor the repository tree declares a licence.
Fiori overview page comparing aggregated and plain donut-chart cards
Neither the package manifest nor the repository tree declares a licence.
Analytical List Page over a CAP OData V4 service
Neither the package manifest nor the repository tree declares a licence.
Common.DefaultValuesFunction pointed at a CAP service function
Mass edit enabled in a Fiori elements list report over CAP
Singleton entity whose flags drive Fiori elements feature control
CAP sample drawing a material BOM as a UI5 network graph
Neither the package manifest nor the repository tree declares a licence.
Incident Management reference application for CAP
One object page field made read-only from another's value, two ways
Neither the package manifest nor the repository tree declares a licence.
List report inline edit on a draft-enabled CAP service
Neither the package manifest nor the repository tree declares a licence.
Outbound navigation patterns from a Fiori Elements list report
Neither the package manifest nor the repository tree declares a licence.
CAP and UI5 app for in-place table maintenance with SmartTable
Neither the package manifest nor the repository tree declares a licence.
Travel-booking reference app on CAP Node.js and Java backends
Showcase of Fiori elements for OData V4 features on a CAP backend
CodeJam building a bookshop app on the flexible programming model
Exercise solutions for the UX405 course on Fiori elements with CAP
UI5 apps calling CAP OData actions and functions from custom code
Neither the package manifest nor the repository tree declares a licence.
CLI for the SAP BTP Application Frontend service
CAP Node.js runtime
Playback-only SAP Companion (Help4) workarea served from CAP
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
UI5 CLI middlewares running inside the CDS server
For a deployed application's UI. The README adds it with `npm add cds-plugin-ui5 -D`, a development dependency of the CDS server, and states nothing about a build or a deployment.
CAP bookshop showing UI5 development with cds-plugin-ui5
Fiori elements app in the HTML5 Application Repository with cdm.json
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary The subaccount destination's url names the us10 trial's repository runtime, so another region or subaccount needs it rewritten before the descriptor deploys.
CAP Node.js runtime
Maven bill of materials pinning CAP Java module versions
CAP plugin rendering UI5 views with entity data on the server
On the UI5 path what comes back is an XML view or fragment with the data already substituted, streamed as the entity's media content, rather than an HTML page — the README calls this pre-rendering, and only the Vue path produces markup. The view kept under `srv/` has its UI5 bindings replaced by Handlebars expressions, so it is a second copy of the view, separate from the one the application ships. Version 1.0.8 declares `@sap/cds` `>=8` as its peer dependency, which puts a project on CAP 7 outside its stated range.
Demo CAP bookshop with server-rendered UI5 views
No license Neither the package manifest nor the repository tree declares a licence.
Functional boundary As a deployment template it stops at the service: the `mta.yaml` has one module, `gen/srv` on the Node.js buildpack, and no HTML5 repository or router module for the app.