NewSAP Cloud Application Programming Model
Domain Developer Experience

Wed 28
2 changes
CF Space Switcheradded to the atlasSwitches Cloud Foundry API, org and space from a view in VS CodeIDE extension,
Now AI Helps You Developing SAPUI5 ApplicationspublishedA walkthrough of Joule's generative AI chat panel for freestyle SAPUI5 development inside SAP Build Code: typed requests in the panel add a view with routing, a model with sample data and a table, or make hardcoded texts translatable, and an "Accept" button transfers the generated code straight into the project's files, with a "Copy" fallback for editing it by hand first. It recommends asking for whole increments rather than one control at a time, notes that Joule keeps the running conversation as context until "Reset Conversation" is pressed, and flags that generated control namespaces are sometimes wrong. A related Joule feature from the Fiori tools team instead creates a complete SAP Fiori elements list report application with its CAP project from business requirements, to continue from with this one.Blog,
Mon 26
10 changes
enforce-export-coverageadded to the atlasStatic check that each exported TypeScript function has a testCLI,
hana-linteradded to the atlasRegex naming rules for SAP HANA artifacts in a CAP projectCLI,
My CAP Projects ToolboxpublishedA working inventory of daily CAP tooling: scaffolding a project with cds init and growing it facet by facet through cds add (TypeScript, seed data, an .http test file, a handler stub), then running it with cds watch and setting a breakpoint in a custom handler from SAP Business Application Studio's JavaScript Debug Terminal. It also walks through an @open entity that accepts properties the model never declared, and reading temporal data defined with CAP's temporal aspect, where a plain read returns only what is valid now and a custom handler is needed to retrieve every time slice.Blog,
Debuggingcore coverage, coverage by ecosystem revisedReassessed against the graph (check:capabilities): seven ABAP providers newer than the block were never named. State stays core-and-community.Capability,
Show 6 more
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,
Local developmentcoverage by ecosystem, coverage by flavor revisedReassessed against the graph (check:capabilities): the note counted providers and claimed an absence about who has built something, which goes stale as providers arrive.Capability,
Model visualisationcoverage by ecosystem revisedReassessed against the graph (check:capabilities): abapGraph and abap-search-tools-ui arrived after the ABAP block was last looked at and the text never named them. No state changed.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,
TypeScript patternscore coverage revisedReassessed against the graph (check:capabilities): removes the count of ways and links the providers that define each kind (decorators, method names, folder layout, persistence), as WRITING §3 asks.Capability,
The last 7 days. Older changes stay in each entry's history.