OrganisationIndependent

Expertum

Capabilities1

Provides 1
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.

Entries1

Group by
EntrySignals
Maintains1
@expertum/cap-email-pluginv0.1.1
Functional boundary

Annotation-driven mail on CAP entity lifecycle events

Details

History6
  • @expertum/cap-email-pluginlinks.repo → https://github.com/expertum-net/cap-email-pluginThe repository answers again: the GitHub API returns it created 2026-03-06 and pushed 2026-09-18, and raw.githubusercontent serves its README, its package.json and lib/. Nothing says whether it was private or gone between 2026-09-08 and now.
  • @expertum/cap-email-pluginsource_available → trueFollows the repository being readable again. The declared Apache-2.0 licence and the TypeScript the package is built from are both in it.
  • @expertum/cap-email-plugindescription.when_not_to_use → The two version floors, and the provider boundary0.1.1 was published on 2026-09-18 and its README carries no POC label; the repository it declares is readable. What holds is Node >= 22 and @sap/cds >= 9, plus the boundary the README's own provider table states: graph is the kind that sends and basic is a base class, whose dispatchEmail is a no-op for a subclass to override.
  • @expertum/cap-email-pluginrequires → object form, both conditionalNeither is needed in every configuration. The README lists the Destination service for the Microsoft Graph provider alone, and package.json marks @sap-cloud-sdk/http-client optional in peerDependenciesMeta.
  • @expertum/cap-email-pluginlinks.repo → removed404 from the GitHub API. Found by the first full run of scripts/check-links.mjs — the citation had a checked date and nobody had re-read it.
  • First entry seenDiscovered via npm registry · keywords:cds.
Profile1
For your agent