Everything in UI5 / Web Components
Type: 3
Domain
Origin
Signals
Web Components: Answers in Web Components
More
Group by: Capability
Where it runs
Distributed through
APIs and a UI5 component for document management in apps
Groups npm audit findings by root dependency, with failing thresholds
It audits through npm: a project that resolves its dependencies with another package manager, or has no `package.json`, has nothing for it to run. What it reports is what `npm audit` knows, so a vulnerability outside the npm advisory data is not in its table.
Shows which feature branches reached which environment branch
A team that does not keep one long-lived branch per environment has no environment branches for it to compare feature branches against. What it reports is the merge state of branches in Git, so it says nothing about whether a merged change has been built or deployed to the environment.
Development environment on BTP for UI5, Fiori, mobile and CAP
IDE service on SAP BTP for SAPUI5, Fiori and full-stack apps
Joule's generative AI inside SAP Build Code
Development environment on BTP for UI5, Fiori, mobile and CAP
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Stores UI5 and HTML5 apps and serves them through the approuter
Key-user adaptation and personalisation for UI5 apps on SAP BTP
Role-based portal sites with pages, apps and widgets
One inbox for tasks across SAP applications and BTP workflows
Pro-code CLI for building and deploying Joule Studio solutions
Local ABAP server serving /IWBEP/ OData v2 without an SAP system
Not a system to run a business application on: there is no business application in it, and what it implements of the language, the dictionary and Gateway is a stated subset of each. It is a clean-room reimplementation of the `/IWBEP/` interfaces that bundles no SAP source and no standard DDIC, so a service that reads standard objects has nothing to read, and `ANORMALIES.md` records every place the runtime differs from SAP before any workaround is written.
Predefined CI/CD pipelines for SAP development projects