Everything in the atlas
Type
Domain: Integration & Messaging
Origin
Signals
More: 6
Group by: Capability
Stores, browses and resends messages a CAP service receives
Node module for CAP calling external APIs through a destination
Quiet Release and repository quiet for 57 months.
Functional boundary The package declares `@sap/cds` ^4.5.2 among its dependencies and pins `@sap-cloud-sdk/core` at 1.37.1, so a project on CAP 5 or later is outside the range it states.
Destination resolution and axios calls from CAP configuration
Release and repository quiet for 46 months.
MTA deploying CAP, HDI container and a Fiori elements app
CAP plugin wrapping the SAP Forms service by Adobe on BTP
Stores, browses and resends messages a CAP service receives
Kafka adapter exposing topics as a CDS messaging service
CAP service for typed decisions about one text or JSON state
CAP Java is outside it: the plugin is written for CAP Node.js applications, and `cds add decisions` prints a message and writes nothing in a Java project. A decision needs an answer, so the service cannot be queued: a truthy `queued`, `outboxed` or `outbox` setting fails with `INVALID_CONFIG`, which rules out handing a call to the outbox. The package is not yet on npm, so it is installed from a GitHub release archive, and the subclass hooks, the HTTP mock server, the `cds add` facet and the provider test kit are marked experimental.
Data federation for CAP via delegation, caching and replication