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
A Release Set is comprised of document versions and (optionally) tasks. Tasks are like to-dos that should be tracked alongside the Release Set, but are not necessarily CMS activities.
35
41
36
42
For example, a task might be to finalize digital advertising. It is not a CMS activity, but it is a requirement that must be met before publishing the Release Set.
37
43
38
44
### Adding documents
39
45
40
-
- Click the **Add document** button.
41
-
- Select the document node from the picker.
42
-
- Add or create a new version of the selected document in the versions editor.
43
-

44
-
- Adding an existing version opens the version picker. Creating a new version opens the [Alternate Version](../alternate-versions/alternate-versions.md) workspace editor.
45
-

46
-
- After selecting or creating a version, it is displayed in the version editor.
- After submitting the modal, the updated versions are displayed in the overlay. The documents list shows the selected documents, while the calendar shows the Release Set and its components.
53
-

54
-
- Selecting a day in the calendar displays the scheduled content changes for that date.
55
-

56
-
- The `Add` button in the calendar day dialog allows adding items to the Release Set, similar to the `Add document` button in the main overview.
46
+
1. Click the **Add document** button.
47
+
2. Select the document node from the picker.
48
+
3. Add or create a new version of the selected document in the version editor.
Adding an existing version opens the version picker. Creating a new version opens the [Alternate Version](../alternate-versions/alternate-versions.md) workspace editor.
7. Click the **Add** button in the calendar dialog to add items to the Release Set.
57
80
58
81
### Publishing a Release Set
59
82
@@ -63,4 +86,4 @@ Publishing content within the Release Set is managed by a recurring hosted servi
63
86
64
87
As publishing progresses, each document version is promoted to be the current backoffice draft, and then published as normal. A version of the original backoffice draft is preserved as an Alternate Version and can be republished or edited in the future.
65
88
66
-
When a Release Set has no further changes to publish, the status is updated to `Complete`. The Set can then be deleted, or updated and republished. Content published within the Set is preserved and can be further edited or included in a new Release Set.
89
+
When a Release Set has no further changes to publish, the status is updated to `Complete`. The Set can then be deleted, or updated and republished. Content published within the Set is preserved and can be further edited or included in a new Release Set.
0 commit comments