You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: 18/umbraco-workflow/release-notes.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,11 +22,11 @@ This section contains the release notes for Umbraco Workflow 18, including all c
22
22
23
23
#### Element type workflow support
24
24
25
-
Workflows can now be applied to element types, not just documents. This extends the same multi-stage approval workflow model to the new element content type introduced in Umbraco 18. Element folders are also supported, allowing workflow configuration inheritance down nested element folder hierarchies.
25
+
Extends Workflows' multi-stage approval workflow model to the new element content type introduced in Umbraco 18. Element folders are also supported, allowing workflow configuration inheritance down nested element folder hierarchies.
26
26
27
27
#### Workflow actions
28
28
29
-
A new extensible action system allows configuring pre-approval and post-approval actions per document type. Actions execute automatically before or after a workflow completes, and can optionally block the workflow on failure.
29
+
A new extensible action system allows configuring pre-approval and post-approval actions per Document Type. Actions execute automatically before or after a workflow completes, and can optionally block the workflow on failure.
30
30
31
31
Developers can create custom actions by implementing `IWorkflowAction` or extending `WorkflowActionBase<TConfig>`, and register them via `WorkflowActionCollectionBuilder`. A built-in Webhook action ships as the first implementation, sending a POST request with workflow instance details to a configured URL.
32
32
@@ -40,7 +40,7 @@ This simplification enables element type support and provides a single API surfa
40
40
41
41
#### Standalone settings workspaces
42
42
43
-
Content Approvals, Content Reviews, and Release Sets settings have each been converted from tree nodes within a shared settings workspace to standalone workspaces with dedicated URL routes. The previous settings tree is replaced with a menu and sidebar pattern, providing a cleaner, more focused navigation experience.
43
+
Content Approvals, Content Reviews, and Release Sets settings have been converted to standalone workspaces with dedicated URL routes. The previous settings tree is replaced with a menu and sidebar pattern, providing a cleaner, more focused navigation experience.
44
44
45
45
#### Frontend performance
46
46
@@ -50,7 +50,7 @@ Content Approvals, Content Reviews, and Release Sets settings have each been con
50
50
51
51
#### Backend modernization
52
52
53
-
* Feature-slice namespace reorganization: models and view models previously in flat `Umbraco.Workflow.Core.Models`/`ViewModels` namespaces are now organized into feature-specific namespaces (e.g.`ContentApprovals`, `ApprovalGroups`, `Settings`).
53
+
* Feature-slice namespace reorganization: models and view models previously in flat `Umbraco.Workflow.Core.Models`/`ViewModels` namespaces are now organized into feature-specific namespaces (for example,`ContentApprovals`, `ApprovalGroups`, `Settings`).
54
54
* All previously `[Obsolete]` members from v17 have been removed.
55
55
* Legacy migrations (pre-v17) removed. Fresh installs use a single `InitialCreate` migration.
56
56
* SwaggerGen replaced with `Microsoft.AspNetCore.OpenApi`.
Copy file name to clipboardExpand all lines: 18/umbraco-workflow/upgrading/version-specific.md
+4-1Lines changed: 4 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,10 @@ DTOs were also renamed from `Poco` to `Dto` suffix to remove the implied couplin
45
45
46
46
The list below includes changes raising validation errors `CP0001`, `CP0002` and `CP0006` between versions 17.3.2 and 18.0.0-rc1.
47
47
48
-
Of note are the removal of split config models in favor of unified `ConfigUpdateRequestModel`, the consolidation of `NodeId`/`ContentTypeId` into `EntityId` on permission models, and the removal of previously obsoleted members on `IWorkflowInstanceResolver`, `IEmailTemplateLocator`, and `IPropertyValueTransformer`.
48
+
Noteable changes include:
49
+
* removal of split config models in favor of unified `ConfigUpdateRequestModel`
50
+
* consolidation of `NodeId`/`ContentTypeId` into `EntityId` on permission models
51
+
* removal of previously obsoleted members on `IWorkflowInstanceResolver`, `IEmailTemplateLocator`, and `IPropertyValueTransformer`.
0 commit comments