Skip to content

Draft Lock: add tip and reorder #1975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
renejeglinsky merged 3 commits into from
Jul 17, 2025
Merged

Draft Lock: add tip and reorder #1975

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1430f95
add tip and reorder
renejeglinsky Jul 16, 2025
112e44d
Update node.js/fiori.md
renejeglinsky Jul 17, 2025
b1fb4c9
Merge branch 'main' into rjegl07/draftLockDelete
renejeglinsky Jul 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
53 changes: 28 additions & 25 deletions node.js/fiori.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -77,8 +77,35 @@ You can set the property to one of the following:
- number of minutes like `'10min'`
- number of milliseconds like `1000`

### Bypassing the SAP Fiori Draft Flow
:::tip Delete released draft locks
If the `draft_lock_timeout` has been reached, every user can delete other users' drafts to create an own draft. There can't be two drafts at the same time on the same entity.
:::

### Garbage Collection of Stale Drafts

Inactive drafts are deleted automatically after the default timeout of 30 days. You can configure or deactivate this timeout by the following configuration:

```json
{
"cds": {
"fiori": {
"draft_deletion_timeout": "28d"
}
}
}
```

You can set the property to one of the following:
- `false` in order to deactivate the timeout
- number of days like `'30d'`
- number of hours like `'72h'`
- number of milliseconds like `1000`

::: info Technical background
It can occur that inactive drafts are still in the database after the configured timeout. The deletion is implemented as a side effect of creating new drafts and there's no periodic job that does the garbage collection.
:::

### Bypassing the SAP Fiori Draft Flow
Creating or modifying active instances directly is possible without creating drafts. This comes in handy when technical services without a UI interact with each other.

To enable this feature, set this feature flag in your configuration:
Expand Down Expand Up @@ -122,30 +149,6 @@ Note that this feature creates additional entry points to your application. Cust
payloads rather than the complete business object.
:::

### Garbage Collection of Stale Drafts

Inactive drafts are deleted automatically after the default timeout of 30 days. You can configure or deactivate this timeout by the following configuration:

```json
{
"cds": {
"fiori": {
"draft_deletion_timeout": "28d"
}
}
}
```

You can set the property to one of the following:
- `false` in order to deactivate the timeout
- number of days like `'30d'`
- number of hours like `'72h'`
- number of milliseconds like `1000`

::: info Technical background
It can occur that inactive drafts are still in the database after the configured timeout. The deletion is implemented as a side effect of creating new drafts and there's no periodic job that does the garbage collection.
:::

### Differences to Previous Version

- Draft-enabled entities have corresponding CSN entities for drafts:
Expand Down