OrganisationIndependent

CAP

Capabilities8

Provides 8
AttachmentsCAPAttachmentscapabilityStoring a file somebody uploaded next to the record it belongs to, and getting it back out — where the bytes actually live, who may read them, and what the UI shows while they are being scanned.Audit loggingCAPAudit loggingcapabilityRecording who touched personal or sensitive data, in a form an auditor accepts, without hand-writing it in every handler. It is often confused with application logging, which records what the code did rather than who accessed what.DebuggingCAPDebuggingcapabilitySeeing what running code did between an input arriving and a result coming out: which code ran, what the values were at each point, and why a value ended up as it did.Event MeshCAPEvent MeshcapabilityEmitting and consuming business events across systems through brokers, including subscriptions and mapping application events to broker topics. Work that must survive a request, including deferred processing and retries, belongs to [async processing](capability:async-processing).LLM integrationCAPLLM integrationcapabilityCalling a language model from application code with the tenant, destination and credential handling already solved instead using an SDK call with a hand-rolled key.Metadata publishingCAPMetadata publishingcapabilityDescribing a service to something other than a human — service metadata for clients, and machine-readable descriptions for registries and discovery.NotificationsCAPNotificationscapabilityTelling a person something happened when they are not looking at the screen — a notification in the launchpad, an email, a message somewhere they already are.Workflow integrationCAPWorkflow integrationcapabilityDriving an external workflow or automation engine from an application and reacting to what it emits — triggering runs transactionally and importing the engine’s shape as a typed model.

Entries10

Group by10 of 10 entries
EntrySignals
Maintains10
cap-java/cds-ai
none

Bridge from CAP Java to SAP AI Core, with Fiori field recommendations

com.sap.cds:cds-feature-advanced-event-mesh
none

CAP Java plugin for SAP Integration Suite, advanced event mesh

com.sap.cds:cds-feature-attachments
Functional boundary

CAP Java attachments with database storage and an Object Store module

com.sap.cds:cds-feature-auditlog-ng
none

CAP Java plugin sending audit log events to SAP Audit Log service

com.sap.cds:cds-feature-console
none

Connects a running CAP Java app to CAP console for monitoring

com.sap.cds:cds-feature-event-hub
none

Connects CAP Java messaging to SAP Cloud Application Event Hub

com.sap.cds:cds-feature-n8n
none

Triggers n8n workflows from CAP Java through the outbox

com.sap.cds:cds-feature-notifications
none

Business notifications from CAP Java via SAP Alert Notification

com.sap.cds:cds-feature-ord
none

Generates Open Resource Discovery documents from a CAP Java model

com.sap.cds:sdm
Functional boundary

CAP Java plugin for attachments in SAP Document Management

Details

