Skip to content

Copy document inbox in copy and print flows #1173

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
robinbisping merged 2 commits into from
Jul 9, 2026
Merged

Copy document inbox in copy and print flows #1173

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f026bac
fix(release-2026-07): copy document inbox in copy and print flows
robinbisping Jul 7, 2026
7967b8e
fix(release-2026-07): review feedback
robinbisping Jul 9, 2026
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
2 changes: 2 additions & 0 deletions content/guides/editor/document-copy-flows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -57,6 +57,8 @@ liServer.registerCopyFunctions([
])
```

The source document's inbox is copied to the new document when it is created ({{< added-in "release-2026-07" >}}). Inbox entries that the target document's inbox config does not permit are skipped. If that leaves an inbox group empty, the empty group is still copied.

## Add document copy flow to `projectConfig`

### Minimal
Expand Down
2 changes: 2 additions & 0 deletions content/guides/editor/document-print-flows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,8 @@ liServer.registerPrintFunctions([
])
```

The source document's inbox is copied to the new document when it is created ({{< added-in "release-2026-07" >}}). Inbox entries that the target document's inbox config does not permit are skipped. If that leaves an inbox group empty, the empty group is still copied. Re-running a print flow to check the source for changes does not modify the inbox.

## Add document print flow to `projectConfig`

### Minimal
Expand Down
12 changes: 12 additions & 0 deletions content/operations/releases/release-2026-07.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -306,6 +306,18 @@ The Retresco and iMatrics tag components also got a design refresh. Tags are now

For more information and configuration details, see the [Retresco integration]({{< ref "/guides/integrations/retresco" >}}) documentation.

### Copy Document Inbox in Copy and Print Flows

When editors create a copy or a print version of a document, the source document's inbox is now carried over to the new document automatically.

The inbox is copied when the new document is created. This is now the default behavior for all document copy flows and print flows, so no configuration is required. Re-running a print flow to check the source for changes does not touch the inbox.

{{< info >}}
Inbox entries that the target document's inbox config does not permit are not carried over. If this leaves an inbox group empty, the group itself is still copied.
{{< /info >}}

For more information, see the [Document Copy Flows]({{< ref "/guides/editor/document-copy-flows" >}}) and [Document Print Flows]({{< ref "/guides/editor/document-print-flows" >}}) documentation.

### Keep Inbox Items After Dropping Them Into a Document

By default, an inbox item is removed from the inbox as soon as it is dragged into a document. Some workflows call for the opposite. An editor researching images for an article might want to keep them in the inbox while trying out different options during production. For those setups the item should remain in the inbox after it has been placed.
Expand Down