cds 9: task queue

guides/deployment/custom-builds.md

@@ -22,7 +22,7 @@ The CDS model folders and files used by `cds build` are determined as follows:
 - Known root folders, by [default](../../get-started/#project-structure) the folders _db/, srv/, app/_,  can also be configured by [`folders.db`, `folders.srv`, `folders.app`](../../get-started/#project-structure).
 - The _src_ folder configured for the individual build task.
 - If [feature toggles](../extensibility/feature-toggles#enable-feature-toggles) are enabled: subfolders of the folder _fts_.
-- CDS Model folders and files defined by the [required services](../../node.js/cds-env#services) of your project. This also includes models used by required built-in CDS services, like [persistent outbox](../../node.js/outbox#persistent-outbox) or [MTX related services](../multitenancy/mtxs#mtx-services-reference).
+- CDS Model folders and files defined by the [required services](../../node.js/cds-env#services) of your project. This also includes models used by required built-in CDS services, like [persistent queue](../../node.js/queue#persistent-queue) or [MTX related services](../multitenancy/mtxs#mtx-services-reference).
 
 Feature toggle folders and required built-in service models will also be added if user defined models have already been configured as [_model_ option](#build-task-properties) in your build tasks.
 

guides/messaging/task-queues.md

@@ -26,7 +26,7 @@ This guide will grow with the functionality.
 
 Regarding the _outbox_, please see the following existing documentation:
 - [Transactional Outbox](../../java/outbox) in CAP Java
-- [Outboxing with `cds.outboxed`](../../node.js/outbox) in CAP Node.js
+- [Outboxing with `cds.queued`](../../node.js/queue) in CAP Node.js
 
 
 
@@ -42,7 +42,7 @@ Simply configure your messaging service for Node.js as <Config>cds.requires.mess
 With the inbox, all messages are acknowledged towards the message broker regardless of whether they can be processed or not.
 Hence, failures need to be managed via the dead letter queue built on `cds.outbox.Messages`.
 
-[Learn more about the dead letter queue in Node.js.](../../node.js/outbox#managing-the-dead-letter-queue){.learn-more}
+[Learn more about the dead letter queue in Node.js.](../../node.js/queue#managing-the-dead-letter-queue){.learn-more}
 [Learn more about the dead letter queue in Java.](../../java/outbox#outbox-dead-letter-queue){.learn-more}
 
 Inboxing is especially beneficial in case the message broker does not allow to trigger redelivery and/ or "fix" the message payload.

node.js/_menu.md

@@ -57,7 +57,7 @@
 # [cds. utils](cds-utils)
 # [cds. test()](cds-test)
 # [cds. plugins](cds-plugins)
-# [cds. outboxed()](outbox)
+# [cds. queued()](queue)
 # [TypeScript](typescript)
 # [Fiori Support](fiori)
 # [Best Practices](best-practices)

node.js/messaging.md

@@ -127,7 +127,7 @@ this.after(['CREATE', 'UPDATE', 'DELETE'], 'Reviews', async (_, req) => {
 ```
 ::: tip
 The messages are sent once the transaction is successful.
-Per default, a persistent outbox is used. See [Messaging - Outbox](./outbox) for more information.
+Per default, a persistent queue is used. See [Messaging - Queue](./queue) for more information.
 :::
 
 ## Receiving Events
@@ -160,6 +160,24 @@ messaging.on('*', async msg => { /*...*/ })
 In general, messages do not contain user information but operate with a technical user. As a consequence, the user of the message processing context (`cds.context.user`) is set to [`cds.User.privileged`](/node.js/authentication#privileged-user) and, hence, any necessary authorization checks must be done in custom handlers.
 :::
 
+### Inbox <Beta />
+
+You can store received messages in an inbox before they're processed. Under the hood, it uses the [task queue](./queue) for reliable asynchronous processing.
+Enable it by setting the `inboxed` option to `true`, for example:
+
+```js
+{
+  cds: {
+    requires: {
+      messaging: {
+        kind: 'enterprise-messaging',
+        inboxed: true
+      }
+    }
+  }
+}
+```
+
 ## CloudEvents Protocol
 
 [CloudEvents](https://cloudevents.io/) is a commonly used specification for describing event data.