onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
NewSAPUI5 and OpenUI5

New in UI5

7 days30 days90 daysAll time
All time
50releases875added to the atlas97new pieces of content275revisions
Change
Kind
Origin
Domain
1297 changes
DayCapability

Today
39 changes
audit-summaryadded to the atlasGroups npm audit findings by root dependency, with failing thresholdsCLI,
git-env-branchesadded to the atlasShows which feature branches reached which environment branchCLI,
Give Your AI Agent Some Tools: Introducing the UI5 MCP ServerpublishedAnnounces @ui5/mcp-server, SAP's open-source MCP server for UI5 development, and walks through its initial six tools. get_project_info, get_api_reference and run_ui5_linter (which applies UI5 linter fixes) read the project's own version, manifest and code rather than an LLM's training data, which is what agent access to your code explains. create_ui5_app scaffolds a new JavaScript or TypeScript project, standalone or inside an existing CAP application, from templates with pre-configured OData model setups, which is generators.Blog,
How to Use NPM Modules Like crypto-js in SAPUI5 Using UI5 Tooling ModulespublishedWalks through adding ui5-tooling-modules to a SAPUI5 project on UI5 Tooling v3: installing the npm package crypto-js alongside it, then wiring a ui5-tooling-modules-task builder task and a ui5-tooling-modules-middleware dev-server middleware into ui5.yaml so the UI5 module loader can resolve it. A controller then loads crypto-js/sha256 through sap.ui.define and calls it like any other AMD dependency, with the stated limit that the pattern works only inside a controller or other AMD-style module, not through a top-level import or require().Blog,
Show 35 more
UI5 MCP Server Got Extended for UI Integration Cards GenerationpublishedVersion 0.2.1 of the UI5 MCP Server adds three tools for UI Integration Cards: get_integration_cards_guidelines feeds an agent current best practices and API versions, create_integration_card scaffolds a new card project, and run_manifest_validation checks the generated manifest against the schema. The post frames these as closing the same gaps as the server's existing tools — an LLM's outdated or wrong card API knowledge — this time for scaffolding and validating a card rather than a full app.Blog,
ui5-task-check-eocpadded to the atlasUI5 build task warning when the app's UI5 version reaches EOCPBuild tool,
Robin van het Hofadded to the atlasPerson,
Agent access to your codecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the tool count and the two absence claims about who has built something.Capability,
Agent guidancecoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): docs/WRITING.md §3 rules out provider counts and absence claims in every capability field.Capability,
App hostingcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): removed the absence claim about ui5 artifacts.Capability,
Attachmentscoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): drops a count-like contrast with a plugin the flavor does not have.Capability,
Authenticationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): no community artifact on the UI5 door provides this capability by an edge; the middlewares the text named provide ui5-build-tooling, and the only sample on the door is not a presence. what_core_does stays, so the core remains present.Capability,
Build and dev-server toolingcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): removed a count ("the one ... project") and an absence claim about who built something, restated as a fact about the documentation.Capability,
Change promotioncore coverage, id, ecosystems, name revisedPublic feedback issue #9. The ABAP name is kept in framing_by_ecosystem.abap; the default name and description now state the cross-door concern.Capability,
Custom controls and librariescore coverage revisedReassessed against the graph (check:capabilities): independent maintainers, the abap2UI5 controls and a generator now shape the answer.Capability,
Data bindingcore coverage revisedReassessed against the graph (check:capabilities): states the kinds the independent providers add; the option list names every provider.Capability,
Destinationscoverage by ecosystem revisedReassessed against the graph (check:capabilities): the entry is in the graph, so the name links to it and not to its repository (WRITING section 3.6).Capability,
Document extractioncoverage by ecosystem revisedReassessed against the graph (check:capabilities): removed the provider-count and absence claims (docs/WRITING.md §3); the states are unchanged.Capability,
Documentationcore coverage, coverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): absence claims about providers go stale as providers arrive. The flavor states are unchanged.Capability,
Editor supportcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): the providers behind the UI5 door are SAP's (UI5 Language Assistant, and SAP Build Code and SAP Web IDE Full-Stack, which serve ui5). The community SAPUI5 Extension is an entry in the graph but has no provides edge to this capability.Capability,
Generatorscore coverage, coverage by ecosystem, framing by ecosystem revisedReassessed against the graph (check:capabilities): the atlas holds these entries, so the links point at them and not at their repositories (docs/WRITING.md section 4).Capability,
Importing and exporting table datacore coverage revisedReassessed against the graph (check:capabilities): the count of sample repositories goes stale as providers arrive, and the ABAP backend importer and the Excel add-in change the shape of the answer, so the note names those kinds. The ABAP state stays core-and-community.Capability,
Input validationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact carries a provides edge to this capability for the UI5 door, because openui5-validator provides ui5-data-binding. The state follows the edges, and the core stays present through the block's sourced what_core_does.Capability,
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.Capability,
Knowing the maintenance status of a releasecore coverage, coverage by ecosystem revisedui5-task-check-eocp, from public feedback issue #6, is the first independent provider on the UI5 door, beside SAP's SAPUI5 version overview.Capability,
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.Capability,
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.Capability,
LLM integrationcoverage by ecosystem, core coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): the note claimed who provides the capability behind this flavor, which moves with the corpus. The flavor state is unchanged.Capability,
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.Capability,
Loggingcoverage by ecosystem revisedReassessed against the graph (check:capabilities): the state is now community-only and the block needed to say what the community adds.Capability,
Seed datacore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): no artifact provides seed-data for the UI5 door; the two tools the sentence named provide ui5-testing. The core stays present on the sourced what_core_does. The tools stay on the graph under ui5-testing.Capability,
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.Capability,
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.Capability,
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.Capability,
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.Capability,
TypeScript supportcore coverage revisedReassessed against the graph (check:capabilities): four providers arrived after the block was assessed (dts-generator task, Babel transform, JSX runtime, UI5 MCP server) and the text named none. The state stays core-and-community: the block's sourced what_core_does keeps the core present and community-origin providers count for the ui5 door. assessed_at and relationship stand.Capability,
UI5 testingcore coverage, coverage by flavor revisedReassessed against the graph (check:capabilities): Node.js unit test environments and mock-data generators are kinds the text did not name.Capability,
Vulnerability scanningecosystems, description revisedPublic feedback issue #10. CAP and UI5 coverage assessed as unmapped: no atlas artifact provides the dependency-tree check there yet.Capability,
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.Capability,
Yesterday
2 changes
UI5 Plugins for Coding Agents: Now Supporting GitHub CopilotpublishedUI5/plugins-coding-agents renames itself from "UI5 Plugins for Claude", since the plugin concept — skills, MCP server, guidelines — was always agent-agnostic, and with v0.1.3 adds GitHub Copilot support alongside Claude Code through Awesome GitHub Copilot. Three skills join the ui5 plugin: ui5-best-practices-integration-cards for UI Integration Card manifest and binding rules, ui5-best-practices-opa5, which uses a TestRecorder to inspect the running app's control tree and generate waitFor snippets, and ui5-best-practices-tables, a selection guide across UI5's table controls. Installing the skills alone, for an agent that reads neither marketplace, still leaves @ui5/mcp-server to be set up by hand.Blog,
Agent access to your codecoverage by ecosystem revisedRewritten at the maintainer's request (2026-10-25): what SAP ships named whole, and what the community adds written from what its ABAP MCP servers state about how they run, connect and sign in.Capability,
Sat 24
49 changes
btp-agentadded to the atlasLangGraph agent and UI5 chat screen over four BTP MCP serversSample,
aesatirogluadded to the atlasPerson,
alisonjiadded to the atlasPerson,
Amirthaadded to the atlasPerson,
Show 45 more
ankitshah25added to the atlasPerson,
Belle Panadded to the atlasPerson,
Chris Perumaladded to the atlasPerson,
Claire Westadded to the atlasPerson,
denoadded to the atlasPerson,
Denys Severynadded to the atlasPerson,
Eason-Lingadded to the atlasPerson,
elenaylzadded to the atlasPerson,
Felixadded to the atlasPerson,
florianstephan01added to the atlasPerson,
flx-rscadded to the atlasPerson,
Giorgi Cheishviliadded to the atlasPerson,
Harald Gutbrodadded to the atlasPerson,
i307698added to the atlasPerson,
ianquigley-sapadded to the atlasPerson,
IB002added to the atlasPerson,
ilias-gmailadded to the atlasPerson,
Inna Atanasovaadded to the atlasPerson,
Johannes Dobereradded to the atlasPerson,
Justin Wilabyadded to the atlasPerson,
Lena Hammereradded to the atlasPerson,
levwzadded to the atlasPerson,
Luca Mülleradded to the atlasPerson,
Marcos Canales Mayoadded to the atlasPerson,
Mariana Nabokaadded to the atlasPerson,
Mathieu Lajoieadded to the atlasPerson,
matseadded to the atlasPerson,
Michael Henningeradded to the atlasPerson,
msaravanabhavanadded to the atlasPerson,
ᴍᴀʀᴄadded to the atlasPerson,
Ogulcan Kusluogluadded to the atlasPerson,
oksanazubchenkoadded to the atlasPerson,
Paola Lauferadded to the atlasPerson,
Philipp Reisingeradded to the atlasPerson,
PrayasDas03added to the atlasPerson,
Rodrigo Eidelveinadded to the atlasPerson,
Selvakumar Shanmugamadded to the atlasPerson,
SimonStemmleadded to the atlasPerson,
stefanoScalzoadded to the atlasPerson,
Tarang Guptaadded to the atlasPerson,
Vivekadded to the atlasPerson,
ynnenuadded to the atlasPerson,
zhouwei0115added to the atlasPerson,
詹斯迪added to the atlasPerson,
ui5-test-runnerreleased 6.0.0Command line running UI5 QUnit and OPA tests in parallelCLI,
Thu 22
1 change
SRB Consulting Teamadded to the atlasPerson,
Wed 21
1 change
Using the UI5 Mockserver for Client-Specific Data and TestingpublishedWalks through a same-day feature in @sap-ux/ui5-middleware-fe-mockserver, 'Support autoloading mockdata file for specific tenants', which loads a <Entity>-<client>.json file keyed to the sap-client URL parameter and falls back to the entity's plain JSON file when no client-specific one exists. Shows the setup replacing generated mock data with hand-written JSON, then drives the same sap-client parameter through separate package.json scripts so wdi5 end-to-end tests can run against distinct tenant datasets.Blog,
Tue 20
26 changes
Adrian Duszyńskiadded to the atlasPerson,
Aydin Ozcanadded to the atlasPerson,
Brianadded to the atlasPerson,
Carlos Orozcoadded to the atlasPerson,
Show 22 more
Codexadded to the atlasPerson,
faustefanadded to the atlasPerson,
Frank Stødleadded to the atlasPerson,
Hasan Çiftçiadded to the atlasPerson,
Herbert Kaintzadded to the atlasPerson,
huschlekadded to the atlasPerson,
Ilja Postnovsadded to the atlasPerson,
Jascha A. Quinternadded to the atlasPerson,
jchirkadded to the atlasPerson,
Joaquim Monserrat Companysadded to the atlasPerson,
Kamil Kováčadded to the atlasPerson,
lenasrdadded to the atlasPerson,
Martín Rodriguezadded to the atlasPerson,
mdel-cmadded to the atlasPerson,
Michael Delladded to the atlasPerson,
nwei-mcadded to the atlasPerson,
osvaldoalvaradodevadded to the atlasPerson,
PulseShiftadded to the atlasPerson,
Raffaele Di Sommaadded to the atlasPerson,
Sergio Graciaadded to the atlasPerson,
Wolfgang Haagadded to the atlasPerson,
ypcycadded to the atlasPerson,
Mon 19
78 changes
@ui5-community/jsx-runtimeadded to the atlasPlugin-based JSX runtime for UI5 views written as .tsxPackage,
@ui5-community/jsx-runtime-helloworldadded to the atlasScaffolded UI5 TypeScript app consuming the JSX runtimeSample,
@ui5-community/jsx-runtime-showcaseadded to the atlasShowcase and documentation app of @ui5-community/jsx-runtimeSample,
@ui5/linteradded to the atlasStatic analysis tool for UI5 projectsCLI,
Show 74 more
@ui5/middleware-code-coverageadded to the atlasUI5 CLI middleware for Istanbul code coverageBuild tool,
@ui5/sample-appadded to the atlasOpenUI5 sample app set up with the UI5 CLISample,
@ui5/tooling-webcadded to the atlasDeprecated UI5 Tooling extensions for UI5 Web Components wrappersBuild tool,
Agentic UI Extensibility: The Next Chapter of SAPUI5 FlexibilitypublishedA Devtoberfest 2026 session on SAPUI5 flexibility: a recap of key-user adaptation 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.Talk,
AI-assisted SAP development with MCPpublishedA Devtoberfest 2026 session (UI-41) that traces AI-assisted SAP development from pasting code into a chat window to coding agents with built-in connectors, and sorts the MCP servers around SAP development into SAP's own, the community's and the hosted ones, where the agent cannot change what the server allows. Four demos follow: GitHub Copilot alone explaining an ABAP report from a Git repository, @ui5/mcp-server reading an OpenUI5 sample app and converting it to TypeScript, mcp-sap-docs grounding Terraform files for a BTP subaccount the presenter had not written before, and arc-1 with Copilot in Eclipse tracing why a title longer than 40 characters is rejected and proposing the DDIC-allowed length instead. It ends on a skill that migrates an SAP Gateway project on an ECC system to RAP on S/4HANA step by step, and on a rule Marian Zeis gives for servers written for internal use: keep them read-only, because what the agent is short of is context.Talk,
Beyond copilots: Agentic development with SAPUI5publishedDevtoberfest 2026 session UI-12, from the SAPUI5 team, on the year of work behind UI5/plugins-coding-agents: what a model produces for UI5 without help — outdated concepts, framework versions a decade old, generic JavaScript rules, code that does not run — and the two ways they chose to close that gap, an MCP server in September 2025 and skills packaged as plugins once agents began reading them. Three plugins are demonstrated live in Claude Code: the everyday one scaffolds an Oktoberfest tents application in about four minutes, the TypeScript conversion plugin rewrites an existing JavaScript project and reconfigures its build with the types and the transpile task, and the modernisation plugin takes a ten-year-old application through staged migrations, applying UI5 Linter's automatic fixes where they cannot break the app and the model where they can, then running the tests. @ui5/mcp-server is still the path for the parts that need a server, and the plugins are installed from the Claude Code and GitHub Copilot marketplaces rather than a UI5-hosted one.Talk,
Bring "developers.sap.com" Into Your Dev Environment: SAP Developer Context for AI Coding AgentspublishedDevtoberfest 2026 session FA-11: a tour of the rebuilt developers.sap.com by the team that runs it, from the administration screens behind the home page to the agent interfaces in front of it. The site is a CAP application on SAP HANA Cloud and SAP BTP, open-sourced in full, and the half of the session that places it here is how its content reaches an agent: every tutorial is also served as markdown, a coding agent is detected and given that version instead of the HTML, a well-known agent card advertises what the site offers, and SAP Developers MCP answers questions about tutorials, news and a reader's own completion history in Claude Code and Joule Desktop, over OAuth or a personal access token. Behind the answers sit two things working together: a knowledge graph in the HANA database over 1400 tutorials and 11,000 concepts, and SAP AI Core for the Joule interactions and the embeddings, with the agent harness written for the site rather than taken off a shelf. Where neither MCP nor A2A is available, the same content is published as skills.Talk,
Bringing SAP themes to any web app with coding agentspublishedA Devtoberfest 2026 session from SAP's UI theme designer team, in two halves. The first is how an SAP theme is built: seven reference tokens, the main tokens that carry the semantics, component tokens such as the emphasized button background, and derived tokens for states like hover — the inheritance chain that makes theming hard to follow by eye, and the reason a custom theme always derives from an SAP base theme. The second installs SAP/ui-theme-designer-plugins-for-coding-agents in Claude Code and has it apply SAP design tokens to a login screen built with a non-SAP component library, then make the page themeable from a theme root and a theme URL parameter; the design-tokens skill npm-installs the theming content to read current parameter values, and the help skill fetches the UI theme designer help pages at query time. The presenters state the skills are not limited to SAPUI5 and run in any coding agent that reads skills.Talk,
Building Agentic Workflows with n8n in Joule StudiopublishedA Devtoberfest 2026 session, JS-31, on SAP-managed n8n inside Joule Studio, 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 Center, and SAP AI Core 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.Talk,
From Intent to Arcade: Building Joule*Bert with Joule Studio and AI-Assisted Pro CodepublishedA Devtoberfest 2026 AI-track session that takes a Q*bert-style arcade game, written as an Easter egg for colleagues, through every phase Joule Studio runs: intent analysis with its clarifying questions, a product requirements document, a specification with its task list, generated code, generated tests and deployment. The knowledge-graph lookup reports that the game maps to no enterprise process and the flow adjusts, and the presenter edits the requirements by hand when the first version declares sound out of scope. He then pushes the project to GitHub, clones it and initialises the jl command line so that Joule Studio's MCP servers are wired into the coding agent in VS Code, where mobile arrow keys were added afterwards; applications could not yet be deployed to the Joule Studio runtime, so this one runs on Kyma.Talk,
generator-ui5-react-nestadded to the atlasYeoman generator for a UI5 app that loads a React appGenerator,
Intelligent App Development at Scale: SAP Fiori Elements + ABAP Development Tools for VS CodepublishedA Devtoberfest 2026 session (UI-33) that builds a RAP service and the SAP Fiori elements app over it from one VS Code workspace, with a coding agent driving two of SAP's MCP servers. The ABAP Development Tools for VS Code edges hold on the demo itself: its virtual file system keeps the ABAP package beside the Fiori project, the ADT MCP Server inside it creates, changes and activates the ABAP objects, and a version not yet released publishes the service binding from the agent instead of by hand. The @sap-ux/fiori-mcp-server edge covers its generators and the three-step workflow it uses for changes — list the functionality available for the application, ask for its JSON schema, then execute it — and the agent guidance edge rests on the skills the Fiori team publishes beside it, on the session's account of what a skill adds that a server does not, and on the analytical chart demo where a skill orchestrates both servers in one task.Talk,
jest-environment-ui5added to the atlasJest environment running UI5 unit tests in Node.jsPackage,
openui5-error-collectoradded to the atlasUI5 library collecting an app's JavaScript errorsPackage,
openui5-model-json-crudadded to the atlasOpenUI5 JSONModel extension with CRUD over HTTPPackage,
openui5-model-odata-v2-odatapromiseadded to the atlasOpenUI5 OData V2 model extension with PromisesPackage,
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.Package,
openui5-smart-mockserveradded to the atlasUI5 MockServer extension generating mock data with Faker.jsPackage,
openui5-touradded to the atlasOpenUI5 control library for guided app toursPackage,
openui5-validatoradded to the atlasOpenUI5 library validating view fields against JSON schemaPackage,
Real Pro-Code Development with Joule StudiopublishedA Devtoberfest 2026 AI-track session that runs one agent build across both of Joule Studio's paths. Playing a procurement manager, one presenter states the intent in the browser, answers the clarifying questions, watches the fit-gap analysis name the S/4HANA APIs the use case needs, and pushes the intent and requirements document to GitHub; the other clones it and carries on in a terminal, logging in with the jl command line against her landscape URL and running its init command to fetch Joule Studio's skills for OpenCode. From there the coding agent writes the specification, the discovered API specifications, the MCP translation and the agent's Python file with its model configuration and evaluation scenarios, which is the edge to Agent tooling; the skills themselves, which SAP says not to edit but which a developer may add to, are the edge to Agent guidance.Talk,
srbinfoandsupportjsadded to the atlasA JavaScript library that shows a UI5 dialog with application details such as device, resolution, browser zoom, app version and last commit.Package,
srbjsloggeradded to the atlasA browser JavaScript logger whose log, warn and error calls write prominent output to the console, loaded into a UI5 app through index.html or the manifest's resources.Package,
Supply Chain Rescueadded to the atlasCAP and SAPUI5 demo of recovery from a supply disruptionSample,
UI5 Toolsadded to the atlasVS Code extension to serve, proxy, build and deploy UI5 projectsIDE extension,
UI5 Views, Reimagined: Type-Safe TSX for a Modern Dev ExperiencepublishedA Devtoberfest 2026 session on @ui5-community/jsx-runtime, the incubation project that lets a UI5 view be written as TSX: XML-like markup that the TypeScript compiler checks against the control's own types and a Babel plugin turns into the constructor calls UI5 already makes. The edge to the runtime rests on the session's own description, which gives the project's documentation site as the session's documentation. The TypeScript support edge holds because that is the session's subject — per-property checking, completion on every attribute, renames that carry through a view, and typed event objects that remove the casts — alongside what stays unchanged: string and expression bindings, controllers, routing and i18n, and XML views living beside TSX ones in the same app. The build edge rests on the setup, where ui5-tooling-transpile is given the JSX transform in ui5.yaml; the walkthrough then builds a bookshop app on a CAP OData service and names what is still missing, UI flexibility and native HTML among it.Talk,
ui5-antaresadded to the atlasSAPUI5 library generating OData V2 metadata-based dialogs and pagesPackage,
ui5-cc-timerbuttonadded to the atlasUI5 control library with a button that delays enabling or showingPackage,
ui5-control-generatoradded to the atlasCommand line generator of UI5 custom controls from htmlGenerator,
ui5-deployeradded to the atlasUI5 Tooling module deploying Fiori/UI5 apps to SAP systemsCLI,
ui5-i18n-excel-converteradded to the atlasCLI converting UI5 i18n properties files to Excel and backCLI,
ui5-middleware-destinationadded to the atlasUI5 Tooling middleware proxying destinations and neo-app.json routesBuild tool,
ui5-middleware-oidcadded to the atlasUI5 dev server middleware adding an OpenID Connect loginBuild tool,
ui5-middleware-route-proxyadded to the atlasUI5 server middleware proxying route prefixes to a backendBuild tool,
ui5-space-webcomponent-libraryadded to the atlasUI5 library wrapping a UI5 Web Components package, step by stepSample,
ui5-space-webcomponent-packageadded to the atlasStep-by-step UI5 Web Components package in TypeScriptSample,
ui5-task-cachebuster-indexingadded to the atlasUI5 builder task preparing build output for the cachebusterBuild tool,
ui5-task-dts-generatoradded to the atlasUI5 builder task generating d.ts type declarationsBuild tool,
ui5-task-minifieradded to the atlasUI5 builder task minifying HTML, CSS and JSON filesBuild tool,
ui5-task-transpile-genadded to the atlasUI5 builder task transpiling ES6 to ES5 with BabelBuild tool,
ui5pluginadded to the atlasSAPUI5 extension for Visual Studio CodeIDE extension,
ui5plugin-linteradded to the atlasCommand-line linter for UI5 classes, XML views and i18n filesCLI,
ui5plugin-parseradded to the atlasnpm library parsing SAPUI5 and project UI5 class metadataPackage,
vitest-environment-ui5added to the atlasVitest environment running UI5 unit tests in Node.jsPackage,
vscode-ui5-api-referenceadded to the atlasVS Code side bar view of the SAPUI5 and OpenUI5 API referenceIDE extension,
vscode-ui5-language-assistantadded to the atlasVS Code extension for SAPUI5 and OpenUI5 XML views and manifestIDE extension,
vscode-ui5-odata-mock-generatoradded to the atlasVS Code extension generating OData mock data from service metadataIDE extension,
wdio-qunit-serviceadded to the atlasWebdriverIO service running QUnit test pagesPackage,
Concircleadded to the atlasPerson,
@satiroglu/kaevlinks, type properties, requires revisedThe dependency the entry could not point at before. @ui5/linter is pinned at 1.23.7 in the npm record's dependencies and the README states "Integrates the official @ui5/linter in a restricted child process", so the edge is the maker's own statement; the for sentence carries the conditions the rule reference puts on the adapter rather than on the dependency, which ships with every install. Written now because the artifact exists to point at: it was not in the graph when this entry was drafted, and the prose link in what_it_solves moves from the repository address to the entry with it.CLI,
@ui5-community/jsx-runtimedescription, requires[external:babel-plugin-transform-react-jsx], identity, type properties revisedThe type owns the key for a package (CONCEPT-038) and the record stated nothing, which reads as "does not say" while the README's repository layout says of this package "Publishable to npm." and the package README's install step is "pnpm add @ui5-community/jsx-runtime". The sibling packages in the same monorepo are each marked "Not published" and state no distribution.Package,
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.Sample,
Authenticationecosystems revisedui5-middleware-oidc was staged in intake-20261019-bestofui5 under ui5-build-tooling because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware.Capability,
Destinationsecosystems revisedui5-middleware-destination was staged in intake-20261019-bestofui5 under ui5-build-tooling; its drafter left out a destinations edge because this capability was not open on the UI5 door. The UI5 reading comes from the README of SAP's backend-proxy-middleware.Capability,
Editor supportecosystems revisedUI5 Language Assistant, SAP's VS Code extension for UI5 XML views and manifest.json, and the SAPUI5 Extension by iljapostnovs were staged in intake-20261019-bestofui5 with this concern as their best fit, and the capability was not open on the UI5 door. The UI5 reading comes from the UI5 Language Assistant README.Capability,
generator-ui5-react-nestentry revisedListed on bestofui5.org and not yet in the atlas. Read from the repository README (main branch) and the npm record for 1.0.14 (Apache-2.0, author Aydin Ozcan, depends on yeoman-generator ^5.7.0). README sentences used: "Unlike traditional solutions that rely on iframes"; "UI5Nest control integration with Workzone or Fiori Launchpad (on-prem) is seamless."; "You can deploy to HTML5 Repository like you do it with your UI5 application."; "The scaffolded React application uses Vite,"; "generator-ui5-react-nest scaffolds the necessary files and configurations for managed router." The when_not_to_use sentence rests on the README's statements that it opts for JavaScript, that react-router-dom is not included in the generated project and that UI5 Web Components are left out.Generator,
Input validationecosystems revisedopenui5-validator was staged in intake-20261019-bestofui5 under ui5-data-binding because this capability was not open on the UI5 door. The UI5 reading comes from the OpenUI5 pages on data types and validation messages.Capability,
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.Capability,
Lintingcoverage by ecosystem revisedUI5 linter (@ui5/linter) and ui5plugin-linter were staged in intake-20261019-bestofui5 with provides edges here, so the note that the graph holds no UI5 linter no longer holds and a community linter is present. The UI5 linter README was read again on 2026-10-19.Capability,
Loggingecosystems revisedSRBJSLogger and openui5-error-collector were staged in intake-20261019-bestofui5 with no capability edge, because this capability was not open on the UI5 door. The UI5 reading comes from the sap/base/Log API documentation and the OpenUI5 Logging and Tracing page.Capability,
secondsky/sap-skillstype properties, flavors revisedRead today in the two plugins that answer the CAP and the UI5 door, which the ABAP pass had not opened. The sap-cap-capire skill's frontmatter states that it covers Node.js and Java runtimes, so CAP's two flavors rest on the maintainer's sentence where the entry previously answered in both by the serves-another-door fallback, which is the same reading off an absence. The sapui5 skill's frontmatter names freestyle apps and Fiori elements apps in one clause, so freestyle is stated, and fiori-elements moves onto that sentence from the README line about which request activates sap-fiori-tools, which said what triggers a plugin rather than what it covers. Nothing read names UI5 Web Components, so that flavor stays unstated. Stating freestyle changes an answer: the entry answered no there while it stated one UI5 flavor and now answers yes, which a reader comparing that flavor's options will see. The ABAP pair is unchanged.Skill,
Seed dataecosystems revisedvscode-ui5-odata-mock-generator and openui5-smart-mockserver were staged in intake-20261019-bestofui5 under ui5-testing; the first one's drafter noted that seed-data fit better but was not open on the UI5 door. The UI5 reading comes from the OpenUI5 mock server pages and SAP's ui5-middleware-fe-mockserver README.Capability,
srbinfoandsupportjsentry revisedListed on bestofui5.org and absent from the atlas. The npm description, "A JS library that shows a UI5 dialog with application details such as device, resolution, browser zoom, app version, and last commit.", and the README's manifest.json configuration name the stack. No provides edge: no capability on the UI5 door covers support or diagnostic information.Package,
srbjsloggerentry revisedListed on bestofui5.org and absent from the atlas. Entered on the README's motivation sentence, "I wanted to better separate the log outputs of our UI5 applications" (excerpt), and its UI5 setup steps; the npm description alone, "SRB logging library for javascript", names no stack. No provides edge: the logging capability lists no UI5 door.Package,
UI5 Views, Reimagined: Type-Safe TSX for a Modern Dev Experienceexplains, summary and sources revisedThe session is about the runtime the atlas holds, and the entry named it only as "the incubation project". Its own description gives the project's documentation site as the session's documentation, "Documentation: https://ui5-community.github.io/jsx-runtime/", which is the docs address of artifact:ui5-community-jsx-runtime, and that page carries the same label the session uses for the project, Incubation. The description sentence is added as a source and the summary names and links the runtime instead of pointing at it. The two edges already recorded are unchanged, and so are the claims about what the session shows: the quotes behind them were re-read on 2026-10-19. The session's own repository, github.com/petermuessig/devtoberfest2026-jsxruntime, is named in the same description and is not in the graph, so it is not an edge here.Talk,
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.Package,
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.Package,
ui5-fe-mockserver-tutorialtype properties, requires revisedThe README's Prerequisites tell the reader to clone and run that CAP project before starting, and the fact was already in what_it_solves with no edge under it. artifact:marianfoo-ui5-call-action was a pending draft when this entry was written and is published now, so the plain link in the prose became a graph link in the same pass, as did ui5-middleware-odata-recorder.Sample,
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.CLI,
ui5-tooling-transpiledescription revisedFound while assessing artifact:ui5-community-jsx-runtime, which requires this extension at version 3.12 or later for exactly that option: the record described the transpile step and said nothing about JSX, so the dependency was visible from one side only. The sentence rests on this package's own README, which says of the option that it "includes the `@babel/plugin-transform-react-jsx` into Babels plugin configuration to transform JSX/TSX syntax into JavaScript" (read 2026-10-19). The version the option arrived in is not stated there, so it stays on the requiring edge where the sentence that gives it lives, and nothing here names the runtime, which this README does not mention.Build tool,
ui5pluginentry revisedListed on bestofui5.org as ui5plugin and not yet in the atlas. Read from the repository README and package.json (name ui5plugin, displayName SAPUI5 Extension, version 1.21.1, Apache-2.0, engines vscode ^1.86.0) and the Marketplace page (identifier iljapostnovs.ui5plugin, description "Extension for working with UI5 projects"). The npm name ui5plugin is unpublished, so no npm link. No part_of edge: the README says the extension uses the parser and linter packages, which is a dependency and not a statement that they are parts of it. No capability for editor support on the UI5 door exists, so only linting is claimed.IDE extension,
ui5plugin-linterentry revisedListed on bestofui5.org and not yet in the atlas. Read from the repository README (https://github.com/iljapostnovs/ui5plugin-linter): "Command Line Linter for UI5 based projects."; the install, --rmcache and --format commands; the JS/TS, XML and properties checks; and "It is possible to add config for ui5plugin-parser as well." The npm record for 1.17.1 gives the bin ui5linter, Apache-2.0 and the ui5plugin-parser 1.10.1 dependency. It is a different tool from SAP's UI5 linter (github.com/UI5/linter), which the graph does not hold as an artifact.CLI,
ui5plugin-parserentry revisedListed on bestofui5.org and not yet in the atlas. Read from the repository README (https://github.com/iljapostnovs/ui5plugin-parser): "Parser package for UI5 based projects"; "Initialization process reads the metadata of standard SAPUI5 classes and parses all projects in CWD"; "UIClass will have class metadata such as fields, methods, properties, aggregations, associations, events etc."; "Primarely used by ui5plugin-linter package and Visual Studio Code SAPUI5 Extension"; "nested projects are not supported anymore"; and the npm record for 1.10.1 (Apache-2.0, author Ilja Postnovs). No provides edge: the README describes a parser, and none of the capabilities in the graph is a parsing library. Distribution through npm rests on the registry record alone, since the README gives no install command.Package,
Werkbankprovides revisedWhat Werkbank adds for ABAP, CAP and UI5 is its catalog of development skills; the workspace itself is not specific to any of those stacks. Agent workspaces is narrowed back to BTP.Desktop app,
Sun 18
8 changes
openui5-cameraadded to the atlasUI5 control for live camera preview and PNG capturePackage,
openui5-passwordadded to the atlasOpenUI5 password input with strength scoring and rulesPackage,
SAP Developers MCPadded to the atlasHosted MCP server of developers.sap.com tutorials and missionsMCP server,
ui5-cap-serverside-rendering-demoadded to the atlasDemo CAP bookshop with server-rendered UI5 viewsSample,
Show 4 more
ui5-lib-visualizationadded to the atlasUI5 control library wrapping C3.js charts as ui5.viz controlsPackage,
UI5Xadded to the atlasUI5 library of eight composite controls under the ui5x namespacePackage,
Tiago Almeidaadded to the atlasPerson,
SAP Developers MCPentry revisedNEIGHBOURS §5.1 named the hosted MCP as a companion to index as an artifact, and the graph had no entry for it. ecosystem: umbrella because its content covers SAP technologies across stacks (llms.txt names ABAP Cloud, CAP, Fiori, HANA Cloud and integration) and no single door holds it. No read_only: the anonymous mounts are read-only, but the signed-in tier writes progress (complete_step). No tool_count: the quickstart and the API page list different tools per mount. The site also serves a GraphQL API, not recorded as an interface here for want of a page read. /mcp/homepage is left out of the description: the quickstart lists it as anonymous and the API page as signed-in.MCP server,
Sat 17
88 changes
@abap2ui5/embed-controladded to the atlasUI5 custom control that runs an abap2UI5 app inside a host appPackage,
abap2UI5 frontend-webcomponentadded to the atlasabap2UI5 frontend rendering with UI5 Web ComponentsPackage,
abap2UI5 Layout Editoradded to the atlasDrag-and-drop UI5 view editor that writes an abap2UI5 app classWeb tool,
abap2UI5 protocoladded to the atlasVersioned specification of the abap2UI5 roundtrip protocolPractice,
Show 84 more
abap2UI5/samples-controlsadded to the atlasUI5 Demo Kit samples rebuilt as abap2UI5 appsSample,
custom-controlsadded to the atlasThirteen custom UI5 controls for abap2UI5 appsPackage,
custom-controls-customeradded to the atlasTemplate repository for own UI5 artefacts served to abap2UI5Sample,
launchpad-kpiadded to the atlasPuts a number from an abap2UI5 app on a Fiori launchpad tilePackage,
SAP-samples/digital-manufacturing-extension-samplesadded to the atlasSamples for the six extension types of SAP Digital ManufacturingSample,
A ChatGPT-like chat app built with modern SAP technologies (CAP, SAPUI5) – Part 1/3explains 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).Blog,
A ChatGPT-like chat app built with modern SAP technologies (CAP, SAPUI5) – Part 2/3explains 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).Blog,
A ChatGPT-like chat app built with modern SAP technologies (CAP, SAPUI5) – Part 3/3explains 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).Blog,
Agentic Engineering for SAP BTP Extensionsexplains 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).Reference architecture,
App hostingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
Authenticationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
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).Blog,
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).Blog,
Building an Attachment Upload and Download Solution Using UploadSetwithTable Controlexplains 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).Blog,
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).Blog,
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).Blog,
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).Blog,
Building Secure SAPUI5 Applications: Best Practices for Developersexplains 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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
Change promotiondescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.abap. Maintainer-requested scope audit.Capability,
Configure Journal Entry Posting Approval from Store Template in Build Process Automationexplains 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).Blog,
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).Blog,
Create Automated System Tests for SAP Cloud Application Programming Model Projectsexplains 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).Tutorial,
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).Blog,
Custom controls and librariesdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
debug a CAP app with UI5 TypeScript UI component with VS 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).Blog,
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).Blog,
Develop a Full-Stack CAP Application Following SAP BTP Developer's Guideexplains 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).Workshop,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Reference architecture,
Evaluating SAP’s new MCP servers: UI5, CAP, and Fiori tools in practiceexplains 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).Blog,
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).Blog,
Extend Upload Set to Fiori Elements and utilize Document Management 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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
From SEGW and Legacy UI5 to RAP with ARC-1explains 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).Blog,
Github Copilot VSCode - My Own SAP Development Rulesexplains 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).Blog,
How I Use AI for Development and Why Context Mattersexplains 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).Blog,
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).Blog,
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).Blog,
Integrate Document Information Extraction into UI5 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).Blog,
Integrated frontend dev servername, description revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Launchpad and site contentdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.btp. Maintainer-requested scope audit.Capability,
Launchpad pluginsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
Lintingdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Media Handling in SAP CAPM – Backend and Frontend Implementationexplains 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).Blog,
Migrate your code with UI5 linter – Autofix has landedexplains 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).Blog,
OData to outcomes—Build AI-enabled SAP Fiori apps using SAP Fiori elementsexplains 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).Talk,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
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).Blog,
SAP Fiori Tools Update – First Release of the SAP Fiori MCP Server for Agentic AIexplains 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).Blog,
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).Blog,
The Complete Guide to Calling Actions in UI5 with Custom 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).Blog,
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).Blog,
Touch operationdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
TypeScript supportdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
UI5 AI Features library is now an npm Packageexplains 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).Blog,
UI5 Has Entered the Chat: Building Interactive MCP Apps for SAPexplains 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).Blog,
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).Blog,
Unlocking Efficiency: Leveraging SAP BTP Document Management Service in Fiori Applications # 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).Blog,
Upload attachments in a Freestyle UI5 and CAP appexplains 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).Blog,
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).Blog,
Useful CAP CDS and Fiori Commands to Accelerate Development and 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).Blog,
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).Blog,
Web Components interopdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.ui5. Maintainer-requested scope audit.Capability,
Why SAP Cloud Identity Matters for SAP Task Center: It’s About Trust and Global User IDexplains 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).Blog,
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).Blog,
Fri 16
4 changes
open-steamgateadded to the atlasLocal ABAP server serving /IWBEP/ OData v2 without an SAP systemApp,
Ajay Sorengadded to the atlasPerson,
hristotsolevadded to the atlasPerson,
SAP Tutorialsadded to the atlasPerson,
Thu 15
20 changes
Agentic Engineering for SAP BTP ExtensionspublishedAn agent harness coordinates code generation across isolated Git worktrees, using a skills registry, SAP CAP MCP Server, Fiori MCP Server and UI5 Web Components MCP Server for development context. The diagram shows LiteLLM as a model proxy in front of SAP AI Core, while automated checks and review gate the generated changes. The worked scenario is CAP-based extensions on BTP, with specifications written before generation and reusable skills governed across teams.Reference architecture,
Werkbankadded to the atlasLocal desktop workspace for AI conversations with SAP connectorsDesktop app,
Mario Ponceadded to the atlasPerson,
@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.Package,
Show 16 more
Agent access to your codeframing by ecosystem revisedBeside Agent access to your systems, the ABAP door read as two names for one thing. This one is about the code, development objects reached through ADT; that one is about business data and operations. The atlas maintainer's decision.Capability,
Agent guidancecoverage by ecosystem, framing by ecosystem, facets, coverage by flavor, framing by flavor revisedskillOverflow entered on 2026-09-18, after this flavor was assessed, serves the UI5 door and states no flavor, so by the flavor rule it answers in all of them. Its own skill list names SAPUI5 data binding, custom controls, i18n and testing and nothing about the component library, so it is reported as a fallback rather than read as a community presence here. Saying so is what keeps core-only honest beside the options the page lists.Capability,
Authenticationcoverage by ecosystem, facets, framing by ecosystem revisedThe paragraph counted two services while seven entries stand behind the door, the router and the Cloud Connector among them, so it told a reader the door was smaller than it is.Capability,
DanKromp/skillOverflowprovides revisedThe entry's own prose said the collection covers UI5 and Fiori work and the edge cited only the total count. The UI5 pass needed to know what that coverage is, because this entry states no flavor and so answers in all of a door's flavors; the two rows name the skills the fallback rests on, which is what the capability's freestyle and web-components readings now cite.Skill,
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.Capability,
karma-ui5-transpilelifecycle, provides[capability:ui5-testing], description revisedThe README calls the karma-ui5 plugin obligatory and says the configuration is read from it, which is what makes it a prerequisite rather than a companion.Package,
LLM integrationcore coverage, coverage by flavor, framing by flavor, facets revisedTwo questions the options here answer differently and the page could not show. Which models an option reaches is the first fact a reader needs, because all but one of the CAP options are clients of SAP AI Core; whether the response can be streamed decides whether a chat surface is possible at all. Both are scoped to cap: the ABAP, UI5 and BTP options were not read for them in this pass.Capability,
SAP Power for Kiroprovides, description revisedThe entry said it is packaged as a Kiro power and not how it gets there or which Kiro it needs; the README read on 2026-10-15 states both.Skill,
SAP/ui-theme-designer-plugins-for-coding-agentsprovides, description revisedThe plugin's own README read on 2026-10-15 lists parameter inheritance beside component consumption in the design-tokens skill, and the entry said nothing about how the plugin gets in front of an agent. Both are facts a reader needs before the parameter mapping is any use to them.Skill,
secondsky/sap-skillslinks, flavors, requires, provides, description revisedThe same correction as description.what_it_solves, on the edge that carries this artifact's answer to the capability, so the two do not state the repository's evidence model differently. The rewording also removes the two em dashes the prose scan reported in this field.Skill,
UI5 testingcore coverage, coverage by flavor, framing by flavor, facets revisedTwo questions the options' own documentation answers and a reader asks first: which level of the suite a tool is for, and whether it produces a coverage report. Three more were researched and left out. Whether a tool reaches an app served elsewhere would have been stated yes by two options and by nobody as a no, so it would have separated rows by absence, which absence does not mean. The automation libraries a tool drives are named by one option only. Declared maturity is the lifecycle field on the artifact, not a column here.Capability,
ui5-cap-ai-featuresprovides[llm-integration], requires[sap-ai-sdk-orchestration] revisedThe edge read as an unconditional prerequisite while this entry's own when_not_to_use already said the package is an optional peer. The README states it in one sentence, quoted now: a frontend-only install does not need it and a backend project installs it explicitly, which is the distinction a reader deciding what to add to package.json needs. The edge to the HTML5 Application Repository is untouched; nothing was read for it in this pass.CDS plugin,
ui5-test-runnerdescription, provides[capability:ui5-testing] revisedBoth are stated by the documentation in its own words: QUnit pages are labelled unit tests and OPA5 pages integration tests, and coverage is documented for both modes. Version 6 turns coverage off by default, which is a setting and not a change to whether it is available.CLI,
UI5/plugins-coding-agentsprovides, description revisedThe old sentence named one marketplace and pointed at an installation guide without saying what it contains. The plugin READMEs read on 2026-10-15 state three routes, including a Copilot marketplace the entry did not mention, and state that the skills-only route leaves the UI5 MCP server to be installed by hand. That last fact changes what a reader gets, since the entry's own warning already turns on which server reads the project.Skill,
wdio-ui5-servicedescription, provides[capability:ui5-testing], links revisedThe documentation site SAP's own testing page links to as the wdi5 home page, and where the authentication and running pages read for this assessment are published.Package,
Werkbankecosystem revisedThe project homepage describes "A small, curated shelf of MCP servers and SAP development skills." Its own catalog spans ABAP (ARC-1 and ABAP Cloud), CAP (CAP Upgrade), and UI5 skills; the workspace is not specific to one stack. This intake follows the maintainer’s explicit request after the September source sweep passed it over for lacking a workspace capability; that concern now exists as Agent workspaces. The served views describe which users the project-owned install catalog addresses. Werkbank provides the workspace; each selected connector or skill supplies the stack-specific behavior. No SAP implementation capability is attributed to Werkbank itself.Desktop app,
Wed 14
5 changes
@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.Package,
Agent access to your codenormative relevance revisedThe policy's agentic provision reaches every server that calls ADT for an agent; it was stated on arc-1 alone and as unsourced prose in several boundaries.Capability,
Attachmentscoverage by ecosystem revisedThe five citations and four links to FileUploader.ts and UploadCollection.ts used the organisation the project has left, which now answers only as a redirect. Both files were opened at the new address on 2026-10-14 and carry the sentences quoted here, so every claim and every quote stands as written and only the addresses and their titles moved; the checked dates stay at the day each quote was last read in full.Capability,
LLM integrationcoverage by flavor revisedThe PromptInput page no longer carries the sentence this rested on. Read again on 2026-10-14 it states "The @ui5/webcomponents-ai package is under development and considered experimental - components' APIs are subject to change. Furthermore, the package supports Horizon themes only", with no version marker in it. The since-2.0 claim had no second source, so it goes rather than stand unsourced; the experimental state and the Horizon-only limit stay, in the words the page now uses, which are the words coverage_by_ecosystem.ui5 already quoted. The flavor's own assessment of who provides it was not redone, so assessed_at stands.Capability,
Show 1 more
TypeScript supportcoverage by flavor revisedThe library is an entry in the graph and provides this capability, so both paragraphs name it by its package name and link the entry, which the 2026-09-14 reasons above said did not exist yet. The two outward addresses they used are the organisation the project has left: github.com/SAP/ui5-webcomponents redirects to github.com/UI5/webcomponents. The React wrapper is not an entry, so it keeps an outward link, at the address its own published package names, github.com/UI5/webcomponents-react. No claim changed: the typescript-support page still reads "TypeScript Support is enabled for both component development and component consumption" and still dates stable definitions to 1.19.0, read again on 2026-10-14. Who provides the capability was not surveyed again, so the state and assessed_at stand.Capability,
Mon 12
7 changes
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 annotations 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 Studio from the published OData 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.Blog,
AyhamTadded to the atlasPerson,
leoirudayamadded to the atlasPerson,
prajnaparmitaadded to the atlasPerson,
Show 3 more
SaranyaSampathadded to the atlasPerson,
Talari Hari Kumaradded to the atlasPerson,
Knowing the maintenance status of a releaseentry revisedDrafted with sap-support-radar and pam-mcp-server, the first umbrella artifacts (ADR-0063), which had no concern to attach to: mcp-servers is serving an application one built, agent-systems-access reaches into a running SAP system, and documentation is first-party docs made searchable. On the ABAP, CAP and UI5 doors because each has a published SAP answer of its own: the Product Availability Matrix, capire's release schedule and the SAPUI5 version overview. BTP is left out: its services name plans and regions rather than releases, and no page was read that states a maintenance period for one. core-only on every door because SAP publishes the answer and no door holds an option of its own; the umbrella entries count into no door's coverage by construction.Capability,
Sun 11
3 changes
Build your first agent with Joule Studio in a pro-code waypublishedThe command line interface of Joule Studio, which the atlas holds as @sap/joule-work-dev-cli-early-adopters, carries an agent from a structured intent through generated product requirements documentation and wired APIs to a deployment on Joule Studio's SAP-managed runtime, in one guided flow. SAP's abstract names the stages of that pipeline and promises working code at the end; what the generated requirements and APIs look like is not described. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Charan Ravikumar, Evgenii Skrebtcov, Maria Kondratyeva and Simon Endres, written here from SAP's abstract; the recording is not yet published.Talk,
Extending SAP Autonomous SuitepublishedExtensibility across SAP Autonomous Suite: AI-enabled development in SAP Build solutions, the ABAP Cloud model among them, as the way extensions are designed, generated and deployed, and a direction for making extensions ready for agentic AI. The abstract names the suite, SAP Build and the ABAP Cloud model and no single feature, so the edges are to Extensibility, the concern, and to SAP Build Code, the SAP Build solution held here in which Joule generates and deploys development; which other SAP Build solutions the session shows is not stated. A TechEd 2026 session (Tuesday 27 October, Berlin), presented by Alexander Rother and Khaled MUSILHY, written here from SAP's abstract; the recording is not yet published.Talk,
OData to outcomes—Build AI-enabled SAP Fiori apps using SAP Fiori elementspublishedA Fiori elements app built through SAP's MCP servers: the OData V4 service comes from the MCP server for RAP, which the atlas holds as the ADT MCP Server, or from @cap-js/mcp-server for CAP, and the UI from @sap-ux/fiori-mcp-server, with annotations and actions added before the app is tied to SAP's AI features. Agent access to your code on both the service and the UI side; SAP's abstract names the servers and the steps and says nothing about which AI features or which agent host. A TechEd 2026 session (Thursday 29 October, Berlin), presented by Benedikt Schoelch, Sebastian Steinhauer, Sebastian Werner and Stefan Engelhardt, written here from SAP's abstract; the recording is not yet published.Talk,
Sat 10
1 change
Reading Between the Lines: Under-Documented Fiori Elements Capabilities in SAPUI5 1.149publishedReads SAPUI5 1.149's framework source, not its release notes, to show Fiori Elements shifting side-effect refresh, AI field placeholders and multi-user drafting from controller extensions into what the backing service annotates. Event-driven SideEffects push over a WebSocket channel through @cap-js-community/websocket, while Draft handling gains ABAP RAP's live field locking on CAP Node.js through Sören Leibach's own cap-collaborative-draft plugin. Both rest on Fiori annotations such as Common.SideEffects and CollaborativeDraft.enabled, which the frontend reads rather than requiring a manifest flag.Blog,
Fri 9
3 changes
scaffold-fiori-ai-bridgeadded to the atlasAgent skill generating a Joule Frontend Actions bridge for UI5 appsSkill,
Agent guidanceecosystems revisedSAP Commerce opened as a product door (docs/concepts/product-doors.md, ADR-0033) and sap-commerce-skill entered behind it with no tile to sit under. Packaged knowledge for the Commerce type system, service layer, ImpEx and OCC API is the same concern the node already holds on four doors, so the key was added rather than the capability forked.Capability,
scaffold-fiori-ai-bridgeentry revisedA repository new to the SAP AI Skills Library registry snapshot of 2026-10-09, with no prior processed record in the collection cache, registering one skill at skills/Scaffold-fiori-ai-bridge. Written from the repository's README and that skill's own SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the UI5 door because the files it reads and writes are a UI5 application's, with Joule and WebMCP as the consumers it generates for.Skill,
Thu 8
3 changes
app-to-app-nav-basadded to the atlasThree Fiori apps wired to one cross-app navigation intentSample,
btp-ui5-show-userinfoadded to the atlasUI5 app reading the signed-in user via launchpad and approuterSample,
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.Sample,
Fri 2
1 change
@satiroglu/kaevdescription, source available, provides revisedkaev.org groups one of its four categories as "Performance & OData" and the rule reference carries the rows behind it, so the tool answers frontend performance as well as linting, by static rule over the project's own code. That capability's reading says the core stops at configuration and the build and sends the reader to the browser's developer tools for the network log, which is the half these rules read statically instead. It was assessed core-only on 2026-09-14 and holds no provides edge from any artifact today, so this is the first one on it, and the state needs the same re-assessment as linting's.CLI,
Thu 1
3 changes
JulianSchSAPfirst recorded in the atlasPerson,
Raj Singhfirst recorded in the atlasPerson,
@satiroglu/kaevdescription revisedThe manifest condition was not the README's claim. It states "The official UI5 Linter adapter currently applies to application roots" and "Integrates the official @ui5/linter in a restricted child process", so the condition came out and the child process went in. All seven sources were re-read on 2026-10-01 and every quote still stands word for word; 0.3.0, published 2026-09-30, is still the latest version, and github.com/satiroglu/kaev returned 404 again.CLI,

