Prompt management
Keeping the prompts an application sends to a model as templates with placeholders, stored and versioned apart from the code that calls them, so a change of wording is not a deployment. What people conflate under it: the template filled at runtime, the registry it lives in, and the orchestration step that fills it.
Showing artifacts, examples and content with confirmed Node.js applicability. View All CAP
Overview
No SAP artifact is confirmed here for Node.js.
A Node.js coverage assessment has not been written. View all flavors
A prompt registry that lives in the application rather than in a service: templates are registered once and invoked by name from a CAP handler, gitPromptRegistry loads them from a Git repository and caches them instead, so a wording change goes through pull request review separately from a code deployment, and promptVersionPin decides which version a call or a session gets.
A Node.js coverage assessment has not been written. View all flavors
Artifacts
Seen working
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Every CDS service in both samples is marked `@requires: 'any'` and left publicly accessible, which the README says simplifies the testing and deployment process, and it asks for proper authentication mechanisms to be applied in their place.
Details
Coverage
For your agent
- Ref
capability:prompt-management- JSON
- /capabilities/prompt-management.json
- MCP
- Connecting an agent