onedevatlasBeta
Browse the atlas
AllCAPUI5ABAPBTP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

cap-js-notifications

A CAP Node.js order service that sends a notification after every create, published as a sample implementation of @cap-js/notifications.

The wiring sits in three files. package.json pins the plugin at 0.1.0 on @sap/cds 7, srv/service.cds projects shop.Orders into a draft-enabled service with Fiori annotations for the list and the detail view, and srv/service.js connects to the notifications service in an after CREATE handler and calls notify with recipients, a priority, a title and a description. The recipient is one address written into the handler, so nothing here decides who is told. Production configuration is declared in package.json, xsuaa for authentication and HANA for the database, and the scripts build and deploy the project as a multi-target application.

GitHub0 ★

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
NotificationsCAPNotificationscapabilityTelling 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.
Flavors
Node.js

Who is behind it

Mio YasutakeMio YasutakePersonMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained

As a sample

Form
does not say

Connections1

Download
cap-js-notifications connectionscap-js-notificationsPROVIDES→ demonstrates1demonstrates authoredNotifications

README

quoted from miyasuta/cap-js-notifications, read
miyasuta/cap-js-notifications/README.mdOn GitHub

Getting Started

Welcome to your new project.

It contains these folders and files, following our recommended project layout:

File or FolderPurpose
app/content for UI frontends goes here
db/your domain models and data go here
srv/your service models and code go here
package.jsonproject metadata and configuration
readme.mdthis getting started guide
excerpt, no licence read, read the rest, on GitHub

Details

Sources3
GitHub organisations and accountsdiscovered here, miyasutachecked
github.com/miyasuta/cap-js-notificationstree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub organisations and accounts · miyasuta
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
Flavors1
Node.js
“"@sap/cds": "^7"” — miyasuta/cap-js-notifications — package.jsonchecked
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:miyasuta-cap-js-notifications
JSON
/artifacts/miyasuta-cap-js-notifications.json
MCP
Connecting an agent