Wed 30
3 changes
@satiroglu/kaevadded to the atlasRule-based checker for SAPUI5 and OpenUI5 projectsCLI,
ui5-test-runneradded to the atlasCommand line running UI5 QUnit and OPA tests in parallelCLI,
@satiroglu/kaeventry revisedHanded over as three URLs. Typed cli because what is published is a command with a kaev bin entry, run in a project directory rather than installed into a UI5 build; independent because the site states "Independent developer tool. Not affiliated with or endorsed by SAP." It answers linting on the UI5 door, where the graph already reads UI5 linter as the core's answer and KAEV's own documentation names that linter as something it runs alongside its own rules — and it would be the first provider that capability holds on that door, whose coverage was assessed core-only on 2026-09-14 with a note saying the graph holds no UI5 provider. No repo link: the repository field of the npm record points at github.com/satiroglu/kaev, which still returned 404 on 2026-09-30, so the entry is reachable through npm, the site and the documentation. when_not_to_use states the proprietary licence and the heuristic disclaimer, both from the maker's own pages; identity.license is "Proprietary" because the npm record says "SEE LICENSE IN LICENSE" and the licence page says no open-source licence is granted.CLI,
Tue 29
4 changes
sap-fiori-guidelinesadded to the atlasAgent skill built from the Fiori Design GuidelinesSkill,
ui5-tcode-finderadded to the atlasBrowser page searching SAP transaction codesWeb tool,
sap-fiori-guidelinesentry revisedRead out of the SAP AI Skills Library repository, which the atlas holds as source:sap-ai-skills-library rather than as an artifact because the registry keeps other people's code in their own repositories. This skill is SAP's own code in that repository, so it is entered from its SKILL.md, README and references directory, as plugins/aicore-skills was on 2026-09-25. Hard rule 7: skills are indexed, never authored here.Skill,
ui5-tcode-finderentry revisedStaged with the capability Finding a transaction code, drafted in the same batch because the corpus held no concern for it. ecosystem: abap is a placement rather than a stated fact: the repository is an OpenUI5 and TypeScript application, but its subject is the transaction codes of a classic SAP system and the only stack its features name is SAP GUI for HTML. serves_ecosystems: ui5 rests on the overview sentence naming the T-Codes a UI5 or Fiori project needs. use_as: reference because it is consulted at its own address rather than installed into a project.Web tool,
Mon 28
1 change
Useful CAP CDS and Fiori Commands to Accelerate Development and DeploymentpublishedA command-by-command walkthrough of @sap/cds-dk's cds add and fiori add generators: cds add xsuaa writes an XSUAA security configuration from the CDS model's authorization annotations, and cds add hana together with cds deploy --to hana switches persistence from the default SQLite database to SAP HANA Cloud. cds add mta and fiori add deploy-config, from @sap/generator-fiori, build the Cloud Foundry deployment descriptor together, adding a destination-service block and an xs-app.json that routes the Fiori app's calls through a named destination.Blog,
Sun 27
9 changes
Attachmentscore coverage revisedThe paragraph opened with SAP's packages and never said that the runtime serves a @Core.MediaType element with nothing installed. capire's Serving Media Data page is that built-in layer, cited by pagination-and-streaming and not here. Two deliveries, said apart (docs/concepts/sap-ships-and-documents.md).Capability,
Authenticationcore coverage revisedcapire audit 2026-09-27, proposed pages read once more: the security overview and the product security overview were cited nowhere; the first carries a boundary SAP draws itself.Capability,
Destinationscore coverage revisedP1 backfill 2026-09-27: the paragraph shared no page with the runtime edge because it had no page at all. capire documents the connectivity component under Outbound Authentication; the paragraph now rests on it and on the pages the edge cites.Capability,
Documentationcore coverage revisedPackage pass 2026-09-27: the capability had no paragraph and no source at all.Capability,
Show 5 more
Input validationchanged in, core coverage revisedcapire audit 2026-09-27, proposed pages read a third time: the boundary said the check past the constraints is a before handler of the developer's own, and the two pages that document that handler were cited nowhere; the Node.js page states the order the boundary implies, declarative first.Capability,
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.Capability,
Localizationcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
Loggingcore coverage revisedcapire audit 2026-09-27: a page this capability owns was cited nowhere.Capability,
ui5-middleware-capdescription, provides, alternative to, compat, requires, identity revisedThe package manifest names the author, "author": "Peter Muessig". The entry recorded him as a contributor only, which is the weaker claim; cds-plugin-ui5 in the same repository already carries both.Build tool,
Sat 26
2 changes
Configure Journal Entry Posting Approval from Store Template in Build Process AutomationpublishedWalks through deploying SAP's Journal Entry Posting Approval template from the SAP Build Process Automation Store against an on-premise S/4HANA system that has no Secure Network Connection: destinations for S/4HANA via Cloud Connector, for SAP Document Management service, integration option to hold the approval's supporting documents, and for the BPA service and its SMTP mail. It then swaps the template's SNC action groups for basic-connection BAPI calls and deploys the approval's UI5 applications so the task lands in My Inbox, with a Desktop Agent registered to run the unattended document-check and document-post automations.Blog,
Why SAP Cloud Identity Matters for SAP Task Center: It’s About Trust and Global User IDpublishedA step-by-step configuration walkthrough for wiring SAP Cloud Identity Services as the trust and user-correlation layer behind SAP Task Center: establishing Identity Authentication as the sole trusted identity provider for the BTP subaccount, and generating the Global User ID — carried in the token's user_uuid claim rather than the SAML name identifier — that Task Center uses to match logged-in users to their tasks. It also covers syncing that ID between Microsoft Entra ID, the Identity Directory and SAP S/4HANA through Identity Provisioning jobs, and the principal-propagation trust the cloud connector needs to pass it through to an on-premise task provider.Blog,
Fri 25
22 changes
@concircle/i18n-ai-translatoradded to the atlasCLI translating UI5 i18n.properties files with OpenAICLI,
@marianfoo/ui5-cc-dayjsadded to the atlasUI5 custom control formatting dates with Day.jsPackage,
@sap-ux/createadded to the atlasCommand line for changing features of an existing Fiori projectCLI,
@sap-ux/fe-fpm-writeradded to the atlasWriter of flexible programming model elements into Fiori elements appsPackage,
Show 18 more
@sap-ux/odata-service-writeradded to the atlasWriter that adds an OData service to an existing UI5 projectPackage,
@sap-ux/odata-vocabulariesadded to the atlasOASIS and SAP OData vocabularies with a VocabularyServicePackage,
@sap-ux/ui5-application-writeradded to the atlasWriter of the base structure of a UI5 project from Node codePackage,
cap-materialbom-graphadded to the atlasCAP sample drawing a material BOM as a UI5 network graphSample,
fiori-table-maintenanceadded to the atlasCAP and UI5 app for in-place table maintenance with SmartTableSample,
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 Studio deployment to a working tile in SAP Build Work Zone, standard edition on SAP S/4HANA Cloud Public Edition: 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 Services tenant.Blog,
spreadsheetimporter/sample-full-btpadded to the atlasCAP Risks and Mitigations project with a Spreadsheet Upload buttonSample,
spreadsheetimporter/sample-odata-api-uploadadded to the atlasUI5 app opening the Spreadsheet Importer on on-premise OData servicesSample,
ui5-call-actionadded to the atlasUI5 apps calling CAP OData actions and functions from custom codeSample,
ui5-errorhandler-sampleadded to the atlasTwo UI5 apps consuming one npm package in two waysSample,
ui5-fe-mockserver-tutorialadded to the atlasTen exercises on the Fiori elements mock server middlewareSample,
ui5-plugin-loaderadded to the atlasUI5 Tooling v4 extension that registers other extensionsBuild tool,
ui5-webcomponents-bundleadded to the atlasCustom UI5 Web Components bundle loaded with one script tagPackage,
ui5con24-dev-envadded to the atlaspnpm workspace running CAP, a local launchpad and two UI5 appsSample,
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.Sample,
ui5-errorhandler-sampleentry revisedIts own README states the subject: "This sample shows how to use npm packages", with "How to consume a UI5 AMD style module" and "How to consume a classic js class" as the two examples. That places it on capability:ui5-build-tooling, where artifact:ui5-community-ui5-tooling-modules already sits, rather than anywhere near error handling: the error handler is the payload being consumed and not what the sample teaches. demonstrates rather than provides, because a sample is evidence. compat.runtimes is package.json's @ui5/cli devDependency. The last description sentence is the README's "@marianfoo/ui5-errorhandler": "^0.0.4" set against package.json's "@marianfoo/ui5-cc-errorhandler": "^0.0.1" on main, both read on 2026-09-25. The library itself, marianfoo/ui5-errorhandler, was read in the same batch and not drafted; see the manifest note. GitHub reported this repository as a fork on 2026-09-25 and its README credits easy-ui5 rather than an upstream repository, so no lineage is written here: the fork flag is crawled and lineage needs the maintainer's own sentence.Sample,
ui5-fe-mockserver-tutorialentry revisedSample with use_as reference, following artifact:sap-samples-manage-apis-codejam: a repository of exercises is evidence that something works and never an option to depend on. It demonstrates capability:ui5-testing because that capability's core coverage already names "an OData V2 mock server for a backend stand-in" as what SAP ships, and capability:ui5-build-tooling because the mockserver is registered as UI5 Tooling custom middleware in ui5-mock.yaml. compat.runtimes is the README's Required Tools, "**Node.js** (20 LTS or higher)". @sap-ux/ui5-middleware-fe-mockserver, the middleware being taught, has no entry of its own, so it stands in the prose as a code span and the README's own pointer to SAP/open-ux-odata is linked out. No licence is stated anywhere in the repository, so identity is absent.Sample,
ui5-plugin-loaderentry revisedbuild-tool and capability:ui5-build-tooling for the same reason its four named neighbours carry them: it is registered in the customMiddleware and customTasks blocks of ui5.yaml and does its work inside ui5 serve and ui5 build. compat.runtimes is the README's Requirements section, "**Node.js v18.0.0 or higher**"; identity.license is the README's License section and the npm record, both MIT. No flavors: the README states no UI5 flavor, and absent is not a claim. One discrepancy for an editor rather than the entry: the npm record for ui5-plugin-loader 0.2.0, published 2025-07-23, gives its repository as git+https://github.com/marianzeis/ui5-plugin-loader.git, while the source read here is github.com/marianfoo/ui5-plugin-loader; the npm description, "Auto-mounts UI5 tooling extensions based on manifest JSON files", and the 0.2.x version line both match this README.Build tool,
Wed 23
1 change
The Fourth Way to Go Offline in UI5 (And Why the Service Worker Stays Dumb)publishedReporting on the UI5Con session run by Viktor Sperling and Lars Kissel, the post proposes a fourth offline architecture for a warehouse scanning app: a service worker kept deliberately ignorant of OData, and a JSONModel/IndexedDB layer that does an explicit download, work, submit cycle, queuing local mutations before posting one $batch with a single changeSet at the end of a session. It also works through the alternative v4.ODataModel change-buffer pattern (updateGroupId, submitBatch) and explains why Fiori elements' annotation-driven, live OData V4 interactions resist offline replay. The session-token and XSRF-expiry problem for long offline periods is named as an open gap rather than solved.Blog,
Tue 22
3 changes
@ui5/mcp-serverreleased 0.3.0Setups that rely on MCP roots to keep the server's tools inside the workspace.MCP server,
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).Service,
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.Capability,
Mon 21
1 change
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 Studio 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.Blog,
Sun 20
4 changes
UI5con_2026_MCPAppsadded to the atlasFive MCP servers whose tools return a prebuilt UISample,
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.Capability,
Input validationcore coverage revisedThree independent CAP artifacts carry a provides edge to this capability: sap-cap-validator-plugin (entered 2026-09-18), cds-validate and cap-toolkit (both 2026-09-07). The state said only the core was present. relationship is unassessed: no retrieved document gives the history between them and the core.Capability,
LLM integrationcore coverage revisedThe boundary is kept and made checkable against capire's new AI pages: aicore is documented as the default kind for production and hybrid, and every other documented kind (auto and mock on Node.js, ollama and mocked on Java) is for local runs.Capability,
Sat 19
12 changes
Building Secure SAPUI5 Applications: Best Practices for DeveloperspublishedA developer-facing rundown of secure coding habits for SAPUI5 apps: typed bindings and custom formatters to reject bad input before it reaches a handler, encodeHTML() instead of rendering untrusted HTML, keeping tokens and URLs out of local and session storage, and CSRF token handling on the ODataModel. It sets up linting with ESLint and an eslint-config-ui5 rule set to catch unsafe DOM access, eval calls and unused imports as part of CI, alongside the same input validation instinct: reject invalid input early rather than trust the backend to catch it.Blog,
Migrate your code with UI5 linter – Autofix has landedpublishedUI5 linter v1.12.0 adds an initial autofix, reached with ui5lint --fix, and the post walks through it end to end: the tool first reports a deprecated global reference (sap.ui.model.json.JSONModel), then the fix rewrites it into the equivalent module import and local variable. This first version only handles that one class of deprecation — replacing deprecated globals with imports — with more fix types left for later releases tracked on the tool's GitHub roadmap.Blog,
Alla Volkovfirst recorded in the atlasPerson,
Andreas Roesslerfirst recorded in the atlasPerson,
Show 8 more
michawaifirst recorded in the atlasPerson,
Priyanka Sakundarwarfirst recorded in the atlasPerson,
rayakorenfirst recorded in the atlasPerson,
Sapir Polfirst recorded in the atlasPerson,
Shahar Soelfirst recorded in the atlasPerson,
Spreadsheet Importerfirst recorded in the atlasPerson,
tal-sapanfirst recorded in the atlasPerson,
theming-technical-userfirst recorded in the atlasPerson,
Fri 18
20 changes
@sap-ux/cap-config-writeradded to the atlasWriter module for changing a CAP project's configuration from codePackage,
@sap-ux/i18nadded to the atlasReader and writer for i18n bundles of UI5 or CAP projectsPackage,
DanKromp/skillOverflowadded to the atlasCollection of 41 agent skills, 37 for SAP development tasksSkill,
spreadsheetimporter/packed-deployment-abapadded to the atlasUI5 app template deploying the Spreadsheet Importer once to ABAPSample,
Show 16 more
spreadsheetimporter/sample-adaptation-banksadded to the atlasAdaptation project adding spreadsheet upload to Manage BanksSample,
spreadsheetimporter/sample-adaptation-banks-updateadded to the atlasManage Banks adaptation updating existing records from a spreadsheetSample,
spreadsheetimporter/sample-standaloneadded to the atlasUI5 app opening the Spreadsheet Importer on its ownSample,
ui5-cc-pdfvieweradded to the atlasUI5 custom control rendering a PDF from a base64 data URIPackage,
ui5-cc-spreadsheetimporteradded to the atlasUI5 component adding a spreadsheet upload dialog to Fiori appsPackage,
ui5-lib-diffadded to the atlasHosted app listing changes between SAPUI5 or OpenUI5 versionsWeb tool,
ui5-middleware-odata-recorderadded to the atlasUI5 middleware recording OData traffic as mock server datasetsBuild tool,
ui5-task-btp-manifestadded to the atlasUI5 Tooling task writing the service name into the importer manifestBuild tool,
DanKrompadded to the atlasPerson,
DanKromp/skillOverflowentry revisedDiscovered through the SAP AI Skills Library and represented once at repository level. The registry listed 37 contained skills when checked; the canonical repository contained and documented 41, so the repository count is used for the artifact while both snapshots remain in the crawl record.Skill,
Destinationscore coverage revisedThe earlier assessment rested on every provider being SAP-official and said in its own note that a community alternative appearing would make core-only wrong. cdse is one: it reads the destination from the CAP configuration and makes the call with axios, and it is independent. The samples that demonstrate this capability are unaffected, since a sample is evidence and not an option. The relationship is recorded as unassessed because nothing checked here says how the two came to be present side by side.Capability,
Importing and exporting table datacoverage by ecosystem revisedA UI5 entry now answers the import side: ui5-cc-spreadsheetimporter reads an uploaded spreadsheet in the browser and submits its rows through the app's own OData model. The core side is unchanged: SAP's spreadsheet export documentation still describes export only, so the previous note that no UI5 entry answers the import side is what has moved, not the reading of the core.Capability,
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.Capability,
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.Package,
ui5-lib-diffentry revisedRead out of the marianfoo account listing. capability:documentation reads core-only on the UI5 door on the grounds that every provider there is SAP-published; this is an independent one, so that reading needs reassessing rather than carrying over.Web tool,
ui5-middleware-odata-recorderentry revisedRead out of the marianfoo account listing. Two provides edges because the two halves are different claims: it is a UI5 server middleware, and what it produces is the mock-server dataset that capability:ui5-testing's core coverage already names as the framework's backend stand-in.Build tool,
Thu 17
2 changes
Attachmentscore coverage revisedReplace unsupported migration/UI boundary with sourced implementation limits; keep community additions separate. Add four CAP-scoped comparison questions and preserve other ecosystems/flavors.Capability,
SAP Document Management service, integration optionserves ecosystems revisedAdd CAP to served ecosystems from documented CAP integration; preserve the existing BTP/UI5 contribution and source dates. CAP plugin restrictions do not apply to the service itself.Service,
Tue 15
568 changes
Before You Upgrade S/4HANA: Static UI5 Checks with MCPpublishedA UI5 version upgrade checked against one app by pairing two MCP servers: the ui5_version_diff tool added to mcp-sap-docs, which reads a bundle from ui5-lib-diff downloaded once at setup and filters it by version range, change type, library or query text, and @ui5/mcp-server, whose get_project_info, get_version_info, run_ui5_linter and run_manifest_validation say what the app uses and what fails. Run with a ui5-versions-upgrade.md skill on the legacy app from From SEGW and Legacy UI5 to RAP with ARC-1, from SAPUI5 1.84.59 to 1.147.2, the diff range held 985 deprecations and 961 What's New entries, and the linting and manifest validation narrowed that to findings in this app, among them jQuery.sap.require, synchronous bootstrap, the sap_belize theme, sap.m.MessagePage and an old manifest _version. The checks read the source in a local checkout and never the deployed app, so the report is a first pass: a changelog entry is not proof that a workaround can be deleted, and the app still has to be run and tested.Blog,
Building an Enterprise-Ready SAP AI Agent with Open SourcepublishedA self-hosted chat agent for SAP systems: LibreChat as UI and orchestrator with Entra ID sign-in and SharePoint connected, a local LLM through Ollama, and two MCP servers, mcp-sap-docs for public documentation and the ADT MCP server vibing-steampunk for the system itself. The ADT server runs in its read-only mode under a technical user with display authorisations only, so the agent can find a function module and pull its source, or locate a RAP business object with its behaviour definition and projection view, but cannot change anything. Two workflows show it, explaining what BAPI_DISPUTE_CREATE does in one system and planning a RAP action from a PDF specification, where the generated ABAP is copied into Eclipse by hand; the full setup is in the marianfoo/llm-client-sap-system-integration-sharepoint repository.Blog,
Establish a central inbox with SAP Task CenterpublishedSAP's reference architecture for SAP Task Center 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 UIs. It rests on Cloud Identity Services: 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 Connector for on-premise SAP S/4HANA.Reference architecture,
Finally: An MCP Server for ABAPpublishedAnnounces the ABAP variant of mcp-sap-docs, published at mcp-abap.marianzeis.de for GitHub Copilot's Agent Mode in ADT for Eclipse, which the post names as the trigger, with ABAP knowledge still a recurring problem in the models. Documentation irrelevant to ABAP was removed from the SAP docs server and the ABAP Keyword Documentation, the DSAG ABAP Development Guidelines and the ABAP Style Guide were added, with search reaching past the local index to SAP Community posts and SAP Help. Copilot in Eclipse is where the post puts the weight, because SAP Joule for Developers, ABAP AI capabilities in Eclipse is not available for S/4HANA on-premise systems; an update of 2026-02-05 adds Software Heroes as an online source and an abap_feature_matrix tool that checks feature availability across releases and ABAP Cloud, and the server runs hosted or locally with Node or Docker.Blog,
Show 564 more
From SEGW and Legacy UI5 to RAP with ARC-1publishedThree ARC-1 skills, run in Cursor with Composer-2 against a deliberately rough demo on an S/4HANA 2023 trial system, turn the SEGW service ZDEMO_MIG_PROJECTS_SRV into a managed, draft-enabled RAP business object published as OData V4, replace its ApproveProject function import and its direct UPDATE ... COMMIT WORK with the action approve_project written in EML in local mode, and rebuild the freestyle UI5 JavaScript app once in UI5 TypeScript and once as a Fiori elements list report and object page driven by metadata extensions. What the published transcripts add is how the agent got there: it found the generated MPC class names and the custom logic in DPC_EXT only by reading the system, the skills made it print the extracted model and stop for confirmation before writing, and @ui5/mcp-server, mcp-sap-docs and @sap-ux/fiori-mcp-server each had their own job beside it. The demo is small on purpose, and the post says a productive SEGW service that calls BAPIs, carries custom authorisation logic or supports deep inserts is not solved with one prompt.Blog,
How I Use AI for Development and Why Context MatterspublishedPart one of the AI ABAP development series traces a move from pasting ChatGPT output and error messages back and forth to tools that search, read docs and inspect files themselves, and holds that the context around a model decides more in real projects than benchmark results do. In SAP work the grounding comes from mcp-sap-docs, which brings SAP Help, GitHub repositories, style guides and DSAG guidelines into the session, and context for changing a class also means the tables it uses, the classes it calls and similar implementations. Agentic autonomy is a slider set per project, with the time saved on typing moved into planning and review, and the post stops before ABAP: SAP's MCP servers for UI5, CAP and Fiori (@ui5/mcp-server, @cap-js/mcp-server, @sap-ux/fiori-mcp-server) sit in off-stack work that git and pipelines already gate, and the harder ABAP case is left to the next part.Blog,
Joule in SAP Build Codeadded to the atlasJoule's generative AI inside SAP Build CodeService,
SAP Build Codeadded to the atlasDevelopment environment on BTP for UI5, Fiori, mobile and CAPService,
SAP Cloud Portal Serviceadded to the atlasRole-based portal sites with pages, apps and widgetsService,
SAP Continuous Integration and Deliveryadded to the atlasPredefined CI/CD pipelines for SAP development projectsService,
SAP Document Management service, integration optionadded to the atlasAPIs and a UI5 component for document management in appsService,
SAP Web IDE Full-Stackadded to the atlasIDE service on SAP BTP for SAPUI5, Fiori and full-stack appsService,
UI flexibility serviceadded to the atlasKey-user adaptation and personalisation for UI5 apps on SAP BTPService,
UI5 Has Entered the Chat: Building Interactive MCP Apps for SAPpublishedMCP Apps let an MCP tool point at a ui:// resource that a compatible host renders in a sandboxed iframe, and the post walks through the five samples of UI5con_2026_MCPApps, built with Mike Zaschka for UI5con, from a plain HTML time tool through UI5 Web Components and UI Integration Cards to UI5 lint findings from @ui5/mcp-server and an ARC-1 transport review. In the samples the model selects the tool and does not generate the interface, the prebuilt kind of generative UI, and the subject is the server side of MCP servers: register the resource, link it from the tool's _meta.ui.resourceUri, return text content as a fallback beside structuredContent, call callServerTool() only for tools of the server that owns the app, and send a message to the host when another server such as ARC-1 has to act. It stops at the host, whose support differs by client and whose iframe sandbox is not a complete security model, and Joule support for MCP Apps could not be verified at the time of writing.Blog,
50gYfirst recorded in the atlasPerson,
a-z-ivanovfirst recorded in the atlasPerson,
abap2UI5first recorded in the atlasPerson,
abap2UI5-addonsfirst recorded in the atlasPerson,
Abhishek Rawatfirst recorded in the atlasPerson,
actions-userfirst recorded in the atlasPerson,
Aditya Bhatiafirst recorded in the atlasPerson,
Adrian Bobevfirst recorded in the atlasPerson,
Adrian Martenfirst recorded in the atlasPerson,
Aisling Noonefirst recorded in the atlasPerson,
Ajinkya Patilfirst recorded in the atlasPerson,
AKlic-sapfirst recorded in the atlasPerson,
Aleksandar Terzievfirst recorded in the atlasPerson,
Aleksandr Suvorovfirst recorded in the atlasPerson,
Alex Engelfirst recorded in the atlasPerson,
alex-avizov-sapfirst recorded in the atlasPerson,
Alexandar Mitsevfirst recorded in the atlasPerson,
Alexanderfirst recorded in the atlasPerson,
Alexander Deutschmannfirst recorded in the atlasPerson,
Alexander Rießfirst recorded in the atlasPerson,
AlexXiongfirst recorded in the atlasPerson,
Ali Schmalzhaffirst recorded in the atlasPerson,
Alice V.first recorded in the atlasPerson,
Alina Govoruhinafirst recorded in the atlasPerson,
Amar Ubhefirst recorded in the atlasPerson,
Amiram Wingartenfirst recorded in the atlasPerson,
Amiya Ranjan Dasfirst recorded in the atlasPerson,
Andis Redmansfirst recorded in the atlasPerson,
Andreas Eckerfirst recorded in the atlasPerson,
Andreas Kunzfirst recorded in the atlasPerson,
Anilafirst recorded in the atlasPerson,
AnKirilinfirst recorded in the atlasPerson,
Ankur Mongafirst recorded in the atlasPerson,
Annemarie Frankfirst recorded in the atlasPerson,
AnnFrfirst recorded in the atlasPerson,
annikarosselfirst recorded in the atlasPerson,
antoniymfirst recorded in the atlasPerson,
Anupam Medirattafirst recorded in the atlasPerson,
Arley Triana Morinfirst recorded in the atlasPerson,
Arnaud Buchholzfirst recorded in the atlasPerson,
Arnaud Buchholzfirst recorded in the atlasPerson,
Artemis Coderfirst recorded in the atlasPerson,
Arthur Trauterfirst recorded in the atlasPerson,
asenbozhilov1first recorded in the atlasPerson,
AshwinKumarBolarfirst recorded in the atlasPerson,
Attila Borosfirst recorded in the atlasPerson,
Austin Devinefirst recorded in the atlasPerson,
avasilev-sapfirst recorded in the atlasPerson,
avh-sapfirst recorded in the atlasPerson,
awolfishfirst recorded in the atlasPerson,
AxelWarnerfirst recorded in the atlasPerson,
Barbara Hartelfirst recorded in the atlasPerson,
BeastiWfirst recorded in the atlasPerson,
Ben Brennanfirst recorded in the atlasPerson,
benderskiy-sapfirst recorded in the atlasPerson,
Benedikt Schölchfirst recorded in the atlasPerson,
Benedikt Volkefirst recorded in the atlasPerson,
Benjamin Reimfirst recorded in the atlasPerson,
bhumika196first recorded in the atlasPerson,
Bhuwan Rawatfirst recorded in the atlasPerson,
Biser Miloshevfirst recorded in the atlasPerson,
bistradolapchievafirst recorded in the atlasPerson,
blaesiusfirst recorded in the atlasPerson,
Boghyon Hoffmannfirst recorded in the atlasPerson,
Boris Dafovfirst recorded in the atlasPerson,
Boyan Rakilovskifirst recorded in the atlasPerson,
bpukalskyifirst recorded in the atlasPerson,
Brian Bernardfirst recorded in the atlasPerson,
Brian Bogovichfirst recorded in the atlasPerson,
Brijesh Lochanfirst recorded in the atlasPerson,
broksyfirst recorded in the atlasPerson,
Cahit Gürgücfirst recorded in the atlasPerson,
Carson Rodriguesfirst recorded in the atlasPerson,
ch0k1first recorded in the atlasPerson,
Chetan Mahajanfirst recorded in the atlasPerson,
Christianfirst recorded in the atlasPerson,
Christian Georgifirst recorded in the atlasPerson,
Christian Geyerfirst recorded in the atlasPerson,
Christian Grailfirst recorded in the atlasPerson,
Christian Kolbowskifirst recorded in the atlasPerson,
Christian Montoyafirst recorded in the atlasPerson,
Christian Neufirst recorded in the atlasPerson,
Christian Pätzoldfirst recorded in the atlasPerson,
Christoph Gollmickfirst recorded in the atlasPerson,
Christoph Krämerfirst recorded in the atlasPerson,
ChristophLauxfirst recorded in the atlasPerson,
ChristophMarotzkefirst recorded in the atlasPerson,
ChristophSzabofirst recorded in the atlasPerson,
Christos Koutsiarisfirst recorded in the atlasPerson,
Christos Koutsiarisfirst recorded in the atlasPerson,
Cian Morrinfirst recorded in the atlasPerson,
Ciarafirst recorded in the atlasPerson,
Claus Hunsenfirst recorded in the atlasPerson,
Clemens Maierfirst recorded in the atlasPerson,
clementlemarc-certuafirst recorded in the atlasPerson,
Colin Otcherefirst recorded in the atlasPerson,
colindoherty1first recorded in the atlasPerson,
Constantin Lebrechtfirst recorded in the atlasPerson,
CPielkafirst recorded in the atlasPerson,
Csaba K Molnárfirst recorded in the atlasPerson,
d.ramadanfirst recorded in the atlasPerson,
d027183first recorded in the atlasPerson,
D067839first recorded in the atlasPerson,
Daniel Langfirst recorded in the atlasPerson,
Daniel Nanovskifirst recorded in the atlasPerson,
Daniel Nowakfirst recorded in the atlasPerson,
Daniel Petersfirst recorded in the atlasPerson,
Daniel Shterevfirst recorded in the atlasPerson,
Danyal Aslamfirst recorded in the atlasPerson,
Dario Zilocchifirst recorded in the atlasPerson,
David Klugfirst recorded in the atlasPerson,
David O'Connorfirst recorded in the atlasPerson,
David Reynoldsfirst recorded in the atlasPerson,
David Sooterfirst recorded in the atlasPerson,
Davis Voicescuksfirst recorded in the atlasPerson,
dchangamdfirst recorded in the atlasPerson,
Denise Nepraunigfirst recorded in the atlasPerson,
dependabot-supportfirst recorded in the atlasPerson,
DerGuteWolffirst recorded in the atlasPerson,
Deyan Yanakievfirst recorded in the atlasPerson,
dhanwin89first recorded in the atlasPerson,
Dianafirst recorded in the atlasPerson,
Diana Pazhevafirst recorded in the atlasPerson,
Diana Shtilianovafirst recorded in the atlasPerson,
Dimitar Dimitrovfirst recorded in the atlasPerson,
Dimitar Fenerskifirst recorded in the atlasPerson,
Dimo Uzunovfirst recorded in the atlasPerson,
Dirk Teufelfirst recorded in the atlasPerson,
DJ Adamsfirst recorded in the atlasPerson,
DMihaylovafirst recorded in the atlasPerson,
Dobrin Dimchevfirst recorded in the atlasPerson,
Dobromira Boychevafirst recorded in the atlasPerson,
Domifirst recorded in the atlasPerson,
Dominic Holzwarthfirst recorded in the atlasPerson,
Dominik Feiningerfirst recorded in the atlasPerson,
Dominik Heimfirst recorded in the atlasPerson,
Dominik Schreiberfirst recorded in the atlasPerson,
Dominik Storkfirst recorded in the atlasPerson,
Donal Tobin (SAP)first recorded in the atlasPerson,
Dr. Markus Königsteinfirst recorded in the atlasPerson,
Dr. Thomas Chadzelekfirst recorded in the atlasPerson,
drascsfirst recorded in the atlasPerson,
Duc Vo Ngocfirst recorded in the atlasPerson,
Dusan Sachafirst recorded in the atlasPerson,
Eddiefirst recorded in the atlasPerson,
Edouard Ouinfirst recorded in the atlasPerson,
Edrilan Berishafirst recorded in the atlasPerson,
edvardas-kireilisfirst recorded in the atlasPerson,
ej612first recorded in the atlasPerson,
Ekansh Saxenafirst recorded in the atlasPerson,
Elena Nikolovafirst recorded in the atlasPerson,
Emanuel Bahrfirst recorded in the atlasPerson,
Emmanuel Ferdmanfirst recorded in the atlasPerson,
Emre Cevikfirst recorded in the atlasPerson,
erlethorfirst recorded in the atlasPerson,
eswortmalerfirst recorded in the atlasPerson,
Ethan Jewettfirst recorded in the atlasPerson,
eugenreschfirst recorded in the atlasPerson,
Evdokia Yordanovafirst recorded in the atlasPerson,
evkatsarskifirst recorded in the atlasPerson,
Fabian Reinboldfirst recorded in the atlasPerson,
Fabian Tempelfirst recorded in the atlasPerson,
FabPetefirst recorded in the atlasPerson,
Fan Zoufirst recorded in the atlasPerson,
Fatih Pensefirst recorded in the atlasPerson,
Felix Schubertfirst recorded in the atlasPerson,
Filip Siderovfirst recorded in the atlasPerson,
fionan-SAPfirst recorded in the atlasPerson,
Florian Boffofirst recorded in the atlasPerson,
Florian Vogtfirst recorded in the atlasPerson,
fossabotfirst recorded in the atlasPerson,
Frank Hufnagelfirst recorded in the atlasPerson,
Frank Weigelfirst recorded in the atlasPerson,
fred-ops-at-workfirst recorded in the atlasPerson,
Freddy Jetty Johnsonfirst recorded in the atlasPerson,
fumanjinfirst recorded in the atlasPerson,
FUMINfirst recorded in the atlasPerson,
Gabriel Borgesfirst recorded in the atlasPerson,
galroter-sapfirst recorded in the atlasPerson,
GDamyanovfirst recorded in the atlasPerson,
Geert-Jan Klapsfirst recorded in the atlasPerson,
GeneralDukefirst recorded in the atlasPerson,
georgbischofffirst recorded in the atlasPerson,
Georgifirst recorded in the atlasPerson,
Georgi Hristanovfirst recorded in the atlasPerson,
Georgievafirst recorded in the atlasPerson,
GeraldKrausefirst recorded in the atlasPerson,
GerganaKremenskafirst recorded in the atlasPerson,
gernotkuhrfirst recorded in the atlasPerson,
Gery Mfirst recorded in the atlasPerson,
Gianluca Beilfirst recorded in the atlasPerson,
GnagnoHtmlfirst recorded in the atlasPerson,
Goran Peucfirst recorded in the atlasPerson,
Gregor Wolffirst recorded in the atlasPerson,
Guilherme Dellagustinfirst recorded in the atlasPerson,
Guilherme Segantinifirst recorded in the atlasPerson,
Guillaume des Pommarefirst recorded in the atlasPerson,
Günter Klattfirst recorded in the atlasPerson,
Gustavo Kathfirst recorded in the atlasPerson,
hannaolbfirst recorded in the atlasPerson,
Heiko Ettelbrück (SAP)first recorded in the atlasPerson,
Helmut Tammenfirst recorded in the atlasPerson,
Henrique Mattosfirst recorded in the atlasPerson,
Henry Lifirst recorded in the atlasPerson,
HerzogIgzornfirst recorded in the atlasPerson,
Hitesh Parmarfirst recorded in the atlasPerson,
HouYe Huafirst recorded in the atlasPerson,
Hristo Manchevfirst recorded in the atlasPerson,
Hristo Petrovfirst recorded in the atlasPerson,
Hubert Dreckerfirst recorded in the atlasPerson,
HyeongJunfirst recorded in the atlasPerson,
i033653first recorded in the atlasPerson,
IainSAPfirst recorded in the atlasPerson,
IcelandWarriorfirst recorded in the atlasPerson,
ilhan orhanfirst recorded in the atlasPerson,
Iliana Bobevafirst recorded in the atlasPerson,
Ilya Klopkovfirst recorded in the atlasPerson,
Ingmar Lemkefirst recorded in the atlasPerson,
iot-cparsfirst recorded in the atlasPerson,
Irinafirst recorded in the atlasPerson,
ironmanagerfirst recorded in the atlasPerson,
IvaHristovafirst recorded in the atlasPerson,
Ivaylo Ivanovfirst recorded in the atlasPerson,
Ivaylo Plashkovfirst recorded in the atlasPerson,
IvoSGfirst recorded in the atlasPerson,
J Longfirst recorded in the atlasPerson,
J. Schuppanfirst recorded in the atlasPerson,
Jacek Wozniczakfirst recorded in the atlasPerson,
Jakob Marius Kjaerfirst recorded in the atlasPerson,
Jan Dudafirst recorded in the atlasPerson,
Jan Pilzerfirst recorded in the atlasPerson,
Janik Köppelfirst recorded in the atlasPerson,
Jason Maritzfirst recorded in the atlasPerson,
Jay Barbhaiyafirst recorded in the atlasPerson,
Jens Himmelrathfirst recorded in the atlasPerson,
Jens Wallgrenfirst recorded in the atlasPerson,
Jere Kelonenfirst recorded in the atlasPerson,
Jianrong Yufirst recorded in the atlasPerson,
Jiaweifirst recorded in the atlasPerson,
Jimmy Josephfirst recorded in the atlasPerson,
Joaquin Recio Huertasfirst recorded in the atlasPerson,
Jochen Hörtreiterfirst recorded in the atlasPerson,
Johannes Gluchfirst recorded in the atlasPerson,
Johannes Kolbefirst recorded in the atlasPerson,
John Pattersonfirst recorded in the atlasPerson,
Jonathan Bakerfirst recorded in the atlasPerson,
Jordanfirst recorded in the atlasPerson,
Jorge Sanchofirst recorded in the atlasPerson,
Joshua Slaarfirst recorded in the atlasPerson,
Julian Breukschfirst recorded in the atlasPerson,
Julian Daxfirst recorded in the atlasPerson,
Julian Königfirst recorded in the atlasPerson,
Juri Zeislerfirst recorded in the atlasPerson,
k-schaserfirst recorded in the atlasPerson,
kaiserschmarrnfirst recorded in the atlasPerson,
KaloyanTsv1first recorded in the atlasPerson,
KamalKumarSardiwalfirst recorded in the atlasPerson,
Katrin Polloczekfirst recorded in the atlasPerson,
Kazuhiko Takatafirst recorded in the atlasPerson,
Kevin Edingerfirst recorded in the atlasPerson,
KevinC0210first recorded in the atlasPerson,
Kieran Sukachevinfirst recorded in the atlasPerson,
kitzkanfirst recorded in the atlasPerson,
Klaus Kellerfirst recorded in the atlasPerson,
KleinL31first recorded in the atlasPerson,
Knut Thiesfirst recorded in the atlasPerson,
Konstantin Gogovfirst recorded in the atlasPerson,
korotkovaofirst recorded in the atlasPerson,
Kostas T.first recorded in the atlasPerson,
kranthie-sapfirst recorded in the atlasPerson,
Kristian Kraljicfirst recorded in the atlasPerson,
kskondovfirst recorded in the atlasPerson,
Lars Hvamfirst recorded in the atlasPerson,
Lars Kisselfirst recorded in the atlasPerson,
Lennartfirst recorded in the atlasPerson,
LiamM2004first recorded in the atlasPerson,
LilyanaOviPefirst recorded in the atlasPerson,
logingerfirst recorded in the atlasPerson,
Louise Findlayfirst recorded in the atlasPerson,
Lucafirst recorded in the atlasPerson,
Luca Wunderlichfirst recorded in the atlasPerson,
Lucas da Silva Heimfirst recorded in the atlasPerson,
Ludo Noensfirst recorded in the atlasPerson,
Ludwig Stockbauer-Muhrfirst recorded in the atlasPerson,
Lukas Böhmfirst recorded in the atlasPerson,
Lukas Harbarthfirst recorded in the atlasPerson,
Lukas Heimannfirst recorded in the atlasPerson,
Lukas Theis (MuwuM)first recorded in the atlasPerson,
Lukas Veithfirst recorded in the atlasPerson,
Lyserg-Diethelfirst recorded in the atlasPerson,
Madhu552first recorded in the atlasPerson,
Manuel Blechschmidtfirst recorded in the atlasPerson,
ManuelPastorinifirst recorded in the atlasPerson,
M̷̱̥̳͔̖̠̙͈̫͕͔̳͉̱̣̭̮̠̰̄͊̒̈͛͗̈̇͆͗͆͋̾̋̅ͅͅẠ̴̡̬̭͓̟̠̣̤̓̽͛̋̌̆̆̔́̊̋́͜Ŕ̶͈̹̯̹͈̠̮̰̓̈́̐̊͐̕̕͝C̷̨̡̖̱̭͉̞̗̳͈̩͚̏͛̓̃͂͌̀̆͊̅̃̒̄͐̿̽̚͝first recorded in the atlasPerson,
Marc Bernardfirst recorded in the atlasPerson,
Marcel Schorkfirst recorded in the atlasPerson,
Marcello Urbanifirst recorded in the atlasPerson,
Marco Beierfirst recorded in the atlasPerson,
Marco Chiaradonnafirst recorded in the atlasPerson,
Marco Viethfirst recorded in the atlasPerson,
Marcus Notheisfirst recorded in the atlasPerson,
marcushoepfnerfirst recorded in the atlasPerson,
Maria Dinevafirst recorded in the atlasPerson,
Marian Zeisfirst recorded in the atlasPerson,
Mario Kernichfirst recorded in the atlasPerson,
Marius Augensteinfirst recorded in the atlasPerson,
Marius Freitagfirst recorded in the atlasPerson,
Marius Obertfirst recorded in the atlasPerson,
Mark Schmalefirst recorded in the atlasPerson,
Martinfirst recorded in the atlasPerson,
Martin Januskafirst recorded in the atlasPerson,
Martin Rippelfirst recorded in the atlasPerson,
Martin Schausfirst recorded in the atlasPerson,
Martin Wittmannfirst recorded in the atlasPerson,
martinDaskalovfirst recorded in the atlasPerson,
martinhaeuserfirst recorded in the atlasPerson,
Martotkofirst recorded in the atlasPerson,
Maruf Rasullyfirst recorded in the atlasPerson,
Marvinfirst recorded in the atlasPerson,
Mathias Uhlmannfirst recorded in the atlasPerson,
Matthias Oßwaldfirst recorded in the atlasPerson,
Matthias Schmalzfirst recorded in the atlasPerson,
Matúš Horváthfirst recorded in the atlasPerson,
Mauricio Laufferfirst recorded in the atlasPerson,
Max Reichmannfirst recorded in the atlasPerson,
Max Streifenederfirst recorded in the atlasPerson,
Maxi Dietzfirst recorded in the atlasPerson,
maxi1555first recorded in the atlasPerson,
Maximilian Moehlfirst recorded in the atlasPerson,
maximnaidenovsapfirst recorded in the atlasPerson,
Meghna Senfirst recorded in the atlasPerson,
mehmet-sapfirst recorded in the atlasPerson,
Merlin Beutlbergerfirst recorded in the atlasPerson,
Mert TÜRKOĞLUfirst recorded in the atlasPerson,
mfigueirfirst recorded in the atlasPerson,
Micha Zadikowitschfirst recorded in the atlasPerson,
Michaelfirst recorded in the atlasPerson,
Michael Graffirst recorded in the atlasPerson,
Milen Karmidzhanovfirst recorded in the atlasPerson,
Mio Yasutakefirst recorded in the atlasPerson,
MJ Turnerfirst recorded in the atlasPerson,
mmilko01first recorded in the atlasPerson,
mushegh-sapfirst recorded in the atlasPerson,
Mustafa Mengütayfirst recorded in the atlasPerson,
myordanovfirst recorded in the atlasPerson,
Nabi Zamanifirst recorded in the atlasPerson,
Nafees Ahmedfirst recorded in the atlasPerson,
nafis0077first recorded in the atlasPerson,
NageshwarRaofirst recorded in the atlasPerson,
naid007first recorded in the atlasPerson,
nair-sumeshfirst recorded in the atlasPerson,
Navin Krishnanfirst recorded in the atlasPerson,
Nayden Naydenovfirst recorded in the atlasPerson,
Neta Molchofirst recorded in the atlasPerson,
Nico Schoenteichfirst recorded in the atlasPerson,
Nicolas Lunetfirst recorded in the atlasPerson,
nightcitybladefirst recorded in the atlasPerson,
Nikita B.first recorded in the atlasPerson,
Nikola Anachkovfirst recorded in the atlasPerson,
Nikolay Deshevfirst recorded in the atlasPerson,
Nikolay Hristovfirst recorded in the atlasPerson,
Nikolay Kolarovfirst recorded in the atlasPerson,
Nikolay Vankovfirst recorded in the atlasPerson,
nikolay-lyutov-sapfirst recorded in the atlasPerson,
Nikoleta Ivanovafirst recorded in the atlasPerson,
niyapfirst recorded in the atlasPerson,
NLeenaRajfirst recorded in the atlasPerson,
NStoichkovfirst recorded in the atlasPerson,
oblomov-devfirst recorded in the atlasPerson,
Oliver at evosightfirst recorded in the atlasPerson,
Oliver Muellerfirst recorded in the atlasPerson,
Olivers Berzsfirst recorded in the atlasPerson,
Oliwerfirst recorded in the atlasPerson,
Ondřej Šebelafirst recorded in the atlasPerson,
OpenUI5 Botfirst recorded in the atlasPerson,
Pavanfirst recorded in the atlasPerson,
Pavel Kornevfirst recorded in the atlasPerson,
PavelNikitsiukfirst recorded in the atlasPerson,
Peder Hveem Alsvikfirst recorded in the atlasPerson,
Petar Dimovfirst recorded in the atlasPerson,
Peter Muessigfirst recorded in the atlasPerson,
Peter Skelinfirst recorded in the atlasPerson,
Peter Trebingfirst recorded in the atlasPerson,
PeterBuchholzfirst recorded in the atlasPerson,
PetrStribrnyfirst recorded in the atlasPerson,
Petya Markovafirst recorded in the atlasPerson,
petyabegovskafirst recorded in the atlasPerson,
Petyo Kostakovfirst recorded in the atlasPerson,
Phil Mitchellfirst recorded in the atlasPerson,
Philipp Prachtfirst recorded in the atlasPerson,
philippthielefirst recorded in the atlasPerson,
Pieter Janssensfirst recorded in the atlasPerson,
Pipfirst recorded in the atlasPerson,
pkinkelfirst recorded in the atlasPerson,
pksinsikfirst recorded in the atlasPerson,
Plamen Ivanovfirst recorded in the atlasPerson,
PlamenAngelovfirst recorded in the atlasPerson,
Platon Rovfirst recorded in the atlasPerson,
pramod-jayaram92first recorded in the atlasPerson,
Preetam Kajal Routfirst recorded in the atlasPerson,
pwasemsapfirst recorded in the atlasPerson,
QA-lerfirst recorded in the atlasPerson,
qkt2first recorded in the atlasPerson,
radostinaTsfirst recorded in the atlasPerson,
RainerLiebischfirst recorded in the atlasPerson,
ReshmaRVarmafirst recorded in the atlasPerson,
resitamasfirst recorded in the atlasPerson,
Richard Chanfirst recorded in the atlasPerson,
rimmlermfirst recorded in the atlasPerson,
Robby Manisfirst recorded in the atlasPerson,
Robert Jakobsfirst recorded in the atlasPerson,
Robin Reebfirst recorded in the atlasPerson,
Romanfirst recorded in the atlasPerson,
Romans Koldunsfirst recorded in the atlasPerson,
Ruben Tuiderfirst recorded in the atlasPerson,
Ryan Murphyfirst recorded in the atlasPerson,
rygiolfirst recorded in the atlasPerson,
Sabine Lossfirst recorded in the atlasPerson,
Sam Zhaofirst recorded in the atlasPerson,
sanat-thukralfirst recorded in the atlasPerson,
SAPfirst recorded in the atlasPerson,
SAP Architecture Centerfirst recorded in the atlasPerson,
sap-lhfirst recorded in the atlasPerson,
Saurabh Kumarfirst recorded in the atlasPerson,
schlakfirst recorded in the atlasPerson,
Scott Cameronfirst recorded in the atlasPerson,
Scott McGheefirst recorded in the atlasPerson,
Sebastian Mahrfirst recorded in the atlasPerson,
Sebastian Riedfirst recorded in the atlasPerson,
Sebastian Wennemersfirst recorded in the atlasPerson,
Sebastian Wolffirst recorded in the atlasPerson,
Sergefirst recorded in the atlasPerson,
Sergei Hallerfirst recorded in the atlasPerson,
SHAFFNER7first recorded in the atlasPerson,
Sharmavkshfirst recorded in the atlasPerson,
Shen Linfirst recorded in the atlasPerson,
Silke Ariansfirst recorded in the atlasPerson,
Silke Spangfirst recorded in the atlasPerson,
simlinfirst recorded in the atlasPerson,
Simon Coenfirst recorded in the atlasPerson,
Simon Karolusfirst recorded in the atlasPerson,
Simona Rangelovafirst recorded in the atlasPerson,
Siyana Todorovafirst recorded in the atlasPerson,
Sören Leibachfirst recorded in the atlasPerson,
SpielerB82first recorded in the atlasPerson,
SRKPendyalafirst recorded in the atlasPerson,
stabpdfirst recorded in the atlasPerson,
stanfirst recorded in the atlasPerson,
Stanley-78first recorded in the atlasPerson,
stbodurovfirst recorded in the atlasPerson,
Stefan Blambergfirst recorded in the atlasPerson,
Stefan Dimitrovfirst recorded in the atlasPerson,
Stefan Engelhardtfirst recorded in the atlasPerson,
Stefan Hipfelfirst recorded in the atlasPerson,
Stefan Minchevfirst recorded in the atlasPerson,
Stefan Schreckfirst recorded in the atlasPerson,
Stefania Santimbreanfirst recorded in the atlasPerson,
Steffen Fröhlichfirst recorded in the atlasPerson,
Stoehrfirst recorded in the atlasPerson,
Stoyanfirst recorded in the atlasPerson,
stoyanovskifirst recorded in the atlasPerson,
StSchefirst recorded in the atlasPerson,
Sumeet Mehrafirst recorded in the atlasPerson,
sumitverma03first recorded in the atlasPerson,
Sushant Priyadarshifirst recorded in the atlasPerson,
Sven Benderfirst recorded in the atlasPerson,
Sven Bernhardfirst recorded in the atlasPerson,
SvetoslavSpasovfirst recorded in the atlasPerson,
Svilen Darvenyashkifirst recorded in the atlasPerson,
swendlandtfirst recorded in the atlasPerson,
tabris87first recorded in the atlasPerson,
TaldykinVyacheslavfirst recorded in the atlasPerson,
tamara-fuchsfirst recorded in the atlasPerson,
Tanbarifirst recorded in the atlasPerson,
Tanya Kostadinovafirst recorded in the atlasPerson,
TanyaMedvedevafirst recorded in the atlasPerson,
TeodorTaushanovfirst recorded in the atlasPerson,
Tereza Chobanovafirst recorded in the atlasPerson,
testojsfirst recorded in the atlasPerson,
Thai Pangsakulyanontfirst recorded in the atlasPerson,
Theo Sunfirst recorded in the atlasPerson,
Thomas Frischholzfirst recorded in the atlasPerson,
Thomas Jungfirst recorded in the atlasPerson,
Thomas Koetterfirst recorded in the atlasPerson,
Thomas-Neuhauserfirst recorded in the atlasPerson,
ThomasMarzzfirst recorded in the atlasPerson,
Thorsten Hochreuterfirst recorded in the atlasPerson,
thuyboehmfirst recorded in the atlasPerson,
Tino Butzfirst recorded in the atlasPerson,
tkolmackafirst recorded in the atlasPerson,
Tobifirst recorded in the atlasPerson,
Tobias Hofmannfirst recorded in the atlasPerson,
Tobias Queckfirst recorded in the atlasPerson,
tobias-oetzelfirst recorded in the atlasPerson,
Todor Nikolovfirst recorded in the atlasPerson,
Todor Stoyanovfirst recorded in the atlasPerson,
Tomfirst recorded in the atlasPerson,
Tom Pauluschfirst recorded in the atlasPerson,
Tom Schmelzerfirst recorded in the atlasPerson,
tomb81first recorded in the atlasPerson,
Tommyfirst recorded in the atlasPerson,
Tommy Vinhfirst recorded in the atlasPerson,
Toni Ivanisevicfirst recorded in the atlasPerson,
Tsanislav Gatevfirst recorded in the atlasPerson,
Tsvetelina Petrovafirst recorded in the atlasPerson,
Tuan Dinhfirst recorded in the atlasPerson,
UBSusmithafirst recorded in the atlasPerson,
UI5first recorded in the atlasPerson,
UI5 Communityfirst recorded in the atlasPerson,
Ullas Hollafirst recorded in the atlasPerson,
UserAbcd1234first recorded in the atlasPerson,
uttamypfirst recorded in the atlasPerson,
Uwe Reederfirst recorded in the atlasPerson,
Uwe Schwerkfirst recorded in the atlasPerson,
vadson71first recorded in the atlasPerson,
ValeriCernyhfirst recorded in the atlasPerson,
Valkanisterfirst recorded in the atlasPerson,
valtsonfirst recorded in the atlasPerson,
vberschfirst recorded in the atlasPerson,
Viktor Sperlingfirst recorded in the atlasPerson,
Vilim Mikicfirst recorded in the atlasPerson,
Vinay K Nfirst recorded in the atlasPerson,
vinayhospetefirst recorded in the atlasPerson,
Vincent Escalierfirst recorded in the atlasPerson,
Vitalii Komarfirst recorded in the atlasPerson,
Vitor Eduardo Seifert Bazzofirst recorded in the atlasPerson,
Vivek Gowdafirst recorded in the atlasPerson,
Vladislav Tasevfirst recorded in the atlasPerson,
Vladislavs-Silins-SAPfirst recorded in the atlasPerson,
Volker Buzekfirst recorded in the atlasPerson,
Wayne g.n.Seofirst recorded in the atlasPerson,
Wenqian2024first recorded in the atlasPerson,
Wolfram Woernerfirst recorded in the atlasPerson,
Wouter Lemairefirst recorded in the atlasPerson,
Xexerfirst recorded in the atlasPerson,
Yanaki Yanakievfirst recorded in the atlasPerson,
yanaminkovafirst recorded in the atlasPerson,
Yarloy037first recorded in the atlasPerson,
Yavor Ivanovfirst recorded in the atlasPerson,
yavor8410first recorded in the atlasPerson,
Yuping Zuofirst recorded in the atlasPerson,
Zale-Bfirst recorded in the atlasPerson,
Zdravko Georgievfirst recorded in the atlasPerson,
Ziyang Lifirst recorded in the atlasPerson,
Zornitsa Stoyanovafirst recorded in the atlasPerson,
Zsoltfirst recorded in the atlasPerson,
Zwaartekrachtfirst recorded in the atlasPerson,
zzchao-1999first recorded in the atlasPerson,
Agent access to your codecoverage by ecosystem, framing by ecosystem, coverage by flavor, framing by flavor revisedThe HTTP resources the flavor is restricted to now have a page.Capability,
Attachmentsecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the concern is answered by a repository service with folders and versions, which differs from the CAP, UI5 and ABAP framings of a file stored against an entity or a business object.Capability,
Editor supportecosystems, coverage by ecosystem, framing by ecosystem revisedOn BTP the editor is a hosted service rather than a language server or an Eclipse plugin, which is what the CAP and ABAP framings describe.Capability,
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.Capability,
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.Capability,
TypeScript Sheriff: How can I use TypeScript in the SAP ecosystem? (Part 2 of 3)explains, summary revisedRewritten to say what the post states about each framework, so the new edges hold in the summary, and to drop the sentence on parts one and three that the series section now shows with their decline notes.Blog,
Mon 14
70 changes
@sap/joule-work-dev-cli-early-adoptersadded to the atlasPro-code CLI for building and deploying Joule Studio solutionsCLI,
@ui5/webcomponentsadded to the atlasSAP's UI elements as standard custom elementsPackage,
approuteradded to the atlasShowcase for dev-approuter in front of two UI5 appsSample,
btp-launchpad-ui-samplesadded to the atlasUI5 projects on designing apps for SAP Launchpad ServiceSample,
Show 66 more
cds-bookshopadded to the atlasCAP bookshop showing UI5 development with cds-plugin-ui5Sample,
create-easy-ui5added to the atlasnpm-init wrapper for the Easy-UI5 Yeoman generatorGenerator,
create-wdi5added to the atlasnpm initializer adding wdi5 testing to an existing UI5 appGenerator,
generator-easy-ui5added to the atlasYeoman meta-generator for scaffolding UI5 projectsGenerator,
generator-ui5-addadded to the atlasYeoman generator for UI5 tooling-extension projectsGenerator,
generator-ui5-appadded to the atlasEasy-UI5 generator scaffolding a new UI5 applicationGenerator,
generator-ui5-controladded to the atlasYeoman generator for UI5 custom controls distributed via npmGenerator,
generator-ui5-libraryadded to the atlasEasy-UI5 generator scaffolding a new UI5 libraryGenerator,
generator-ui5-library-webcadded to the atlasYeoman generator for UI5 libraries wrapping UI5 Web ComponentsGenerator,
generator-ui5-projectadded to the atlasYeoman generator for UI5 projects holding several applicationsGenerator,
generator-ui5-ts-appadded to the atlasEasy-UI5 generator scaffolding a TypeScript UI5 applicationGenerator,
generator-ui5-ts-app-fcladded to the atlasGenerator for a TypeScript UI5 FlexibleColumnLayout app on ODataGenerator,
generator-ui5-ts-libraryadded to the atlasEasy-UI5 generator scaffolding a TypeScript UI5 libraryGenerator,
generator-ui5-wdi5added to the atlasYeoman generator scaffolding wdi5 test configuration into a UI5 appGenerator,
karma-ui5-transpileadded to the atlasKarma preprocessor transpiling UI5 sources via ui5-tooling-transpilePackage,
openui5-fhir-sample-appadded to the atlasUI5 app built with openui5-fhir against FHIR servicesSample,
s4hana-avc-ui-extension-templateadded to the atlasTemplate and mock runtime for S/4HANA Variant Configuration UIsSample,
SAP-samples/fundamental-ngx-sample-appsadded to the atlasAngular performance-review demo of Fundamental NGX componentsSample,
teched2025-CA262added to the atlasTechEd 2025 hands-on on SAPUI5 front-end performanceSample,
ui5-appadded to the atlasUI5 app carrying 18 UI5 CLI extensions in one configurationSample,
ui5-bookshop-vieweradded to the atlasUI5 app consuming the cds-bookshop server via ui5-middleware-capSample,
ui5-libadded to the atlasSample setup for developing a UI5 librarySample,
ui5-mdc-json-tutorialadded to the atlasUI5 tutorial on sap.ui.mdc controls with a JSON modelSample,
ui5-moduleadded to the atlasCustom UI5 control packaged as an npm packageSample,
ui5-p13n-tutorialadded to the atlasUI5 tutorial adding p13n Engine personalisation to a custom tableSample,
ui5-tsappadded to the atlasTypeScript UI5 app consuming custom UI5 CLI extensions togetherSample,
ui5-tsapp-webcadded to the atlasTypeScript UI5 app consuming @ui5/webcomponentsSample,
ui5-tslibadded to the atlasTypeScript UI5 library with build, linting and Karma testsSample,
ui5-tsmoduleadded to the atlasTypeScript UI5 module consumed through ui5-tooling-modulesSample,
ui5-webcomponents-ngx-sampleadded to the atlasDemo app for @ui5/webcomponents-ngx, UI5 Web Components for AngularSample,
ui5con-2026-a11y-hands-onadded to the atlasUI5con 2026 workshop fixing accessibility defects in a UI5 appSample,
ui5con-2026-chrome-built-in-aiadded to the atlasUI5 workshop adding Chrome's on-device AI APIs to a TypeScript appSample,
ui5con-2026-fiori-building-blocksadded to the atlasSession building a travel dashboard with Fiori elements and SAPUI5Sample,
ui5con-2026-ui5-linter-workshopadded to the atlasUI5con workshop taking a legacy UI5 app to a clean UI5 linter reportSample,
wdf2025-fiori-innov-day-building-blocksadded to the atlasFiori Innovation Day session building a travel dashboardSample,
Agent access to your codecoverage by flavor, framing by flavor revisedThe UI5-door providers of this capability — @ui5/mcp-server and fiori-mcp — state freestyle and fiori-elements, never web-components. SAP's @ui5/webcomponents-mcp-server does carry the web-components flavor but provides documentation, not this capability: its four tools serve the library's own API and guides and never open the project in front of the agent. No provider states web-components for agent-code-access, and the concern itself is not structurally absent from the flavor, so unmapped reads truer than not-applicable.Capability,
Agent guidancecoverage by flavor, framing by flavor revisedThe door-level framing already says the Web Components skills ship inside the library and version with it; a flavor paragraph names the two skills the flavor's provider actually carries rather than repeating the door's sentence.Capability,
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.Capability,
Attachmentscoverage by flavor, framing by flavor, coverage by ecosystem, ecosystems, framing by ecosystem revisedThe ABAP door opened with Generic Object Services and AttachmentCommentODataService, and what the concern is there differs from the CAP and UI5 framings: the file belongs to a business object in the system rather than to an entity a service defines.Capability,
Authenticationecosystems revisedabap_jwt_generator, abapOAuthAzure, abap2oauth2, abapNTLM and abap-aws-sigv4 in this batch authenticate an ABAP system to external APIs with JWT, OAuth 2.0, NTLM and AWS Signature v4, and abap-pwnedpasswords checks a password against a breach list, so the concern is decided on the ABAP door.Capability,
Build and dev-server toolingcoverage by flavor revisedui5-tooling-modules is the only UI5-door artifact that states web-components in its flavors for capability:ui5-build-tooling, and it is community-org; @ui5/cli states freestyle and fiori-elements only. SAP's own UI5 Web Components documentation puts the actual build and bundle step in the host framework's own bundler, not in UI5 Tooling.Capability,
Change promotioncoverage by flavor revisedABAP Cloud's transport story is SAP's own: gCTS through the Manage Software Components app in the BTP ABAP environment, and Export/Import Software Collection in S/4HANA Cloud Public Edition. The one provider found on the ABAP door for this capability, abapToC's ZTOC transaction, is a classic transport-of-copies tool built as an SAP GUI transaction and states no flavor, so no community option is present in ABAP Cloud.Capability,
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.Capability,
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.Capability,
Document extractionecosystems, coverage by ecosystem, coverage by flavor revisedGrep of data/artifacts for capability:document-extraction finds only SAP Document AI, ecosystem btp, serving cap and carrying no flavors — no UI5 provider, own or serving, states web-components, so core-only and not-applicable are both closed. Checked ui5.github.io/webcomponents: the ui5-file-uploader control opens a file picker and exposes selected files through a read-only property, moving a file the same way SAPUI5's UploadCollection does without reading it, so the flavor's own position is the same unmapped reading as the door's rather than not-applicable.Capability,
Documentationcoverage by flavor revisedThe only UI5-ecosystem artifact that states web-components in its flavors is ui5-webcomponents-mcp-server, sap-official, and no other UI5-ecosystem provider of this capability names the flavor at all — core-only per the reading rule. framing_by_flavor was left unset: framing_by_ecosystem.ui5 already describes this same artifact, and it already reads as the web-components flavor's own paragraph rather than a cross-flavor one, so a second copy would restate it rather than say something different.Capability,
Editor supportecosystems revisedWidened to ABAP: Xexer/my-ide-actions adds IDE actions to ADT, and DevEpos/abap-tags-backend and DevEpos/abap-call-hierarchy are the ABAP backends of two Eclipse plugins. The description lost its CDS wording, which moved to framing_by_ecosystem.cap.Capability,
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.Capability,
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.Capability,
Generatorsecosystems revisedAbapGenerator scaffolds ABAP objects from a template package. Thirteen UI5 Community repositories generate UI5 projects or add to one: Easy-UI5 and its npm init wrapper, generators for apps, libraries, controls and tooling extensions, and create-wdi5 and generator-ui5-wdi5, which add wdi5 to an existing app.Capability,
Input validationecosystems revisedabap-data-validator checks dates, times, e-mail addresses, GUIDs and other types from ABAP code, alone or against a table of rules, and abapDomCheck checks a structure against its domains' fixed values. Both are for data that never passes a screen.Capability,
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.Capability,
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.Capability,
Lintingecosystems revisedui5con-2026-ui5-linter-workshop, a SAP-samples workshop in this batch, runs UI5 linter over a legacy UI5 app, which is this concern on the UI5 door. The UI5 reading comes from the UI5 linter README.Capability,
LLM integrationecosystems, coverage by flavor, framing by flavor, coverage by ecosystem, description revisedThe description named a CAP service, which is false on the UI5, BTP and ABAP doors this capability is in. Only the subject of the call changed.Capability,
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.Capability,
Loggingecosystems revisedNine repositories log from ABAP: six wrap the application log or its ABAP Cloud API, one logs function module calls to its own table, and two send entries to Fluentd, Graylog or Loki.Capability,
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.Capability,
Seed dataecosystems revisedabapFaker generates localised fake names, addresses and other values in ABAP for development and tests, so the concern has an answer behind the ABAP door.Capability,
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.Capability,
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.Capability,
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.Capability,
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.Capability,
TypeScript supportcoverage by flavor, framing by flavor revisedThe freestyle description is about a published types package and a UI5 build step; neither applies here, since the Web Components and their React wrapper carry their own definitions.Capability,
UI5 testingcoverage by flavor revisedwdi5's own docs define a locator as something that identifies a UI5 control, and UI5 Web Components' own README describes the library as usable with any web framework rather than built on OpenUI5; none of the ui5-door providers of this capability (openui5-core, ui5-community-wdi5, ui5-community-wdi5-cucumber, ui5-community-ui5-journey-recorder) state web-components on a flavors or provides edge.Capability,
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.Capability,
Sun 13
58 changes
babel-preset-transform-ui5added to the atlasBabel transformer from modern ES or TypeScript to UI5 module syntaxBuild tool,
fiori-fullscreen-pluginadded to the atlasFiori launchpad plugin adding a fullscreen toggle buttonSample,
generator-ui5-flp-pluginadded to the atlasEasy-UI5 generator scaffolding a Fiori Launchpad pluginGenerator,
generator-ui5-ts-flp-pluginadded to the atlasEasy-UI5 generator for a TypeScript Fiori launchpad pluginGenerator,
Show 54 more
hacking-away-sampleappadded to the atlasUI5con 2022 demo of an end-to-end TypeScript UI5 setup with CAPSample,
SAP-samples/adaptation-project-exercisesadded to the atlasUI5Con workshop on building SAPUI5 Adaptation ProjectsSample,
SAP-samples/ai-seamless-integrationadded to the atlasUI5 Web Components AI patterns embedded in an OpenUI5 appSample,
SAP-samples/fiori-mcp-server-hands-onadded to the atlasExercises building a Fiori elements app from Figma via MCP serversSample,
SAP-samples/teched2022-DT181added to the atlasTechEd 2022 workshop mixing SAPUI5 with Fiori elements building blocksSample,
SAP-samples/teched2025-CA261added to the atlasTechEd 2025 workshop driving a Fiori elements app from Figma via MCPSample,
SAP-samples/ui5-deploymentsadded to the atlasUI5 app deployed to Cloud Foundry via three approuter setupsSample,
SAP-samples/ui5-flexibility-easy-key-user-adaptationadded to the atlasUI5con 2025 tutorial on SAPUI5 flexibility and key user adaptationsSample,
SAP-samples/ui5-typescript-control-libraryadded to the atlasUI5 control library written in TypeScript with full tooling setupSample,
SAP-samples/ui5-typescript-helloworldadded to the atlasSmall UI5 app with a guide to its TypeScript setup from scratchSample,
SAP-samples/ui5-typescript-tutorialadded to the atlasTutorial on TypeScript for UI5 apps via a weather-lookup appSample,
SAP-samples/ui5con-2025-theming-workshopadded to the atlasUI5con 2025 workshop on theming with UI5's CSS custom propertiesSample,
SAP-samples/ui5con-2026-fiori-mcp-serveradded to the atlasUI5con tutorial on Fiori elements apps with AI assistants and MCPSample,
SAP-samples/uxc-integrationadded to the atlasUI5 Web Components shell bar and navigation inside an OpenUI5 appSample,
ui5-cap-todoadded to the atlasTodo app with CAP and SAPUI5 in TypeScript over OData V4Sample,
ui5-cc-chartadded to the atlasUI5 custom control wrapping Chart.js for line chartsPackage,
ui5-cc-mdadded to the atlasUI5 custom control rendering Markdown to HTMLPackage,
ui5-fontawesome-libadded to the atlasUI5 library adding Font Awesome icon sets to sap-icon://Package,
ui5-icon-exploreradded to the atlasLive icon browser for the ui5-fontawesome-lib icon setSample,
ui5-journey-recorderadded to the atlasChrome extension generating OPA5 or wdi5 tests from recorded journeysGenerator,
ui5-middleware-approuteradded to the atlasUI5 CLI middleware proxying the dev server through @sap/approuterBuild tool,
ui5-middleware-capadded to the atlasUI5 CLI middleware running a CDS server inside the UI5 dev serverBuild tool,
ui5-middleware-hmradded to the atlasExperimental UI5 middleware for hot module replacementBuild tool,
ui5-middleware-iasyncadded to the atlasUI5 middleware syncing interactions across browsers over websocketBuild tool,
ui5-middleware-indexadded to the atlasUI5 middleware serving a chosen welcome page at the root pathBuild tool,
ui5-middleware-oneloginadded to the atlasUI5 middleware logging in with Playwright and reusing the sessionBuild tool,
ui5-middleware-serveframeworkadded to the atlasUI5 middleware serving a locally built UI5 frameworkBuild tool,
ui5-middleware-servestaticadded to the atlasUI5 middleware serving static resources from a path or npm packageBuild tool,
ui5-middleware-ui5added to the atlasUI5 middleware including one UI5 application in anotherBuild tool,
ui5-middleware-webjarsadded to the atlasUI5 middleware serving static resources from JAR files (WebJars)Build tool,
ui5-middleware-websocketadded to the atlasWebSocket support for Express-based dev servers such as UI5'sBuild tool,
ui5-monorepo-showcaseadded to the atlaspnpm workspace developing a UI5 app, library and plugin togetherSample,
ui5-task-cachebusteradded to the atlasUI5 builder task cachebusting standalone UI5 applicationsBuild tool,
ui5-task-copyrightadded to the atlasUI5 builder task appending copyright headers to source filesBuild tool,
ui5-task-flatten-libraryadded to the atlasUI5 builder task flattening library output for SAP NetWeaverBuild tool,
ui5-task-i18ncheckadded to the atlasUI5 builder task checking XML views for missing i18n textsBuild tool,
ui5-task-minify-xmladded to the atlasUI5 builder task minifying XML views and fragmentsBuild tool,
ui5-task-pwa-enableradded to the atlasUI5 builder task turning a UI5 app into a progressive web appBuild tool,
ui5-tooling-lessadded to the atlasUI5 CLI extension compiling Less files into CSSBuild tool,
ui5-tooling-stringreplaceadded to the atlasUI5 CLI extension for string replacement during the buildBuild tool,
ui5-tooling-transpileadded to the atlasUI5 CLI extension transpiling code during the UI5 buildBuild tool,
ui5-touch-controlsadded to the atlasUI5 control library of sized sap.m controls and touch inputsPackage,
ui5-ts-modules-showcaseadded to the atlasShowcase of consuming npm libraries from a TypeScript UI5 appSample,
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-plugin 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.Blog,
wdf2025-fiori-innov-day-mcp-serveradded to the atlasFiori Innovation Day exercises on Fiori elements with MCP serversSample,
wdi5-cucumberadded to the atlaswdi5 plugin for Cucumber-style BDD tests on Fiori Elements appsPackage,
wdi5-fe-selectorsadded to the atlaswdi5 selectors for locating controls in Fiori Elements appsPackage,
wdi5-workshopadded to the atlasTwo wdi5 workshops from UI5con 2022 and Devtoberfest 2022Sample,
SAP Samplesadded to the atlasPerson,
Attachmentsname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Destinationsname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Documentationdescription revisedWidened rather than forked into abap-code-documentation: producing a document of a custom package is the same concern from the writing side. The ABAP coverage moved from community-only to core-and-community because ADT's ABAP Doc export is the core's answer for custom code. Done so abap-doc (staged in intake-20260913-mariokernich) can provide it.Capability,
Generatorsname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Seed dataname revisedThe map draws every capability as one tile, and a name that spells out its second half ran to three lines at a size nobody could read. The id already carried the short name; the name now matches it. The concern is unchanged: the description and the coverage say what it spans.Capability,
Fri 11
1 change
mcp-sap-docsdescription revisedCorrected against the README: its offline-sources table lists seventeen repositories, abap-docs-standard through wdi5.MCP server,
Thu 10
11 changes
SAP Power for Kiroadded to the atlasSAP skills for the Kiro IDESkill,
sap-odata-exploreradded to the atlasRust CLI and desktop app for exploring SAP OData servicesDesktop app,
secondsky/sap-skillsadded to the atlasForty SAP development plugins for coding agentsSkill,
@ui5/loggerprovides revisedFiled under logging, which is a running service's log output. This is the UI5 CLI's internal logger, described by its own README as internal — it answers nothing a reader would pick for logging, and belongs where the tooling that depends on it lives.Package,
Show 7 more
Agent guidanceecosystems revisedArtifacts that answer this concern sat behind the ABAP door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a ABAP developer actually decides there, which is the test for opening a door rather than trimming a serves claim.Capability,
Attachmentsecosystems revisedArtifacts that answer this concern sat behind the UI5 door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a UI5 developer actually decides there, which is the test for opening a door rather than trimming a serves claim.Capability,
Documentationecosystems revisedArtifacts that answer this concern sat behind the ABAP door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a ABAP developer actually decides there, which is the test for opening a door rather than trimming a serves claim.Capability,
LLM integrationecosystems revisedArtifacts that answer this concern sat behind the UI5 door with no tile to appear under, so browse counted them and rendered nothing. The concern is one a UI5 developer actually decides there, which is the test for opening a door rather than trimming a serves claim.Capability,
SAP Power for Kiroentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
sap-odata-explorerentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Desktop app,
secondsky/sap-skillsentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README; the catalogue is credited as where it was found and its words are not reused. Hard rule 7: skills are indexed, never authored here.Skill,
Wed 9
23 changes
@ui5/mcp-serveradded to the atlasMCP server for UI5 development with ten toolsMCP server,
@ui5/webcomponents-mcp-serveradded to the atlasMCP server answering questions on UI5 Web ComponentsMCP server,
mcp-sap-docsadded to the atlasMCP server searching seventeen SAP documentation repositoriesMCP server,
SAP Application Frontend serviceadded to the atlasManaged hosting and routing for built frontendsService,
Show 19 more
SAP HTML5 Application Repository service for SAP BTPadded to the atlasStores UI5 and HTML5 apps and serves them through the approuterService,
SAP Task Centeradded to the atlasOne inbox for tasks across SAP applications and BTP workflowsService,
SAP/ui-theme-designer-plugins-for-coding-agentsadded to the atlasAgent plugin on the SAP Design System and theming parametersSkill,
UI5 Web Components agent skillsadded to the atlasTwo agent skills for accessibility and styling of web componentsSkill,
UI5/plugins-coding-agentsadded to the atlasUI5 plugins for coding agentsSkill,
@sap-ux/fiori-mcp-serverprovides, ecosystem, links revisedlinks.repo is the whole of SAP/open-ux-tools, which carries much else besides this. Naming the package directory says which part of the monorepo the artifact is — and it is what lets a sweep tell this entry apart from the next package in the same repository.MCP server,
@ui5/mcp-serverentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.MCP server,
@ui5/webcomponents-mcp-serverentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; the description is written from the project's own README and documentation rather than from the catalogue's line about it.MCP server,
Agent access to your codeid, ecosystems revisedAn SAP-published MCP server entered from the sap-ai-mcp-servers catalogue answers this concern on the BTP door, and the door had no tile for it to sit under.Capability,
Agent guidancedescription, ecosystems revisedThe cross-ecosystem sentence said "writes correct CAP", which was true when CAP was the only door. The CAP-specific wording moved into framing_by_ecosystem.cap where it belongs, and the node's own description now describes the concern rather than one ecosystem's version of it.Capability,
Authenticationecosystems revisedThe BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install.Capability,
Destinationsecosystems revisedThe BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install.Capability,
Documentationcore coverage, ecosystems revisedAn SAP-published MCP server entered from the sap-ai-mcp-servers catalogue answers this concern on the UI5 door, and the door had no tile for it to sit under.Capability,
Loggingecosystems revisedThe BTP services answering this were in the corpus while the capability was not on the BTP map, so browse counted them behind the door and had no group to render them in. The BTP door is a reading of its own — a fallback to CAP's would assert something false about a service you bind rather than install.Capability,
mcp-sap-docsentry revisedNamed in docs/NEIGHBOURS.md §3.1 as a project of the bestofcapjs author but never entered. It is a documentation retrieval server, not an index of options — the complement posture the same section assigns ARC-1, and hard rule 5 makes it exist here only as an attached entry.MCP server,
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.Service,
SAP/ui-theme-designer-plugins-for-coding-agentsentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.Skill,
UI5 Web Components agent skillsentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here. Entered as its own artifact rather than as a block on the library, which the corpus does not yet hold — the same shape fiori-mcp has inside SAP/open-ux-tools.Skill,
UI5/plugins-coding-agentsentry revisedEntered from the sap-ai-mcp-servers catalogue, which is credited as the source; written from the repository's own README rather than from the catalogue's line about it. Hard rule 7: skills are indexed, never authored here.Skill,
Tue 8
47 changes
@sap-theming/theming-base-contentadded to the atlasColour, font and metric definitions of the SAP themesPackage,
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.Blog,
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.Blog,
Building an Attachment Upload and Download Solution Using UploadSetwithTable ControlpublishedThe successor control to UploadSet posts the file in one request by default, and against CAP that is wrong: the record has to be created first and the content put to it afterwards. The author states the two-step shape plainly and notes it may not apply to an ABAP backend, which is the kind of boundary that usually goes unsaid. Written during a proof of concept for a reusable attachment component, and it carries the problem they hit with the control.Blog,
Show 43 more
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.Blog,
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.Blog,
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.Blog,
Calling bound / unbound CAP actions from Fiori elements application.publishedinvokeAction 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.Blog,
CAP - 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.Blog,
CAP 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.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
Create Automated System Tests for SAP Cloud Application Programming Model ProjectspublishedEnd-to-end tests driving the UI with wdi5, run in the pipeline — the layer above cds.test, which stops at the service boundary.Tutorial,
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.Blog,
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.Blog,
Develop a Full-Stack CAP Application Following SAP BTP Developer's GuidepublishedThe eight-part path SAP's own Developer's Guide prescribes: a CAP service, Fiori Elements over it, custom logic, authorization, tests, and the preparation deployment needs. It is the closest thing to an official answer to 'what does a whole CAP application look like', which is why it sits under reference applications rather than under any one of the capabilities it touches.Workshop,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
Extend Upload Set to Fiori Elements and utilize Document Management ServicepublishedWritten two months before there was an official plugin, and the author has left the record of that in the page: an update dated 2024-04-04 noting the CAP team released @cap-js/attachments, and another dated 2024-05-21 saying they tested it and wrote up the Object Store variant separately. The hand-built version underneath is still the answer when the plugin's storage choices do not fit.Blog,
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 — a sample managing text and file information together, and offered as something for people new to BTP rather than as a pattern.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
Media Handling in SAP CAPM – Backend and Frontend ImplementationpublishedFiles against a record with the front end included, which most of the attachments writing here leaves out — the entity that stores the content, the custom logic around it, and then the UI5 side that uploads and retrieves. End to end rather than one half.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
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.Blog,
TypeScript Sheriff: How can I use TypeScript in the SAP ecosystem? (Part 2 of 3)publishedThe middle part of three, and the one about SAP: where TypeScript is supported across a side-by-side extension on BTP, as of July 2023. It says the SAP Cloud SDK already generates OData clients as .ts files and UI5 ships types for its controls and modules, the ground of TypeScript support in UI5, while CAP offers standard types and the new @cap-js/cds-typer generates types for a service, which is typing, with the caveat that running cds-ts commands could overwrite what cds-typer generated.Blog,
Unlocking Efficiency: Leveraging SAP BTP Document Management Service in Fiori Applications # 2publishedDocument Management's own Attachment Reuse UI dropped into a Fiori elements List Report, in two variants — OData V2, and OData V4 in a CAP application. The CAP half is one of the two scenarios rather than the subject; the rest of the series is about custom Fiori apps and a process task UI, with no CAP in them.Blog,
Upload attachments in a Freestyle UI5 and CAP apppublishedAttachments where the UI is freestyle rather than Fiori elements, so none of the generated upload behaviour applies and both ends have to be written.Blog,
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.Blog,
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.Blog,
@sap-ux/fiori-mcp-serverartifact type, description revisedPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.MCP server,
@ui5/loggerartifact type, ecosystem, description revisedPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.Package,
ui5-upload-controlsartifact type, ecosystem, description revisedPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.Package,
Mon 7
22 changes
A ChatGPT-like chat app built with modern SAP technologies (CAP, SAPUI5) – Part 1/3publishedThe concepts before the code: what the GPT model and its API actually offer, and what the finished chat application looks like — personalities included. Written in the weeks when the ground was moving under it, and the post carries its own change log to prove it: GPT-3.5 added on 1 March, GPT-4 on 15 March, and an admission that a series planned as two posts became three.Blog,
A ChatGPT-like chat app built with modern SAP technologies (CAP, SAPUI5) – Part 2/3publishedThe backend: CAP with TypeScript, the entities holding chats and personalities, and the service that talks to the API. This is where the streamed completion and the repositories behind the handler come from, which is the part of the sample still worth lifting even though the model access has since been superseded by AI Core.Blog,
A ChatGPT-like chat app built with modern SAP technologies (CAP, SAPUI5) – Part 3/3publishedThe SAPUI5 frontend of the sample, and mostly an argument for writing UI5 in TypeScript: ES imports in place of sap.ui.define, a class with real private members in place of the underscore convention, and the service types generated from the CDS model copied into the UI package, so one IChats interface types the OData object the controller reads. The second half is structure — a formatter class and a singleton LayoutManager called from the XML view through core:require, a confirmation helper taking a callback, a dialog class resolving a promise, a generic createEntity<T> on a service class — all of it to keep every controller under 100 lines. What it says about arranging a UI5 app holds whatever model sits behind the chat; the tooling around it is of its date, and the post calls UI5's TypeScript support experimental.Blog,
cap-ui5-gpt-chatadded to the atlasChat app on CAP and SAPUI5 against the OpenAI APISample,
Show 18 more
debug a CAP app with UI5 TypeScript UI component with VS CodepublishedDebugging both runtimes at once — the CAP server and a UI5 component written in TypeScript, the latter stepped through in its own sources rather than in the transpiled output. Written when TypeScript for UI5 had just become possible, and the combination it sets up is the one CAP's app folder invites.Blog,
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.Blog,
Evaluating SAP’s new MCP servers: UI5, CAP, and Fiori tools in practicepublishedSomeone trying SAP's three new MCP servers rather than repeating the announcement. It sets the official positioning first — MCP as the bridge from coding assistants to SAP tooling across Cursor, Windsurf, Copilot, Cline and Claude Code, with best-practice scaffolds and BTP-aligned guardrails — and then reports what using them is actually like. The rare kind of post that tests a vendor claim.Blog,
generator-ui5-library-af-deployadded to the atlasYeoman generator for Application Frontend config in UI5 librariesGenerator,
Github Copilot VSCode - My Own SAP Development RulespublishedOne developer's rule files for Copilot, split by concern rather than kept as one prompt: CAP backend rules, UI5 frontend rules, Jest testing rules and Bruno collection rules, each with a scope narrow enough that an agent cannot read it two ways. The CAP file covers reusable types, managed data, soft-delete behaviour and service conventions; the UI5 file covers naming, view constraints and where annotations may live. It is the rule-file half of agent guidance rather than the skill half — nothing is packaged or published, and the value on offer is the shape of the split.Blog,
How to consume UI5 custom libraries in BAS or VS CodepublishedConsuming a custom UI5 library from a UI5 application locally, using yarn workspaces to resolve the dependency instead of adjusting the project before every deploy. The post is honest about its own history: the author had asked the question on SAP Community, found a workaround that needed a pre-deploy edit, and only later learned the workspace approach that removes it. Generator-based setup throughout, and 2021-vintage — yarn workspaces, generator-ui5-library and generator-easy-ui5.Blog,
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.Blog,
Integrate Document Information Extraction into UI5 applicationpublishedUploading an invoice from a UI5 application and getting the extracted fields back on screen, with a destination pointing at the Document Information Extraction API and a Refresh button polling until the job finishes. The polling is the honest part: extraction is asynchronous, and the post does not pretend otherwise. From 2022, so the service has since been renamed and the API moved, but the shape — upload, poll, map the result — is the shape it still is.Blog,
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.Blog,
SAP Fiori Tools Update – First Release of the SAP Fiori MCP Server for Agentic AIpublishedThe release announcement for the Fiori MCP server, placed as the step after the Project Accelerator: an assistant can create and edit Fiori applications directly rather than describing what a developer should do. The vendor's own framing, so read it beside the independent evaluation of the same servers rather than instead of it.Blog,
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.Blog,
The Complete Guide to Calling Actions in UI5 with Custom CodepublishedWritten because the documentation is thin and the samples sparse, and openly as a note to the author's future self — hand-coding an action call has become a rare task for anyone mostly working in Fiori elements, which is exactly why it is hard to look up when it comes round. Comes with a CAP sample project, so the service half is there too.Blog,
UI Composition with Application Frontend ServicepublishedWhy shared UI code is hard, and what Application Frontend changes about it. The piece first lays out the three usual answers and what each costs — copying files at development time and repatching every consumer, publishing an npm package and rebuilding every consumer, or hosting the code separately and paying for it in CORS and session handling, or in an extra network hop through a server-side proxy. It then shows a fourth that only this service can do: runtime server-side composition without the hop, configured through routes in the consuming application's xs-app.json, across three cases — a reusable application embedded in a consumer, and two further composition shapes. Read alongside the generator, which scaffolds the mta.yaml, xs-app.json and zipper configuration this model needs.Blog,
UI5 AI Features library is now an npm PackagepublishedThe release note for a demo turning into a dependency, and it is explicit about why that matters: the earlier version worked, but using it meant cloning the repo and copying both halves, which stops working the moment one of them changes. The post walks through what shipping the CAP plugin and the be.wl.ai control library in one npm version buys — a client and server contract that cannot drift — then lists the eleven controls by group, shows the two-line configuration that activates each half, and notes that this version is actually deployed on BTP behind both a standalone approuter and Work Zone. It closes on the demo repository, written with no library source in it as the test that the package stands alone.Blog,
ui5-ai-features-demoadded to the atlasProduct-review screen consuming ui5-cap-ai-features on CAPSample,
ui5-cap-ai-featuresadded to the atlasCDS plugin and UI5 controls for AI text features via SAP AI CoreCDS plugin,
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.Blog,
Agent guidancecore coverage, gap revisedThe gap's premise was that no SAP-published skill existed. One does now, so the gap is no longer about absence — it is about how much of the corpus four skills reach.Capability,
Tue 1
1 change
Seed datacore coverage revisedWrong since mid-2024 and nobody had checked. It said generated volumes were community territory; cds add data has generated volumes since @sap/cds-dk 7.9.0. Found by doing the version-history pass — which is the argument for that pass in one line.Capability,

