Create collections of content to publish according to multi-stage scheduling rules.
Release Sets are collections of Alternate Versions, where each version can be scheduled independently. Release Sets provides a holistic overview of scheduled content and enables building and managing content schedules to drive digital campaigns.
Release Sets is currently (v16.0.0) available behind a feature flag. To enable the feature, add the following to the appsettings.json file:
"Umbraco": {
"Workflow": {
... // other settings
"FeatureFlags": ["ReleaseSets"]
}
}Ensure the User Group permissions are set to allow appropriate access.
Navigate to the Release Sets dashboard in the Content section.
Click the Create button to open a workspace modal to create a new set.
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.
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.
Click the Add document button.
Select the document node from the picker.
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 workspace editor.
Add an existing version or create a version to display it in the version editor.
Enter the date and time in the Publish at field.
Click Schedule publish to schedule the selected version.
You can add multiple versions of the same document and schedule them in sequence.
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.
Select a day in the calendar to display the scheduled content changes for that date.
Click the Add button in the calendar dialog to add items to the Release Set.
A Release Set can be published immediately or scheduled for future publication. To publish a Set, all assigned versions and tasks must be either Ready to publish (versions) or Complete (tasks). If all components in the Set are in the required status, it can be published by a user with the appropriate permission.
Publishing content within the Release Set is managed by a recurring hosted service, similar to scheduled content publishing.
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.
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.
Last updated 30 minutes ago
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4