PersonIndependent
Sören Leibach
GitHub@sleibachlast push
Capabilities
Provides
Concurrency controlCAPConcurrency controlStopping two people who opened the same record from silently overwriting each other — detecting that the version you read is no longer the version you are saving over.Database connectorsCAPBTPABAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).Draft handlingCAPDraft handlingLetting a user edit a record over several requests before it becomes real — saving unfinished changes, locking, and activating a completed draft.In-app guidanceCAPIn-app guidanceExplaining an application from inside it — guided tours, hotspots and contextual help shown next to the screen a user is on, rather than in a separate manual.Serve your application over MCPCAPBTPABAPServe your application over MCPExposing selected application data and business operations to an AI agent through the Model Context Protocol. An application may also integrate remote services through [service integration](capability:service-integration), connecting its exposed contract with [agent access to your systems](capability:agent-systems-access). Development assistance belongs to [agent access to your code](capability:agent-code-access).TelemetryCAPABAPBTPTelemetrySeeing what a running service did — traces across handlers and database calls, metrics, and correlation that survives an async boundary.Workflow integrationCAPWorkflow integrationDriving 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.
Contributes to
LLM integrationCAPUI5BTPABAPLLM integrationCalling 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.NotificationsCAPABAPNotificationsTelling 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.Retrieval-augmented generationCAPABAPBTPRetrieval-augmented generationGrounding a model's answer in data retrieved at question time: text split into chunks, each chunk embedded as a vector, and the chunks nearest to the question placed into the prompt. Semantic search is the same retrieval with a person reading the matches, and fine-tuning changes the model's weights, not its input.
Entries
Group by9 of 9 entries
EntrySignals
Maintains
cap-collaborative-draftcap-collaborative-draftA cds-plugin that gives a CAP Node.js service the OData contract, tables and handlers Fiori elements needs for collaborative draft, so a second user joins an open draft instead of meeting HTTP 423.independent, cap
The maintainer marks this under active development; public APIs, annotation names and OData contracts may still change.
Collaborative draft support for CAP Node.js services
cap-companioncap-companionServes a playback-only SAP Companion (Help4) workarea from a CAP service, so a Fiori application shows tours and in-app help without Enable Now Manager.independent, cap
Not behind a managed approuter: SAP Build Work Zone does not expose the `/$companion/**` routes, so Companion never reaches CAP, and the README names managed approuter and Work Zone as out of scope for v1. Not where help has to be authored in a browser, since the editor, the producer and writes are absent and content lives in files the plugin compiles.
Playback-only SAP Companion (Help4) workarea served from CAP
cap-mcp-plugincap-mcp-pluginGenerates an MCP server from a CDS model: annotated entities become MCP resources, functions and actions become tools, and services can expose reusable prompt templates. A fork of @gavdi/cap-mcp that adds an OAuth proxy, IAS client registration and draft-lifecycle tools.independent, cap
Not published to npm. Install from source.
MCP server generated from a CDS model, forked from @gavdi/cap-mcp
cap-n8ncap-n8nMaps CAP onto n8n: a programmatic workflow API, @n8n.trigger annotations dispatched through the transactional outbox, and a typed cds import --from n8n.independent, cap
Integration of CAP with n8n workflows and triggers
cap-snowflakecap-snowflakeA CAP database adapter for Snowflake with OData V4 support, which the maintainer marks as early development, so its contract is expected to move.independent, cap
The maintainer marks this early development; expect the contract to move.
CAP database adapter for Snowflake with OData V4 support
cap-ui-telemetrycap-ui-telemetryUI5 frontend performance (FESR) and client error capture for CAP, written as cds.log records and forwarded to SAP Cloud Logging, rather than as OpenTelemetry spans.independent, cap
UI5 frontend performance and error capture for CAP
Contributes to
@cap-js/ai@cap-js/aiOut-of-the-box value-help recommendations powered by SAP RPT-1, SAP AI Core as a standard CAP service, and an experimental local embedding model behind SQLite's vector functions.sap official, cap
Value-help recommendations and SAP AI Core as a CAP service
@cap-js/notifications@cap-js/notificationsPublishes business notifications to SAP Build WorkZone from the application, so a user is told something happened without the UI polling for it.sap official, cap
Business notifications from CAP to SAP Build WorkZone
@cap-js/telemetry@cap-js/telemetryAutomatic OpenTelemetry instrumentation for CAP Node.js services and their database calls, exported as traces and metrics to the console, SAP Cloud Logging, Dynatrace, Jaeger or an OTLP endpoint.sap official, cap
OpenTelemetry instrumentation for CAP services
Writing and topics
Piece, what it offersStill applies
Reading Between the Lines: Under-Documented Fiori Elements Capabilities in SAPUI5 1.149Reading Between the Lines: Under-Documented Fiori Elements Capabilities in SAPUI5 1.149Reads SAPUI5 1.149's framework source, not its release notes, to show Fiori Elements shifting side-effect refresh, AI field placeholders and multi-user drafting from controller extensions into what the backing service annotates. Event-driven SideEffects push over a WebSocket channel through @cap-js-community/websocket, while Draft handling gains ABAP RAP's live field locking on CAP Node.js through Sören Leibach's own cap-collaborative-draft plugin. Both rest on Fiori annotations such as Common.SideEffects and CollaborativeDraft.enabled, which the frontend reads rather than requiring a manifest flag.published 2026-07-09
Details
History
- cap-ui-telemetryTelemetry curation for the CAP door. This is the one option in the corpus answering the boundary the core states, that traces begin when a request arrives, and the entry did not say how it does it or that its records are logs rather than spans. Read against the README at commit 78e5d75.
- cap-mcp-pluginThe comparison distinguishes execution and surface selection at the stated runtime, retaining conditional operations and target restrictions.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginConverts the text answer to controlled list values. Its documented conditions remain in the capability relationship; original citations and runtime scope are retained.
- cap-mcp-pluginResolves the requested review findings while preserving the structured comparison values, runtime scopes and implementation restrictions.
- cap-collaborative-draftRefresh 2026-09-28. The plugin acquires a lock per OData property name in DRAFT.DraftFieldLocks and answers HTTP 409 when another participant holds a non-expired one, which is the job concurrency-control names; the edge was missing and both edges now carry what_it_does with the README's sentences.
- cap-collaborative-draftPlacement copied the package's own npm description. Replaced with a line written for this graph — what it does and where it sits — because an unattributed sentence is an unattributed claim.
- cap-collaborative-draftThe page had no answer to what it does; the paragraph states what it adds, what turns it on, and where it stops — the UI snippets the application owns, conflicts logged rather than merged, and the per-process WebSocket relay.
- cap-collaborative-draftThe README names it a required peer dependency for the real-time relay while its own compatibility table calls it optional; recorded as conditional on real-time presence, with both sentences quoted.
- cap-collaborative-draftThe README and the package's peerDependencies both state @sap/cds >= 8.0; the entry carried the runtime and not the range.
- cap-collaborative-draftStated rather than left to the cds-plugin fallback: the README's first line says CAP Node.js backends.
- First entry seenDiscovered via GitHub API · sleibach, npm registry.
For your agent
- Ref
actor:sleibach- JSON
- /actors/sleibach.json
- MCP
- Connecting an agent