Mon 31
18 changes
@openui5/sap.ui.coreadded to the atlasFramework core: module loader, MVC runtime, binding, routing, themingPackage,
@ui5/cliadded to the atlasUI5 Tooling command line for project setup, dev server and buildCLI,
ui5-middleware-livereloadadded to the atlasLive reload middleware for the UI5 dev serverBuild tool,
ui5-middleware-simpleproxyadded to the atlasDev-server middleware proxying requests to a backend systemBuild tool,
Show 14 more
ui5-task-transpileadded to the atlasUI5 Tooling task transpiling TypeScript and ES modulesBuild tool,
ui5-task-zipperadded to the atlasBuild task packaging the UI5 build result as a zip archiveBuild tool,
ui5-tooling-modulesadded to the atlasUI5 tooling extensions loading npm packages as UI5 modulesBuild tool,
wdio-ui5-serviceadded to the atlasEnd-to-end testing for UI5 on WebdriverIO with UI5 control selectorsPackage,
Mike Zaschkafirst recorded in the atlasPerson,
Attachmentscore 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.Capability,
Authenticationcore 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.Capability,
Editor supportcore 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.Capability,
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.Capability,
Input validationcore 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.Capability,
LLM integrationcore 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.Capability,
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.Capability,
Loggingcore 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.Capability,
Seed datacore 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.Capability,
Sun 30
3 changes
@sap-ux/fiori-mcp-serveradded to the atlasMCP server for creating and editing Fiori applicationsMCP server,
@ui5/loggeradded to the atlasInternal logger of the UI5 CLIPackage,
ui5-upload-controlsadded to the atlasUI5 control library for file upload and download in front of CAPPackage,
Tue 25
1 change
cap-companionadded to the atlasPlayback-only SAP Companion (Help4) workarea served from CAPCDS plugin,

