NewSAPUI5 and OpenUI5
220 changes
Today
App hostingcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the absence claim about ui5 artifacts.App hosting
Custom controls and librariescore coverage revisedReassessed against the graph (check:capabilities): independent maintainers, the abap2UI5 controls and a generator now shape the answer.Custom controls and libraries
Data bindingcore coverage revisedReassessed against the graph (check:capabilities): states the kinds the independent providers add; the option list names every provider.Data binding
Integrated frontend dev servercoverage by ecosystem revisedReassessed against the graph (check:capabilities): the only provider of the capability that counts is cds-plugin-ui5, which sits on the CAP door and does not serve the UI5 door, so no provider of another origin counts there. The core stays present on the sourced what_core_does. The middlewares the removed sentence named are not providers of this capability.Integrated frontend dev server
Show 8 more
Launchpad and site contentcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the note claimed that no community artifact exists, which no longer holds; it now names the kinds the SAP service and the community package add.Launchpad and site content
Launchpad pluginscore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed an absence claim and a count of providers (WRITING §3); the flavor states are unchanged.Launchpad plugins
Localizationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): providers arrived after the block was last looked at, an XLIFF editor and an MCP server among them, and the text named none of the kinds.Localization
Server-side renderingcoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): the sentence claimed an absence of providers, which goes stale when one arrives.Server-side rendering
Task and approval UIscoverage by ecosystem revisedReassessed against the graph (check:capabilities): SAP Task Center (btp-task-center, sap-official) lists ui5 in serves_ecosystems, so the UI5 door has an SAP-official presence; the note also made an absence claim about the graph.Task and approval UIs
Themingcore coverage revisedReassessed against the graph (check:capabilities): sap-theming-base-content is an SAP-official package providing this capability, and the core block never named it. State stays core-only: the new providers are SAP-origin.Theming
Touch operationcore coverage revisedReassessed against the graph (check:capabilities): the community provider's kind was not named in the block; the state stays core-and-community. The web-components flavor history note counts providers by absence and is a dated record, left as written.Touch operation
Web Components interopcore coverage revisedReassessed against the graph (check:capabilities): providers that arrived after 2026-08-31 and shape the answer were not named. State core-and-community is unchanged.Web Components interop
Mon 19
Agentic UI Extensibility: The Next Chapter of SAPUI5 FlexibilitypublishedA Devtoberfest 2026 session on SAPUI5 flexibility: a recap of key-user adaptationKey-user adaptationChanging a delivered app without modifying it — moving, hiding and adding elements as a layered set of changes that survive an upgrade.SAP only as deltas that survive an upgrade, then a lab preview in which Joule works through a pasted list of adaptation requests inside the key-user tooling — moving a section, adding one through embedded content, saving and activating a version — and writes a handover prompt when a request is outside what a key user may change. The developer half pastes that prompt into VS Code, where a coding agent generates an adaptation project through MCP tools, picks up the key-user changes already made, reads the base application's metadata and the UI5 documentation, writes the XML fragments and controller extensions for a new table column and a supplier dialogue, and restarts the editor to verify both appear. The agentic parts are unreleased; what the session shows as already available is the adaptation project for Cloud Foundry in VS Code, role-specific adaptation on Cloud Foundry from SAPUI5 1.146, views in variant management loaded when the manage-views dialogue opens rather than at startup, and the redesigned key-user adaptation mode with its change highlighting and version dialogue.Key-user adaptation
Building Agentic Workflows with n8n in Joule StudiopublishedA Devtoberfest 2026 session, JS-31, on SAP-managed n8n inside Joule StudioJoule StudioSAP’s managed development environment for building custom agents, applications and workflows from business intent, in six phases from intent and specification to deployment on an SAP-managed runtime.sap official, umbrella, shown as a labs preview on a blocked-invoice scenario: a solution made of assets, an intent refined by the web agent into requirements and then a specification, and the generated workflow opened in the n8n editor that Joule Studio connects to its own n8n tenant, with the generated files committed through GitHub. The nodes carry the other edges — the human-in-the-loop node is built on SAP Task CenterSAP Task CenterOne inbox across SAP applications: tasks from S/4HANA, SuccessFactors, Ariba and BTP workflows in one list, with a public API for a custom task provider.sap official, btp, and SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp is where model providers are configured centrally instead of per developer. It ends in Joule chat, where the approval task the workflow created is listed, opened and completed.Task and approval UIs
openui5-model-json-crudadded to the atlasOpenUI5 JSONModel extension with CRUD over HTTPData binding
openui5-model-odata-v2-odatapromiseadded to the atlasOpenUI5 OData V2 model extension with PromisesData binding
Show 13 more
openui5-paginatoradded to the atlasA UI5 custom control that pages through large data in a table, for backends that serve pages over REST rather than OData.Custom controls and libraries
openui5-touradded to the atlasOpenUI5 control library for guided app toursCustom controls and libraries
openui5-validatoradded to the atlasOpenUI5 library validating view fields against JSON schemaData binding
ui5-antaresadded to the atlasSAPUI5 library generating OData V2 metadata-based dialogs and pagesData binding
ui5-cc-timerbuttonadded to the atlasUI5 control library with a button that delays enabling or showingCustom controls and libraries
ui5-i18n-excel-converteradded to the atlasCLI converting UI5 i18n properties files to Excel and backLocalization
ui5-space-webcomponent-libraryadded to the atlasUI5 library wrapping a UI5 Web Components package, step by step
ui5-space-webcomponent-packageadded to the atlasStep-by-step UI5 Web Components package in TypeScript
app-to-app-nav-bastype properties revisedRevision round against the rules added since the draft was written. The type stays sample, so the edge stays demonstrates: the three modules are companion code to a blog post, not an application published to be deployed. form rests on the root README's one line, read as the same backfill read miyasuta/cap-cross-container's "This project is for the following blog post:". The other keys of the sample type do not exist, and nothing else the sources state asks for a field: the repository names no dependency, no whole it is part of and no flavor beyond the two generators, and the Northwind OData V2 service its descriptors read has no external entry to attach a connects edge to.
Integrated frontend dev serverecosystems revisedThe UI5 dev middlewares staged in intake-20261019-bestofui5 that forward the app's backend paths (ui5-middleware-route-proxy, ui5-middleware-destination) could only be placed under ui5-build-tooling, whose own boundary leaves proxying to a backend to middlewares. The two facets stay on CAP, where they were asked. The UI5 reading comes from the UI5 CLI Server page and SAP's backend-proxy-middleware README.Integrated frontend dev server
ui5-antaresentry revisedListed on bestofui5.org and absent from the atlas. The only UI5-door capability that holds a model-bound form and validation is ui5-data-binding; the odata capability lists no UI5 door, so the OData V2 request side has no edge of its own.Data binding
ui5-cc-timerbuttonentry revisedListed on bestofui5.org and absent from the atlas. A UI5 control library packaged for reuse, which is the concern capability:ui5-custom-controls describes.Custom controls and libraries
ui5-i18n-excel-converterentry revisedListed on bestofui5.org and absent from the atlas. Its README names the UI5 application texts and the webapp/i18n folder, so it passes the scope rule; the one capability on the UI5 door that holds it is localization.Localization
Sun 18
openui5-cameraadded to the atlasUI5 control for live camera preview and PNG captureCustom controls and libraries
openui5-passwordadded to the atlasOpenUI5 password input with strength scoring and rulesCustom controls and libraries
ui5-cap-serverside-rendering-demoadded to the atlasDemo CAP bookshop with server-rendered UI5 views
ui5-lib-visualizationadded to the atlasUI5 control library wrapping C3.js charts as ui5.viz controlsCustom controls and libraries
Show 1 more
UI5Xadded to the atlasUI5 library of eight composite controls under the ui5x namespaceCustom controls and libraries
Sat 17
@abap2ui5/embed-controladded to the atlasUI5 custom control that runs an abap2UI5 app inside a host appCustom controls and libraries
abap2UI5 frontend-webcomponentadded to the atlasabap2UI5 frontend rendering with UI5 Web ComponentsWeb Components interop
abap2UI5 protocoladded to the atlasVersioned specification of the abap2UI5 roundtrip protocol
custom-controlsadded to the atlasThirteen custom UI5 controls for abap2UI5 appsCustom controls and libraries
Show 50 more
custom-controls-customeradded to the atlasTemplate repository for own UI5 artefacts served to abap2UI5
launchpad-kpiadded to the atlasPuts a number from an abap2UI5 app on a Fiori launchpad tileLaunchpad and site content
App hostingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.App hosting
Build and deploy a CAP Project Node.js API with a SAP Fiori Elements UI and a managed approuter configurationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Build SAP Overview Page using SAP HANA Cloud & SAP CAP service annotations in Visual Studio Codeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Building an Enterprise Application Using Fiori Elements and CAP - Part 1explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Building an Enterprise Application Using Fiori Elements and CAP – Part 2explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Building an Enterprise Application Using Fiori Elements and CAP – Part 3explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Calling bound / unbound CAP actions from Fiori elements application.explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
CAP - Dynamically hide UI facets in Fiori Elementsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
CAP with Fiori Elements: Actions on List Report / Object Page using Annotations - Part1explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
CAP with Fiori Elements: Actions on List Report / Object Page using Annotations – Part2explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
CAP with Fiori Elements: Configure Multiple Views on List Report Tablesexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
CAP with Fiori Elements: Side Effects, Custom Actions, Dynamic Expressionsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Case-insensitive filters in Fiori Elements (List report + CAP)explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Create an SAP Fiori Elements UI for CAP Node.js applications in SAP Business Application Studioexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Create Fiori List Report with object page using CAPM(node.js) Serviceexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Custom controls and librariesdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Custom controls and libraries
Deep Insert in SAP CAPM Using Composition and Fiori Elementsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Developing a Fiori elements app with CAP and Fiori Toolsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Developing Fiori Element Application (List Report and Object Page) consuming the OData service created using SAP Cloud Application Programming modelexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Developing SAP Fiori Element application by using SAP Cloud Application Programming Modelexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Discovering SAP Fiori Elements Analytical functions by implementing SAP Support Message Reportingexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Display of hierarchical data in SAP Fiori elements using SAP Cloud Application Programming Modelexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Dynamic Criticality in SAP CAP Using Fiori Elements and Node.jsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Establish a central inbox with SAP Task Centerexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Task and approval UIs
Extend SAP SuccessFactors on SAP BTP with CAP - Develop the SAP Fiori Elements Applicationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Extend Upload Set with Table to Fiori Elements and utilize Object Storeexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Fiori Elements のList Reportアプリにカスタムアクションボタンを追加し、カスタムコントローラーを用いてアイコン化するexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
From R/3 ABAP to CAP/Fiori Elements on SAP BTP- Deploymentexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
From R/3 ABAP to CAP/Fiori Elements on SAP Cloudexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
How to Control the Visibility of CRUD and Custom Actions in Fiori Elements Based on Authorizationexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
How to ensure that users can efficiently enter data in SAP Fiori elements applicationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Draft handling
Integrated frontend dev servername, description revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Integrated frontend dev server
Launchpad and site contentdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Launchpad and site content
Launchpad pluginsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Launchpad plugins
Part 1: How to build an extension application for SAP S/4HANA Cloud using CAP, SAP Cloud SDK and SAP Fiori elementsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Part 2: How to build an extension application for SAP S/4HANA Cloud using CAP, SAP Cloud SDK and SAP Fiori elementsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Random collection of useful code fragments for CAP Fiori Elements and SAPUI5explains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
SAP BTP Developer's Guide: Extending Fiori Elements with the Flexible Programming Modelexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
SAP CAP Remote Services & SAP Fiori Elementsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
SAP Fiori Elements using CAP Model - Introductionexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Simple Table Maintenance in SAP Fiori Using UI5 Smart Controlsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
The SAP Fiori elements feature showcase with CAP CDS annotationsexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Touch operationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Touch operation
Understanding and Developing Fiori Plugins with Extension API & TypeScriptexplains revisedDoor scope derived from the artifacts this piece also explains, so a door page lists it only where it holds (docs/concepts/content-on-doors.md).Launchpad plugins
Use SAP CAP SAPUI5 Smart Filter to Show Value Help that are not Associated Entititesexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Visualizing Your SAP Bill of Materials Using CAP, Fiori elements, and the UI5 Network Graphexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Web Components interopdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Web Components interop
XML Annotations: The Essentials Before Adapting Documentation Samples to Your Projectexplains revisedDoor scope proposed from the title and summary, so a door page lists the piece only where it holds (docs/concepts/content-on-doors.md).Fiori annotations
Thu 15
@openui5/sap.ui.coreprovides[capability:ui5-testing] revisedThe edge carried no source, so what the package answers for this capability was an unattributed claim. The three parts are each stated by SAP's own documentation, and the level the package covers, unit and integration, is the comparison the capability now declares. End-to-end is left absent rather than entered as a no: the OPA page's restrictions are the capability's boundary and are recorded there. The other six edges were not read for this job and are unchanged.Routing and navigation
Fiori annotationscore coverage, coverage by flavor revisedThe door has two flavors and neither was assessed, so both were derived from the options alone. Java reads core-only: the three community providers are cds-plugins @sap/cds loads, and the Java side's own facts are the compiler running under the Maven build and the one hierarchy annotation the Java runtime reads itself.Fiori annotations
Wed 14
@ui5/webcomponentssources, description revisedThe paragraph named the three component packages and the framework, which reads as the whole of what the project publishes. Its own package table lists
@ui5/webcomponents-theming, @ui5/webcomponents-localization and the SAP-icons, SAP-icons-TNT and BusinessSuiteInAppSymbols collections beside them, and the npm record for 2.27.2 resolves all of them as dependencies of the main package, so what an application installs is wider than the sentence said.Web Components interopMon 12
A Guide to CDS Metadata Extensions, Fiori App Generation and SAP UI5 Controller ExtensionspublishedWalks through a RAP-based Fiori elements app end to end: layering UI annotationsFiori annotationsDescribing 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.SAP and community, unassessed onto a CDS view through a separate ABAP metadata extension object, gated by
@Metadata.allowExtensions on the base view and ordered across extensions by a required @Metadata.layer value. Generates the app 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 from the published ODataODataExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.SAP and community, narrow by design V4 service's merged $metadata document, then adds an SAP UI5 controller extension — registered in manifest.json against a Fiori elements lifecycle hook — only for behaviour the annotations cannot express.Fiori annotationsThu 8
app-to-app-nav-basadded to the atlasThree Fiori apps wired to one cross-app navigation intent
app-to-app-nav-basentry revisedStaged 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.
Sun 27
Integrated frontend dev servercore coverage, description, facets revisedThe two facts that separate the answers here: where a project has to sit to be served, and what serves its resources once it is found. Both are stated by each option's own documentation, and both are text until the answers are numerous enough to have a vocabulary.Integrated frontend dev server
Localizationcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Localization
Fri 25
@concircle/i18n-ai-translatoradded to the atlasCLI translating UI5 i18n.properties files with OpenAILocalization
@marianfoo/ui5-cc-dayjsadded to the atlasUI5 custom control formatting dates with Day.jsCustom controls and libraries
@sap-ux/odata-vocabulariesadded to the atlasOASIS and SAP OData vocabularies with a VocabularyServiceFiori annotations
cap-materialbom-graphadded to the atlasCAP sample drawing a material BOM as a UI5 network graph
Show 5 more
fiori-table-maintenanceadded to the atlasCAP and UI5 app for in-place table maintenance with SmartTable
How to Deploy a Custom Fiori App to S/4HANA Public Cloud and Add a Tile in SAP Build Work ZonepublishedA step-by-step walkthrough of taking a RAP-based Fiori app from 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 deployment to a working tile in SAP Build Work Zone, standard editionSAP Build Work Zone, standard editionA role-based business site on BTP that puts SAP, custom-built and third-party applications and extensions, cloud and on premise, behind one point of access.sap official, btp on SAP S/4HANA Cloud Public EditionSAP S/4HANA Cloud Public EditionSAP's cloud ERP, run by SAP as software as a service. For the things here it is the business system a side-by-side application on BTP reads from and writes to over its published OData APIs.: the crossNavigation/inbounds block in manifest.json that creates the Launchpad App Descriptor Item, the IAM App that links it to a Business Catalog and Business Role, and the semantic-object-and-action intent Work Zone resolves against. SSO between BTP and S/4 works because both trust the same Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp tenant.Launchpad and site content
ui5-call-actionadded to the atlasUI5 apps calling CAP OData actions and functions from custom code
ui5-webcomponents-bundleadded to the atlasCustom UI5 Web Components bundle loaded with one script tagWeb Components interop
cap-materialbom-graphentry revisedDrafted from the repository's own files, because its README is the unedited
cds init template and the only sentence the maintainer wrote about it is the repository description, "This is a sample to show the Material as Network Graph in a Fiori elements app": db/schema.cds for the model and the GraphNetwork pseudo-entity, srv/service.js for the READ handler that walks the bill of materials, app/material/webapp/manifest.json for the list report and object page generated from @sap/generator-fiori:lrop and the custom section, the graph fragment for sap.suite.ui.commons.networkgraph, and package.json for @sap/cds ^8 and @cap-js/sqlite. artifact_type sample and use_as starting-point are a placement: one commit, a local SQLite run and no deployment described. domain ui-and-frontend-bridge follows the half of it the sample is about, as on cap-sflight. No licence is recorded: the repository has no LICENSE file and package.json carries the cds init defaults "license": "UNLICENSED" and "private": true.Tue 22
SAP Task Centerrequires revisedSAP's Discovery Center lists both Work Zone editions as required services of the all-tasks plan, and npm run check:catalogue listed the relations with no edge. Basis entitlement and conditional: the plan's own description says either edition serves (vocab PERSPECTIVES, 2026-09-22).Task and approval UIs
Server-side renderingcore coverage revisedThe state said community-only and nothing else, so the cap door carried no sentence a reader could use and no source for the claim. capire states that CAP has no UI technology of its own, and the documented bootstrap of the built-in server mounts the app folder as static content without a rendering step; the community sentence names the one provider the graph holds. State unchanged.Server-side rendering
Mon 21
Adaptation Project: SAP標準Fioriアプリのフィルタ項目を必須入力へするための方法publishedWalks through making a filter field mandatory on a standard SAP Fiori elements app (Manage Purchase Orders) without modifying it: an Adaptation Project created 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 adds a local OData annotation file that applies the Org.OData.Capabilities.V1 FilterRestrictions term — RequiresFilter and RequiredProperties on the Plant field — and registers it in manifest.appdescr_variant.json against the mainService data source. It also shows how to look up the target OData service, entity container and entity set through the SAP Fiori Apps Reference Library and the service's own metadata.Fiori annotations
Sun 20
Fiori annotationscore coverage revisedThree independent cds-plugins now provide this capability on CAP beside SAP's own packages: @mpah/enum-value-help, cap-js-geoloc-plugin and urp-vocab. The relationship is unassessed: no retrieved document gives the history between them and the core.Fiori annotations
Fri 18
@sap-ux/i18nadded to the atlasReader and writer for i18n bundles of UI5 or CAP projectsLocalization
ui5-cc-pdfvieweradded to the atlasUI5 custom control rendering a PDF from a base64 data URICustom controls and libraries
Localizationecosystems, coverage by ecosystem, framing by ecosystem revisedBehind the UI5 door the texts are files in the app rather than model elements in a service, which is what the CAP framing describes.Localization
ui5-cc-pdfviewerentry revisedRead out of the marianfoo account listing. No lineage edge: the README states the fork of lemaiwo/UI5LabLibraryPDFViewer, and that repository is not in the corpus, so the fact is carried in the description rather than pointed at an id that does not resolve.Custom controls and libraries
Tue 15
Establish a central inbox with SAP Task CenterpublishedSAP's reference architecture for SAP Task CenterSAP Task CenterOne inbox across SAP applications: tasks from S/4HANA, SuccessFactors, Ariba and BTP workflows in one list, with a public API for a custom task provider.sap official, btp as one inbox for the tasks of several SAP applications, opened in the Task Center web app or as To-Dos in SAP Start and SAP Mobile Start, which is the inbox half of task and approval UIsTask and approval UIsThe screen a person approves something on — a workflow or process task rendered as a form, embedded in an inbox that supplies its context. Distinct from workflow integration, which is about driving the engine: this is the half a human touches, and its hard part is that it cannot run without the engine that normally feeds it.SAP only. It rests on Cloud Identity ServicesCloud Identity ServicesIdentity Authentication and Identity Provisioning as one tenant: the login, the user store or the federation to a corporate identity provider, and the provisioning of users into whatever sits behind it.sap official, btp: every task provider must work with Identity Authentication, its users must carry the Global User ID and so must the recipients of each task, and sign-on between the provider and Identity Authentication is what lets a user navigate from Task Center into the provider. Task Center reaches providers through destinations in a customer subaccount, with Cloud ConnectorCloud ConnectorSAP's on-premises agent that links SAP BTP applications to systems in a customer's own network, as a reverse invoke proxy that exposes only the systems and resources it is configured to allow.sap official, btp for on-premise SAP S/4HANA.Task and approval UIs
SAP Cloud Portal Serviceadded to the atlasRole-based portal sites with pages, apps and widgetsLaunchpad and site content
UI flexibility serviceadded to the atlasKey-user adaptation and personalisation for UI5 apps on SAP BTPKey-user adaptation
Key-user adaptationecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the changes live in a service the application adds, where the ABAP framing places them in the system's layered repository.Key-user adaptation
Show 1 more
Localizationecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the concern includes getting texts translated by a service, where the CAP framing is serving texts per locale and the ABAP framing is translating repository objects in the system.Localization
Mon 14
@ui5/webcomponentsadded to the atlasSAP's UI elements as standard custom elementsWeb Components interop
btp-launchpad-ui-samplesadded to the atlasUI5 projects on designing apps for SAP Launchpad Service
openui5-fhir-sample-appadded to the atlasUI5 app built with openui5-fhir against FHIR services
s4hana-avc-ui-extension-templateadded to the atlasTemplate and mock runtime for S/4HANA Variant Configuration UIs
Show 22 more
SAP-samples/fundamental-ngx-sample-appsadded to the atlasAngular performance-review demo of Fundamental NGX components
teched2025-CA262added to the atlasTechEd 2025 hands-on on SAPUI5 front-end performance
ui5-mdc-json-tutorialadded to the atlasUI5 tutorial on sap.ui.mdc controls with a JSON model
ui5-p13n-tutorialadded to the atlasUI5 tutorial adding p13n Engine personalisation to a custom table
ui5-webcomponents-ngx-sampleadded to the atlasDemo app for @ui5/webcomponents-ngx, UI5 Web Components for Angular
ui5con-2026-a11y-hands-onadded to the atlasUI5con 2026 workshop fixing accessibility defects in a UI5 app
ui5con-2026-fiori-building-blocksadded to the atlasSession building a travel dashboard with Fiori elements and SAPUI5
wdf2025-fiori-innov-day-building-blocksadded to the atlasFiori Innovation Day session building a travel dashboard
App hostingcoverage by ecosystem, coverage by flavor revisedHosting is a question about a built bundle, not about what produced it: UI5 Web Components' own README describes the library as suitable for static web sites and expects it bundled into the app rather than served from its own runtime, so the same two BTP services that answer for the freestyle door answer here too, unchanged. No artifact whose own ecosystem is ui5 states web-components on a provides or demonstrates edge for this capability, so the reading rests on the same absence coverage_by_ecosystem.ui5 already recorded.App hosting
Custom controls and librariesentry revisedFour UI5 Community repositories in this batch, a Chart.js control, a Markdown control, a Font Awesome icon library and the explorer app for it, are controls and icon sets packaged for reuse. Web Components interop and generators each hold a neighbouring concern, and neither is this one.Custom controls and libraries
Data bindingcoverage by flavor revisedSAP's UI5 Web Components documentation states a component takes data through attributes, properties and slots and leaves binding it to a model to whichever framework renders it, and openui5-core, the one artifact that provides this capability on the UI5 door, states only the freestyle flavor.Data binding
Fiori annotationsecosystems revisedWidened to ABAP: SAP-samples/abap-platform-fiori-feature-showcase demonstrates annotation-driven Fiori elements for OData V4 on RAP, the same concern as CAP's annotations.Fiori annotations
Frontend performanceentry revisedteched2025-CA262, a SAP-samples hands-on in this batch, analyses a UI5 app's network traffic, build and OData requests, and no capability held that concern: query profiling is the back-end half. Opened on the UI5 door with one member, which is a sample.Frontend performance
Key-user adaptationecosystems revisedSAPUI5-Adaptation-Project-Downloader reads adaptation-project changes out of the layered repository in an ABAP system, so the flexibility concern has an answer behind the ABAP door.Key-user adaptation
Launchpad pluginscoverage by flavor revisedA launchpad plugin is an SAPUI5 component sap.ushell loads through its Extension service; UI5 Web Components' own README states the library is not built on top of UI5 and names UI5 itself as what remains the choice for a complete application, and none of the three UI5-door artifacts behind this capability state the web-components flavor.Launchpad plugins
Localizationecosystems revisedSeven repositories translate ABAP texts: they push object lists to SAP Translation Hub, call DeepL or LibreTranslate, export a package's texts to a spreadsheet, keep form labels in a table, and read texts from the online text repository.Localization
Routing and navigationcoverage by flavor revisedUI5 Web Components' own README describes it as framework-independent custom elements usable from any web framework rather than built on OpenUI5, and SAP's own routing tutorial for a UI5 Web Components for React project adds react-router-dom; the sole ui5-door provider of this capability, openui5-core, states only the freestyle flavor on its provides edge, so no provider claims web-components either.Routing and navigation
Server-side renderingcoverage by ecosystem, coverage by flavor revisedUI5 Web Components for React documents partial SSR support since v1.17.0 (outer markup only, client-rendered component) and the base UI5 Web Components library tracks full declarative-shadow-DOM SSR as an open, unassigned feature request. Neither is a catalogued artifact in this graph, so no ui5-door provider states web-components for this capability, but the concern plainly exists here — unmapped rather than not-applicable.Server-side rendering
Task and approval UIsecosystems, coverage by flavor revisedThe one template SAP ships for a task UI is built with the SAPUI5 framework and receives its context through the component's startup parameters; UI5 Web Components' own README frames the library as not built on top of UI5 but lightweight, independent UI elements, with UI5 remaining the choice for building complete applications, and no ui5-door provider of this capability states web-components on its provides edge.Task and approval UIs
Themingcoverage by flavor, framing by flavor revisedThe mechanism reads as a different paragraph from freestyle's LESS-in-a-SAPUI5-shell model: a Web Component is consumed from plain HTML, React, Angular or Vue, so what theming IS here is the CSS variable a host page can set, not a control reading a LESS-compiled parameter.Theming
Touch operationcoverage by flavor revisedUI5 Web Components documentation states the same cozy/compact content density concept as sap.m: cozy sized for touch by default, compact an app-applied class for desktop. No artifact in the graph provides ui5-touch-uis for the web-components flavor, sap-official or community.Touch operation
Web Components interopcoverage by flavor, framing by flavor revisedThe capability's cross-ecosystem description frames this as reaching a Web Component from inside a UI5 app; inside the web-components flavor the library itself is the app's framework, not something borrowed from outside it.Web Components interop
Sun 13
fiori-fullscreen-pluginadded to the atlasFiori launchpad plugin adding a fullscreen toggle button
generator-ui5-flp-pluginadded to the atlasEasy-UI5 generator scaffolding a Fiori Launchpad pluginLaunchpad plugins
generator-ui5-ts-flp-pluginadded to the atlasEasy-UI5 generator for a TypeScript Fiori launchpad pluginLaunchpad plugins
SAP-samples/ai-seamless-integrationadded to the atlasUI5 Web Components AI patterns embedded in an OpenUI5 app
Show 11 more
SAP-samples/teched2022-DT181added to the atlasTechEd 2022 workshop mixing SAPUI5 with Fiori elements building blocks
SAP-samples/ui5-deploymentsadded to the atlasUI5 app deployed to Cloud Foundry via three approuter setups
SAP-samples/ui5-flexibility-easy-key-user-adaptationadded to the atlasUI5con 2025 tutorial on SAPUI5 flexibility and key user adaptations
SAP-samples/ui5con-2025-theming-workshopadded to the atlasUI5con 2025 workshop on theming with UI5's CSS custom properties
SAP-samples/uxc-integrationadded to the atlasUI5 Web Components shell bar and navigation inside an OpenUI5 app
ui5-cc-chartadded to the atlasUI5 custom control wrapping Chart.js for line chartsCustom controls and libraries
ui5-cc-mdadded to the atlasUI5 custom control rendering Markdown to HTMLCustom controls and libraries
ui5-fontawesome-libadded to the atlasUI5 library adding Font Awesome icon sets to sap-icon://Custom controls and libraries
ui5-icon-exploreradded to the atlasLive icon browser for the ui5-fontawesome-lib icon set
ui5-touch-controlsadded to the atlasUI5 control library of sized sap.m controls and touch inputsTouch operation
Understanding and Developing Fiori Plugins with Extension API & TypeScriptpublishedDescribes a launchpad plugin as a UI5 component without views that the shell loads for every app, SAPUI5 only, and compares extending the shell through the renderer with the
Extension service from 1.120 and FrameBoundExtension from 1.124, down to the placement options each allows. It builds fiori-fullscreen-pluginfiori-fullscreen-pluginA SAP Fiori launchpad plugin in TypeScript that adds one header button, created through the Extension API, which toggles the browser's fullscreen mode; it needs SAPUI5 above 1.120.independent, ui5 as the sample, and ends with activation: globally through /UI2/FLP_CONF_DEF and /UI2/FLP_CUS_CONF or per role through a Shell-plugin target mapping on an ABAP launchpad, and as an HTML5 app assigned to a role in SAP Build Work Zone.Launchpad pluginsWed 9
SAP Application Frontend serviceadded to the atlasManaged hosting and routing for built frontendsApp hosting
SAP HTML5 Application Repository service for SAP BTPadded to the atlasStores UI5 and HTML5 apps and serves them through the approuterApp hosting
SAP Task Centeradded to the atlasOne inbox for tasks across SAP applications and BTP workflowsTask and approval UIs
SAP Application Frontend serviceentry revised@sap/appfront-cli was in the corpus and the service it drives was not, so the BTP door listed a CLI with nothing behind it. SAP's own page names the HTML5 Application Repository as the thing to stay on where it fits better, which is why the two carry an alternative_to edge rather than one quietly superseding the other.App hosting
Tue 8
@sap-theming/theming-base-contentadded to the atlasColour, font and metric definitions of the SAP themesTheming
Build and deploy a CAP Project Node.js API with a SAP Fiori Elements UI and a managed approuter configurationpublishedGeneration and deployment in one piece, with the managed approuter rather than a standalone one — so the routing is configuration instead of a module, and the post covers what that changes at deploy time.Fiori annotations
Build SAP Overview Page using SAP HANA Cloud & SAP CAP service annotations in Visual Studio CodepublishedAn Overview Page — the card-based Fiori elements floorplan, less written about than the list report — driven entirely from annotations on a CAP service, in VS Code rather than Business Application Studio.Fiori annotations
Building an Enterprise Application Using Fiori Elements and CAP - Part 1publishedPart one of three, and it is all backend: the CAP service the UI will sit on. The author states the constraint the series works under — simple enough for someone new to the stack, without departing from the standard project layout.Fiori annotations
Show 32 more
Building an Enterprise Application Using Fiori Elements and CAP – Part 2publishedThe generator run and the List Report it produces, on top of the service from part one. This is where the annotations start doing the work rather than the CDS entities.Fiori annotations
Building an Enterprise Application Using Fiori Elements and CAP – Part 3publishedThe Object Page, which the author points out is entirely annotation-driven — there is no page to design, only facets to declare. The last of the three.Fiori annotations
Calling bound / unbound CAP actions from Fiori elements application.published
invokeAction from the Fiori elements Edit flow API, with the difference between bound and unbound actions spelled out first because the call shape differs. Under three thousand characters and it answers exactly one question.Fiori annotationsCAP - Dynamically hide UI facets in Fiori ElementspublishedFacets hidden at runtime rather than at design time, which needs two things at once:
UI.Hidden on the annotation side and a virtual element on the CDS side to decide it. Both are linked from the post, and it is barely two pages.Fiori annotationsCAP with Fiori Elements: Actions on List Report / Object Page using Annotations - Part1publishedActions on their own, at length — where an action can be placed, what the annotation looks like for each position, and what changes between the List Report and the Object Page. Part one of two.Fiori annotations
CAP with Fiori Elements: Actions on List Report / Object Page using Annotations – Part2publishedThe second half of the actions pair, published the same day. Between them they cover more ground on this one annotation than the documentation does in one place.Fiori annotations
CAP with Fiori Elements: Configure Multiple Views on List Report TablespublishedSeveral tabs over one entity, each with its own filter — the multiple-views annotation, which is one of the few Fiori elements features that changes the shape of the page rather than its content.Fiori annotations
CAP with Fiori Elements: Side Effects, Custom Actions, Dynamic ExpressionspublishedThe first of the author's Fiori elements posts, and the widest: side effects, which are the annotation that tells the UI a field changed something else; custom actions; and dynamic expressions. The three that turn a generated app into a usable one.Fiori annotations
Case-insensitive filters in Fiori Elements (List report + CAP)publishedA blocker rather than a feature: filters on a List Report are case-sensitive, the business wanted them not to be, and the CAP backend is where it gets fixed. Node and Java both.Fiori annotations
Create an SAP Fiori Elements UI for CAP Node.js applications in SAP Business Application StudiopublishedWritten the week Fiori elements gained OData V4 support, which is what made a generated List Report over a CAP Node.js service possible at all. Short, and dated in the useful sense — it marks when the generator stopped being a V2-only path.Fiori annotations
Create Fiori List Report with object page using CAPM(node.js) ServicepublishedThe short version of the generated-app walkthrough — an existing CAPM Node.js service, and the List Report with Object Page on top of it. Under three thousand characters.Fiori annotations
Deep Insert in SAP CAPM Using Composition and Fiori ElementspublishedParent and children created in one transaction, which composition already gives you in the model — the post is about what Fiori elements does with it, and what the payload looks like when the UI sends both at once.Fiori annotations
Developing a Fiori elements app with CAP and Fiori ToolspublishedA learning write-up from someone new to CAP at the time, and long enough to be thorough. Carries its own update pointing at a newer post on deploying a CAP-based Fiori app to a central launchpad without an approuter.Fiori annotations
Developing Fiori Element Application (List Report and Object Page) consuming the OData service created using SAP Cloud Application Programming modelpublishedOne of the earliest entries here, from mid-2020: the List Report and Object Page pair generated over a CAP OData service, when that combination was still new enough to need explaining.Fiori annotations
Developing SAP Fiori Element application by using SAP Cloud Application Programming ModelpublishedThe long version, and it starts by naming the floorplans — List Report, Worklist, Object Page, Overview Page, Analytical List Page — which is the decision most walkthroughs skip. Then one of them, built out against a CAP service.Fiori annotations
Discovering SAP Fiori Elements Analytical functions by implementing SAP Support Message ReportingpublishedAnalytical annotations learned by building something the author wanted — a view over SAP support messages — after a conversation in February 2021 that the post dates precisely. Exploration written up as exploration.Fiori annotations
Display of hierarchical data in SAP Fiori elements using SAP Cloud Application Programming ModelpublishedHierarchies before the framework supported them, and the post now opens with its own update saying that Fiori elements V4 and OData V4 support tree views natively and linking the guide. Read the update first; the rest is the record of what people did in the meantime.Fiori annotations
Dynamic Criticality in SAP CAP Using Fiori Elements and Node.jspublishedColouring rows by status, which sounds like a UI question and is not: criticality is a value the service has to compute and expose, so the work is a virtual element in CDS and the annotation that points at it. Comes from a real requirement — business users wanting to spot the records that need attention.Fiori annotations
Extend SAP SuccessFactors on SAP BTP with CAP - Develop the SAP Fiori Elements ApplicationpublishedThe UI instalment of the SuccessFactors extension series — the imported service is already modelled and this is the application over it. Names the three posts it depends on.Fiori annotations
Extend Upload Set with Table to Fiori Elements and utilize Object StorepublishedThe Object Store variant of the author's earlier Document Management post, written after testing @cap-js/attachments@cap-js/attachmentsAn official CAP Node.js plugin for attachment handling, with local database storage and AWS S3, Azure Blob or GCP Object Store integration.sap official, cap — a sample managing text and file information together, and offered as something for people new to BTP rather than as a pattern.Fiori annotations
Fiori Elements のList Reportアプリにカスタムアクションボタンを追加し、カスタムコントローラーを用いてアイコン化するpublishedIn Japanese. A custom action button added to a generated List Report and then given an SAPUI5 icon through a custom controller — the point where an annotation-driven app needs a piece of code, and what that costs.Fiori annotations
From R/3 ABAP to CAP/Fiori Elements on SAP BTP- DeploymentpublishedThe doing half: the steps and the code that got the application from the first post deployed and working. Shorter, and it assumes the argument has already been made.Fiori annotations
From R/3 ABAP to CAP/Fiori Elements on SAP CloudpublishedWritten by an ABAP developer of fourteen years explaining what changed and what did not — the argument being that CAP kept the focus on business logic that ABAP had, where learning UI5 and a framework or two had not. The reasoning half of a pair.Fiori annotations
How to Control the Visibility of CRUD and Custom Actions in Fiori Elements Based on AuthorizationpublishedHiding Create, Edit and custom action buttons according to what the user may actually do — the join between the authorisation model and the annotations, which is where the two usually fail to agree and the UI offers something the service will refuse.Fiori annotations
Part 1: How to build an extension application for SAP S/4HANA Cloud using CAP, SAP Cloud SDK and SAP Fiori elementspublishedThe substantial part of a side-by-side extensibility series: CAP Node.js, Cloud SDK and Fiori elements against S/4HANA Cloud. Eighteen thousand characters, and the one to read if you only read one.Fiori annotations
Part 2: How to build an extension application for SAP S/4HANA Cloud using CAP, SAP Cloud SDK and SAP Fiori elementspublishedThe second part, continuing the same extension. Opens with a recap of the stack rather than of the steps, which makes it readable on its own.Fiori annotations
Random collection of useful code fragments for CAP Fiori Elements and SAPUI5publishedExactly what it says, and the author gives the reason: none of these were easy to find in the documentation or the samples. A collection of fragments rather than an argument, and the kind of page people bookmark.Fiori annotations
SAP CAP Remote Services & SAP Fiori ElementspublishedWhat happens to a generated UI when the data is not local: a CAP service projecting a remote one, with Fiori elements on top. The author explored it to find out where the abstraction holds, which is the useful register for this.Fiori annotations
SAP Fiori Elements using CAP Model - IntroductionpublishedThe introduction to a demo project, and it says where the project came from — exploring what the then-new Fiori tools could do. Context rather than code; the List Report post is the one that builds.Fiori annotations
The SAP Fiori elements feature showcase with CAP CDS annotationspublishedThe feature showcase, which is the closest thing to a reference for what the annotations can do, presented here with its CAP CDS side. Short, because the value is in what it points at.Fiori annotations
Use SAP CAP SAPUI5 Smart Filter to Show Value Help that are not Associated EntititespublishedValue help for a field with no association behind it, which is the case the annotation assumes away. Short, and the workaround is the content.Fiori annotations
XML Annotations: The Essentials Before Adapting Documentation Samples to Your ProjectpublishedWhat to understand before copying an annotation out of the UI5 Demo Kit, which is what everybody actually does. The samples assume context the sample does not carry, and adapting one without that context is where the afternoon goes.Fiori annotations
Mon 7
Enable App-to-App Navigation in BASpublishedTesting navigation between two Fiori applications inside Business Application Studio, which Web IDE Full-Stack made easy and BAS initially did not. Two paths: between Fiori elements applications it is a few clicks in Fiori tools with both apps in the same workspace, and for a freestyle application the same result takes a short sequence of manual steps. Written in 2021 against the Fiori tools of the time, so read the mechanism rather than the clicks.Routing and navigation
How to ensure that users can efficiently enter data in SAP Fiori elements applicationspublishedGuidance for draft-enabled Fiori Elements applications aimed at the user who spends their day in them: entering data quickly and by keyboard, on a slow network, without the round trips a draft-backed form can otherwise impose. Written from the design side rather than the implementation side, which is the half most CAP writing about drafts leaves out.Draft handling
SAP BTP Developer's Guide: Extending Fiori Elements with the Flexible Programming ModelpublishedExtension points, building blocks and controller extensions in the Flexible Programming Model, aimed at developers who know the annotations but stop where the floorplan does. The premise is that the capability has been available for a while and is still being discovered, which is a fair description of where most Fiori Elements work runs out of documented ground.Fiori annotations
Simple Table Maintenance in SAP Fiori Using UI5 Smart ControlspublishedStarts from SM30 and the table maintenance dialog it generated with almost no code, then asks what the equivalent is now. That framing is the value: a maintenance screen for a custom table was a solved problem in SAP GUI and is not an obviously solved one on Fiori, and the post works through what smart controls give you towards it.Fiori annotations
Show 1 more
Visualizing Your SAP Bill of Materials Using CAP, Fiori elements, and the UI5 Network GraphpublishedA parent-child structure rendered as a network graph inside a Fiori Elements application, with the CAP service modelling the bill of materials behind it. Useful as one of the few worked examples of putting a non-standard visualisation into an annotation-driven floorplan rather than building a freestyle app around it.Fiori annotations
Mon 31
@openui5/sap.ui.coreadded to the atlasFramework core: module loader, MVC runtime, binding, routing, themingRouting and navigation
Fiori annotationscore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Fiori annotations
Localizationcore coverage revisedStates renamed to describe who is present rather than to interpret intent. left-open-on-purpose asserted a motive; core-and-community states a fact, with relationship carrying the intent separately.Localization
Tue 25
cap-companionadded to the atlasPlayback-only SAP Companion (Help4) workarea served from CAP
Fri 5
@ui5/webcomponentsreleased 2.23.0Handlers reading
event.detail.tab or event.detail.item from a tab or notification click, written against 2.22 or earlier.Web Components interopSat 30
@sap-ux/i18nreleased 1.0.0The package is published as an ECMAScript module (
"type": "module") instead of CommonJS, with Node.js 22 still the minimum; the notes give the Jest configuration for testing code that imports it.Localization@sap-ux/odata-vocabulariesreleased 1.0.0Examples and test setups written for the CommonJS build, such as a Jest configuration without ESM support.Fiori annotations
Wed 4
@sap-theming/theming-base-contentreleased 11.33.0CSS that sets an emphasized button's weight from
--sapButton_Emphasized_FontWeight.ThemingTue 27
@sap-theming/theming-base-contentreleased 11.30.1CSS that reads
--sapContent_Margin_Small or another of the four deprecated margin parameters.ThemingWed 3
@ui5/webcomponentsreleased 2.0.0Code from 1.x importing
ListSeparators.Web Components interopMon 17
@ui5/webcomponentsreleased 2.0.0-rc.6The default of
wrapping-type on ui5-checkbox and ui5-tag changed from None to Normal, so long text wraps instead of being truncated unless wrapping-type="None" is set.Web Components interopThu 6
@ui5/webcomponentsreleased 2.0.0-rc.5The default of
wrapping-type on ui5-radio-button and ui5-link changed from None to Normal, so long text wraps instead of being truncated unless wrapping-type="None" is set.Web Components interopFri 10
@ui5/webcomponentsreleased 2.0.0-rc.3Markup and samples from 1.x that use
<ui5-badge>.Web Components interopThu 18
@ui5/webcomponentsreleased 2.0.0-rc.2Markup from 1.x using
<ui5-multi-combobox allow-custom-values>.Web Components interopTue 9
@ui5/webcomponentsreleased 2.0.0-rc.0Markup from 1.x such as
<ui5-list mode="MultiSelect">.Web Components interopTue 5
openui5-passwordreleased 1.0.0Using the control in an application on a UI5 version below 1.120.Custom controls and libraries