History18
  • cap-java/cds-aiprovides[llm-integration].facets → model_access: SAP AI Core, scoped to the java flavorcapability:llm-integration declared two comparison properties on 2026-10-15. The README, re-read the same day at the commit the entry pins, names SAP AI Core as what the module bridges to and nothing else, so the value is scoped to this artifact's own flavor. response_streaming is left absent: the README says nothing about streaming, and absent is not no.
  • cap-java/cds-aidescription.what_it_solves, provides[llm-integration].sources → capire's plugin list quoted beside themThe 0.0.2-alpha coordinates are a fact about Maven Central and not a statement by the maintainer. capire's plugin list, read on 2026-10-15, says in SAP's own words that the Java version of the AI plugin is currently in alpha, which is the declaration a reader choosing between the two runtimes needs; it is quoted rather than paraphrased and the coordinates stay beside it.
  • com.sap.cds:cds-feature-attachmentsconnects[object-store].condition → The cds-feature-attachments-oss module is selected.The second reader read the connects batch of 2026-09-19 on 2026-09-22, after its acceptance, and found: the connection to the object store carried no condition while the requires edge beside it and the README's default, no dedicated storage target, both state one.
  • com.sap.cds:cds-feature-auditlog-ngconnects[0].sources → +1The second reader read the connects batch of 2026-09-19 on 2026-09-22, after its acceptance, and found: the for sentence names the Audit Log Event Catalog from a passage the edge did not cite; it is cited now.
  • cap-java/cds-aiprovides.what_it_does → Bridges CAP Java to SAP AI Core: resource group management, deployment lifecycle, configuration CRUD and the prediction API, through com.sap.cds:cds-feature-ai-core. com.sap.cds:cds-feature-recommendations builds on that same connection to call SAP RPT-1 for Fiori field recommendations, a narrower, UI-facing use of it.New CAP Java provider discovered through the CAP plugins documentation and the cap-java/cds-ai repository. Both modules are alpha (0.0.2-alpha); cds-feature-recommendations answers a Fiori field-recommendation concern rather than a generic model call, flagged for review rather than attached as a second capability.
  • cap-java/cds-aiconnects → btp-ai-coreThe plugins required SAP AI Core; the connection says what they call it for, and when they do not.
  • com.sap.cds:cds-feature-advanced-event-meshprovides.what_it_does → Connects CAP Java's messaging service to SAP Integration Suite, advanced event mesh: setting a service's `kind` to `aem` routes events to the Solace-based broker, which can reach systems outside SAP as well as inside it.New CAP Java provider discovered through the repository's README and the official CAP documentation. Facts describe the pinned source revision, not verified deployment compatibility.
  • com.sap.cds:cds-feature-attachmentsconnects → btp-malware-scanning, btp-object-storeThe plugin required both services; the connections say under which binding it talks to the scanner, and what it keeps in the object store.
  • com.sap.cds:cds-feature-auditlog-ngprovides.what_it_does → Handles the four CAP audit log event types and sends them to the SAP Audit Log service, matching the Audit Log Event Catalog's semantics so downstream tooling reads standard events.New CAP Java provider discovered through the repository's README and its Maven coordinates. Facts describe the pinned source revision, not verified deployment compatibility.
  • com.sap.cds:cds-feature-auditlog-ngconnects → btp-audit-logThe plugin required the Audit Log service; the connection says which way the events go.
  • com.sap.cds:cds-feature-consoleprovides.what_it_does → Gives CAP console remote monitoring access to a CAP Java application; the application communicates with the console over a plugin dependency and CAP console itself is installed separately.New CAP Java provider discovered through the repository's README and its Maven coordinates. Facts describe the pinned source revision, not verified deployment compatibility.
  • com.sap.cds:cds-feature-event-hubprovides.what_it_does → Sets a CAP Java messaging service's `kind` to `event-hub`, so it sends and receives through SAP Cloud Application Event Hub instead of another broker, with no topics or queues for the application to declare.New CAP Java provider discovered through the repository's README and the official CAP documentation. Facts describe the pinned source revision, not verified deployment compatibility.
  • com.sap.cds:cds-feature-n8nprovides.what_it_does → Fires an HTTP request at an n8n webhook when a CDS event or action annotated with @n8n.process.start occurs, or through a programmatic N8nService.trigger() call, with delivery through the CAP persistent outbox and retry limited to network-level failures.New CAP Java provider discovered through the CAP plugins documentation and the cap-java/cds-feature-n8n repository. Facts describe the pinned source revision (0.0.1); the README itself notes association-path traversal is more limited than the Node.js plugin's.
  • com.sap.cds:cds-feature-notificationsprovides.what_it_does → Delivers business notifications from a CAP Java application to SAP Alert Notification service: CDS events annotated with @notification are provisioned in ANS and emitted on CRUD events, actions or functions, with Web (SAP Build Work Zone) and Email as delivery channels and console logging in local mode.New CAP Java provider discovered through the CAP plugins documentation and the cap-java/cds-feature-notifications repository. Facts describe the pinned source revision (0.0.2-alpha); the module is listed alpha in capire's own plugins page.
  • com.sap.cds:cds-feature-ordprovides.what_it_does → Generates Open Resource Discovery (ORD) documents from the CAP Java model, giving the application the Service Provider Interface a static metadata catalog or a runtime landscape inspection reads.New CAP Java provider discovered through the CAP plugins documentation and the cap-java/cds-feature-ord repository. The repository's own README states little beyond the dependency coordinate; capire's ORD section carries the description.
  • com.sap.cds:cds-feature-attachmentsprovides.what_it_does → Adds attachment storage and handling to CAP Java through an Attachments aspect. The base Maven dependency stores content in the database; com.sap.cds:cds-feature-attachments-oss selects AWS, Azure or Google Object Store storage.New CAP Java provider discovered through official CAP documentation. Facts describe the pinned source revision, not verified deployment compatibility.
  • com.sap.cds:sdmprovides.what_it_does → Stores CAP Java attachments in an SAP Document Management repository through an Attachments aspect. It documents draft handling and direct attachment creation on active entities.New CAP Java provider discovered through official CAP documentation. Facts describe the pinned source revision, not verified deployment compatibility.
  • First entry seenDiscovered via Added by hand.
Profile1
For your agent