Fri 10
1 change
SAP/ui-theme-designer-plugins-for-coding-agentsreleased 2.0.0Instructions or agent configurations that invoke the skills by their unprefixed names.Skill,

Fri 5
1 change
@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.Package,

Sat 30
6 changes
@sap-ux/cap-config-writerreleased 1.0.0Examples and test setups written for the CommonJS build, such as a Jest configuration without ESM support.Package,
@sap-ux/fe-fpm-writerreleased 1.0.0Examples that load the package with const ... = require('@sap-ux/fe-fpm-writer') from a CommonJS module, written against 0.x.Package,
@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.Package,
@sap-ux/odata-service-writerreleased 1.0.0Jest configurations, written for the CommonJS build, of projects that test code importing the package.Package,
Show 2 more
@sap-ux/odata-vocabulariesreleased 1.0.0Examples and test setups written for the CommonJS build, such as a Jest configuration without ESM support.Package,
@sap-ux/ui5-application-writerreleased 2.0.0Examples and test setups written for the CommonJS build, such as a Jest configuration without ESM support.Package,

Wed 4
1 change
@sap-theming/theming-base-contentreleased 11.33.0CSS that sets an emphasized button's weight from --sapButton_Emphasized_FontWeight.Package,

Fri 12
1 change
@ui5/mcp-serverreleased 0.2.0The supported Node.js range is ^20.17.0 or 22.9.0 and later. The release also added the get_typescript_conversion_guidelines tool.MCP server,

Tue 27
1 change
@sap-theming/theming-base-contentreleased 11.30.1CSS that reads --sapContent_Margin_Small or another of the four deprecated margin parameters.Package,

Fri 28
1 change
ui5-cc-spreadsheetimporterreleased 2.0.0Any statement that the component is Apache-2.0 licensed without naming a version. That holds for 1.x only.Package,

Wed 24
1 change
@ui5/clireleased 4.0.0Running UI5 Tooling 4 on Node.js 18, scripts that parse the CLI's system messages from stdout, and code that passes ui5HomeDir.CLI,
Tue 16
2 changes
@sap-ux/ui5-application-writerreleased 1.0.0generate() calls whose app object carries no projectType.Package,
@ui5/loggerreleased 4.0.0Requires Node.js 20.11 or 21.2 and later, and npm 10.Package,
Wed 3
1 change
@ui5/webcomponentsreleased 2.0.0Code from 1.x importing ListSeparators.Package,

Mon 17
1 change
@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.Package,
Thu 6
1 change
@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.Package,

Fri 10
1 change
@ui5/webcomponentsreleased 2.0.0-rc.3Markup and samples from 1.x that use <ui5-badge>.Package,
Wed 8
1 change
ui5-cc-spreadsheetimporterreleased 0.34.0Manifest or ui5.yaml examples that use the camel-case customControl/spreadsheetImporter resource path.Package,

