Skip to content

Commit 3dfe89a

Browse files
committed
more release notes
1 parent 93805eb commit 3dfe89a

File tree

2 files changed

+9
-8
lines changed

2 files changed

+9
-8
lines changed

13/umbraco-workflow/release-notes.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,11 @@ Check the [Version Specific Upgrade Notes](upgrading/version-specific.md) articl
1818
This section contains the release notes for Umbraco Workflow 13 including all changes for this version.
1919

2020
### [13.3.0](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.3.0) (October 23 2024 )
21-
* Adds scheduled content locking feature
22-
* Adds support for content segments
21+
* Adds scheduled content locking feature. Documents can be made readonly until the scheduled release date passes, to ensure approved content isn't modified without workflow approval. [#84](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/84)
22+
* Adds support for content segments. Segment names are displayed when requesting approval and in workflow history [#60](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/60)
2323
* Adds support for Arabic
24-
* Improves UI in workflow detail overlay
25-
* Adds email queue for thread-safe email notifications
24+
* Improves UI in workflow detail overlay. Reduces the number of elements and shifts appropriate datapoints into tag elements.
25+
* Adds email queue for thread-safe email notifications. Emails are now processed in hosted service, via a first-in first-out queue. This resolves a reported issue where sending large numbers of emails could result in data reader errors. [#85](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/85)
2626

2727
### [13.2.1](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F13.2.1) (October 3 2024)
2828
* Ensure scheduling information is displayed in workflow history [#82](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/82)

14/umbraco-workflow/release-notes.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -18,11 +18,12 @@ Check the [Version Specific Upgrade Notes](upgrading/version-specific.md) articl
1818
This section contains the release notes for Umbraco Workflow 14 including all changes for this version.
1919

2020
### [14.1.0](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.1.0) (October 23 2024 )
21-
* Adds scheduled content locking feature
22-
* Adds support for content segments
21+
* Adds scheduled content locking feature. Documents can be made readonly until the scheduled release date passes, to ensure approved content isn't modified without workflow approval. [#84](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/84)
22+
* Adds support for readonly mode when a document is pending workflow approval. Along with the scheduled content lock, this feature requires Umbraco 14.3.0, which is now the minumum version dependency for Umbraco Workflow v14.
23+
* Adds support for content segments. Segment names are displayed when requesting approval and in workflow history [#60](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/60)
2324
* Adds support for Arabic
24-
* Improves UI in workflow detail overlay
25-
* Adds email queue for thread-safe email notifications
25+
* Improves UI in workflow detail overlay. Reduces the number of elements and shifts appropriate datapoints into tag elements.
26+
* Adds email queue for thread-safe email notifications. Emails are now processed in hosted service, via a first-in first-out queue. This resolves a reported issue where sending large numbers of emails could result in data reader errors. [#85](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/85)
2627

2728
### [14.0.3](https://github.com/umbraco/Umbraco.Workflow.Issues/issues?q=is%3Aissue+is%3Aclosed+label%3Arelease%2F14.0.3) (October 3 2024)
2829
* Ensure scheduling information is displayed in workflow history [#82](https://github.com/umbraco/Umbraco.Workflow.Issues/issues/82)

0 commit comments

Comments
 (0)