From 23dcc0030bc3aa1aa11db8657b7e9295f429bea6 Mon Sep 17 00:00:00 2001 From: Max Gruenfelder Date: Mon, 3 Jul 2023 08:42:37 +0200 Subject: [PATCH] wip --- docs/implement-event/index.md | 5 +---- docs/status-handling/index.md | 2 +- docs/transaction-handling/index.md | 5 +++-- 3 files changed, 5 insertions(+), 7 deletions(-) diff --git a/docs/implement-event/index.md b/docs/implement-event/index.md index 1c3d8f11..45546d7d 100644 --- a/docs/implement-event/index.md +++ b/docs/implement-event/index.md @@ -5,16 +5,13 @@ nav_order: 4 --- - # Implement Event - {: .no_toc} - - TOC - {: toc} +{: toc} ## Overview diff --git a/docs/status-handling/index.md b/docs/status-handling/index.md index 593fe0d7..92963708 100644 --- a/docs/status-handling/index.md +++ b/docs/status-handling/index.md @@ -14,7 +14,7 @@ nav_order: 6 - TOC - {: toc} +{: toc} ## Overview One of the main pillars of this library is safe transaction handling of events in combination with business processes. diff --git a/docs/transaction-handling/index.md b/docs/transaction-handling/index.md index 26c2a6e3..4f847a6b 100644 --- a/docs/transaction-handling/index.md +++ b/docs/transaction-handling/index.md @@ -14,14 +14,15 @@ nav_order: 5 - TOC - {: toc} +{: toc} ## Overview One of the fundamental pillars of this library is the secure handling of transactions in conjunction with business processes. All transactions related to event processing are fully managed and should not be committed or rolled back by the event implementation. The circumstances under which transactions are committed or rolled back are described in the -following section. +following section. Transactions are always CDS transactions associated with a CDS context. For more general information +about CAP transaction handling, please refer to the [documentation](https://cap.cloud.sap/docs/node.js/cds-tx). ## Transaction Handling