Thu 18
1 change
@ui5/webcomponentsreleased 2.0.0-rc.2Markup from 1.x using <ui5-multi-combobox allow-custom-values>.Package,
Tue 9
1 change
@ui5/webcomponentsreleased 2.0.0-rc.0Markup from 1.x such as <ui5-list mode="MultiSelect">.Package,

Tue 5
1 change
openui5-passwordreleased 1.0.0Using the control in an application on a UI5 version below 1.120.Package,

Mon 31
17 changes
ui5-middleware-approuterreleased 3.0.0Projects on UI5 Tooling 2 installing the current major of the middleware.Build tool,
ui5-middleware-capreleased 3.0.0Setups that add the middleware to a project built with UI5 Tooling V2.Build tool,
ui5-middleware-iasyncreleased 3.0.0-alpha.0A ui5.yaml written for UI5 Tooling V2 that loads this middleware.Build tool,
ui5-middleware-indexreleased 3.0.0A setup that uses this middleware in a project still built with UI5 Tooling V2.Build tool,
Show 13 more
ui5-middleware-livereloadreleased 3.0.0A ui5.yaml written for UI5 Tooling V2 that loads this middleware.Build tool,
ui5-middleware-servestaticreleased 3.0.0A setup that registers this extension in a project still built with UI5 Tooling V2.Build tool,
ui5-middleware-simpleproxyreleased 3.0.0A setup that registers this middleware in a project still built with UI5 Tooling V2.Build tool,
ui5-middleware-webjarsreleased 3.0.0A setup that uses this middleware in a project still built with UI5 Tooling V2.Build tool,
ui5-task-cachebusterreleased 3.0.0A ui5.yaml written for UI5 Tooling V2 that loads this task.Build tool,
ui5-task-flatten-libraryreleased 3.0.0A ui5.yaml written for UI5 Tooling V2 that loads this task.Build tool,
ui5-task-i18ncheckreleased 3.0.0A ui5.yaml written for UI5 Tooling V2 that loads this task.Build tool,
ui5-task-minify-xmlreleased 3.0.0A setup that uses this task in a project still built with UI5 Tooling V2.Build tool,
ui5-task-pwa-enablerreleased 3.0.0Projects on UI5 Tooling 2 installing the current major of the task.Build tool,
ui5-task-zipperreleased 3.0.0Setups that add the task to a project built with UI5 Tooling V2.Build tool,
ui5-tooling-lessreleased 3.0.0Setups that add the extension to a project built with UI5 Tooling V2.Build tool,
ui5-tooling-modulesreleased 3.0.0A setup that registers this extension in a project built with UI5 Tooling V2.Build tool,
ui5-tooling-stringreplacereleased 3.0.0A setup that registers this extension in a project still built with UI5 Tooling V2.Build tool,

Wed 28
1 change
ui5-cc-spreadsheetimporterreleased 0.21.0Posts and READMEs that install ui5-cc-excelupload.Package,

Tue 18
1 change
ui5-cc-spreadsheetimporterreleased 0.15.0Component configurations that set fieldMatchType.Package,

Thu 9
1 change
@ui5/loggerreleased 3.0.0UI5 Tooling extensions that require('@ui5/logger') from CommonJS, call getGroupLogger, or log with %s placeholders.Package,

Tue 6
1 change
ui5-cc-spreadsheetimporterreleased 0.3.0Integration examples written for 0.2 or earlier.Package,

Tue 21
1 change
ui5-appreleased 0.16.0Instructions that install and run the showcase with yarn.Sample,

Wed 1
3 changes
@ui5/clireleased 2.0.0The ui5 use and ui5 add commands were added.CLI,
@ui5/clireleased 2.0.0The --framework-version option was added.CLI,
@ui5/clireleased 2.0.0Support for Node.js releases before 10 was dropped: only Node.js 10 or higher is supported.CLI,
Everything the feed holds.
AtomJSON