onedevatlasBeta
Browse the atlas
Person

Pierre Fritsch

5contributes to
GitHub@PierreFritsch

Capabilities3

Contributes to 3
Async processingCAPAsync processingcapabilityDoing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.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.Job schedulingCAPJob schedulingcapabilityRunning something later, or on a cadence, without keeping a process alive to do it — a nightly job, a retry in an hour, a report on the first of the month — and knowing afterwards whether it ran.

Entries5

Group by
EntrySignals
Contributes to5
@cap-js-community/event-queuev2.3.2
Functional boundary

Transactional processing of asynchronous and periodic CAP events

@cap-js/sdmv1.11.0
Functional boundary

CAP attachments stored in an SAP Document Management repository

capire/docs
none

Sources of capire, the CAP documentation

SAP-samples/cap-sflight
none

Travel-booking reference app on CAP Node.js and Java backends

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

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

Details

For your agent
Ref
actor:pierrefritsch
JSON
/actors/pierrefritsch.json
MCP
Connecting an agent