diff --git a/guides/databases-sqlite.md b/guides/databases-sqlite.md index 185aced81..b93ea6b89 100644 --- a/guides/databases-sqlite.md +++ b/guides/databases-sqlite.md @@ -650,7 +650,7 @@ ID;title;author.ID;currency.code // [!code --] As mentioned in [Using Lean Draft](#using-lean-draft), we eliminated all draft handling from new database service implementations, and instead implemented draft in a modular, non-intrusive, and optimized way — called *'Lean Draft'*. -When using the new service, the new `cds.fiori.lean_draft` mode is automatically switched on. You may additionally switch on cds.fiori.draft_compat:true in case you run into problems. +When using the new service, the new `cds.fiori.lean_draft` mode is automatically switched on. More detailed documentation for that is coming. diff --git a/node.js/fiori.md b/node.js/fiori.md index 3b1e5eb11..b3b5316fc 100644 --- a/node.js/fiori.md +++ b/node.js/fiori.md @@ -64,10 +64,6 @@ Additionally, you can add your logic to the draft-specific events as follows: - The `EDIT` event is triggered when you start editing an active entity. As a result `MyEntity.drafts` is created. - The `SAVE` event is just a shortcut for `['UPDATE', 'CREATE']` on an active entity. This event is also triggered when you press the `SAVE` button in UI after finishing editing your draft. Note, that composition children of the active entity will also be updated or created. -::: info Compatibility flag -For compatibility to previous variants, set `cds.fiori.draft_compat` to `true`. -::: - ### Draft Locks To prevent inconsistency, the entities with draft are locked for modifications by other users. The lock is released when the draft is saved, canceled or a timeout is hit. The default timeout is 15 minutes. You can configure this timeout by the following application configuration property: