You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: plugins/index.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -313,7 +313,7 @@ Available for:
313
313
## Notifications
314
314
315
315
316
-
The Notifications plugin provides support for publishing business notifications in SAP Build Work Zone. Notification types are defined by annotating CDS events, which the plugin then intercepts and forwards automatically:
316
+
The Notifications plugin provides support for sending emails and publishing business notifications in SAP Build Work Zone. Define notification types declaratively via `@notification`CDS annotations or JSON config — the plugin intercepts annotated events and forwards them automatically:
317
317
318
318
```cds
319
319
@notification: {
@@ -382,17 +382,18 @@ service IncidentService {
382
382
Features:
383
383
384
384
- CAP service-based API — simple, backend-agnostic
385
-
- Notification types defined via CDS @notification annotations
386
-
- Notification types defined via JSON (Node.js only)
385
+
- Notification types defined via CDS `@notification` annotations — `cds build` compiles them to `notification-types.json`
386
+
- Notification types defined via JSON config
387
387
- Auto-emit: annotated CDS events are forwarded to ANS automatically
388
-
- Email delivery via configurable delivery channels
388
+
-**Email delivery** via `@notification.email.subject` and `@notification.email.html` annotations with Mustache syntax
389
389
- Email HTML templates for rich email notifications
390
-
- Batch notifications — emit multiple notifications in a single call
391
-
- i18n support and dynamic priority for notification types
390
+
-**Batch notifications** — send multiple notifications in a single outbox event
391
+
-**i18n support** via `{i18n>key}` syntax in annotations
392
+
-**Dynamic priority** via `@notification.priority` with runtime expressions
392
393
- Console logging in development — no external service needed
393
394
- Transactional outbox — maximized scalability and resilience
394
395
- Automatic registration and lifecycle management of notification types on startup
395
-
396
+
- Optional database storage for sent notifications with cooldown to prevent duplicate delivery (Java)
0 commit comments