NewSAP Commerce Cloud, formerly SAP Hybris

New in SAP Commerce

Change
Kind
Origin
Domain
  • Protocols & APIs0
  • Data & Persistence0
  • Integration & Messaging0
  • AI & Agents11
  • Security & Compliance0
  • Operations & Runtime0
  • Developer Experience0
  • UI & Frontend Bridge0
  • Process & Workflow0
  • Learning & Reference0
14 changes

Today
1 change
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,
Sat 17
1 change
Agent access to your systemsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.Capability,
Fri 16
1 change
Abinaya Srinivasanadded to the atlasPerson,
Thu 15
1 change
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,
Mon 12
3 changes
André Escocardadded to the atlasPerson,
Dawid Michałowiczadded to the atlasPerson,
Agent access to your systemscore coverage, coverage by ecosystem, description revisedMaintainer requested complementary boundaries so a CAP bridge can connect system access and application MCP exposure, while implementation restrictions remain explicit. Domains, providers and task classifications are unchanged.Capability,
Fri 9
7 changes
hybris-mcp-liteadded to the atlasRead-only MCP server over a local SAP Commerce Cloud's HACMCP server,
sap-cx-developer-companionadded to the atlasAgent skill for SAP Customer Experience APIs, CDS and errorsSkill,
Agent access to your systemsentry revisedSplit out of MCP servers at the maintainer's decision. That capability named a protocol and carried two concerns: exposing what you built to agents, which stays there under a name that says so, and giving agents a way into an SAP system you run, which is this one. Thirty providers moved with their own sentences; the Commerce and SuccessFactors slots moved with them. Named beside agent access to your code, its development-time sibling.Capability,
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,
Show 3 more
hybris-mcp-liteentry, provides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.MCP server,
sap-commerce-skillentry revisedDeclined on scope on 2026-09-10, with no Commerce door and no Commerce capability for it to attach to, and reopened in data/curation/decisions.json once the product door opened (docs/concepts/product-doors.md, ADR-0033). Written from the repository's own README; hard rule 7: skills are indexed, never authored here.Skill,
sap-cx-developer-companionentry revisedA new repository in the SAP AI Skills Library registry snapshot of 2026-10-09, registering one skill at skills/sap-cx-developer-companion. Written from the repository's own README and SKILL.md; hard rule 7: skills are indexed, never authored here. Placed behind the SAP Commerce door because the CX API explorer and the error resolver are written against Commerce Cloud OCC and Sales and Service Cloud, with CAP and BTP as served doors for the CDS half.Skill,
The last 30 days. Older changes stay in each entry's history.