Person

René Jeglinsky

Capabilities9

Contributes to 9
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.DestinationsCAPDestinationscapabilityReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.Editor supportCAPEditor supportcapabilityWorking in source code with the editor helping rather than treating it as text — completion, go-to-definition, inline errors, refactoring and preview.GraphQLCAPGraphQLcapabilityServing the same model over GraphQL instead of OData — one endpoint, the client naming the fields it wants, for consumers who expect that shape rather than an OData one.LoggingCAPLoggingcapabilitySeeing what a running service did, in a form something can read afterwards — levels, a formatter that suits a laptop and one that suits a log service.Metadata publishingCAPMetadata publishingcapabilityDescribing a service to something other than a human — service metadata for clients, and machine-readable descriptions for registries and discovery.ODataCAPODatacapabilityExposing data and operations through OData, including the service model, metadata and protocol versions clients require. Version differences affect which clients can consume a service and which query features they can use.Service integrationCAPService integrationcapabilityUsing a service that runs somewhere else as if it were one of your own: its API imported into the model, a proxy that turns a local query into the remote protocol, and a mock that stands in for it on a laptop. Distinct from [destinations](capability:destinations), which is how the address and the credentials are found, and from [replication](capability:replication), which is holding the data locally.

Entries20

Group by20 of 20 entries
EntrySignals
Contributes to20
@cap-js-community/odata-v2-adapterv1.16.2
none

Exposes a CAP service as OData V2

@cap-js/audit-loggingv1.3.0
none

CAP integration with the SAP Audit Log service

@cap-js/graphqlv0.14.0
none

GraphQL protocol adapter generated from the CDS model

@cap-js/ordv1.10.2
none

Generates Open Resource Discovery documents from a CAP model

@capire/data-viewer
Functional boundary

Sample CAP plugin adding a generic data browser

capire/bookshop
none

CAP's getting-started bookshop sample

capire/bookstore
none

Composite CAP app from separately deployed services

capire/docs
none

Sources of capire, the CAP documentation

capire/incidents-app
none

Incident Management reference application for CAP

capire/s4
none

Prebuilt SAP S/4HANA integration package for CAP projects

cds-intellij
none

SAP CDS language support for IntelliJ IDEA

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

CAP Java attachments with database storage and an Object Store module

commonv0.2.5
none

Sample CAP plugin extending @sap/cds/common with reuse data

orders
Functional boundary

Sample CAP reuse service for orders, with a Fiori UI

reviewsv0.1.0
Functional boundary

Sample CAP reuse service for reviews, with a Fiori UI

SAP-samples/cloud-cap-samples-java
none

Bookshop app demonstrating the CAP Java SDK end to end

SAP-samples/fiori-elements-feature-showcase
none

Showcase of Fiori elements for OData V4 features on a CAP backend

shared-db
Functional boundary

CAP sample sharing one domain model and database across apps

xflights
none

CAP reuse package serving Airlines, Airports and Flights data

xtravels
none

CAP travel-booking app built on xflights master data

Details

For your agent