Creative Force's draft and published version functionality provides a robust system for managing changes to both Workflows and Style Guides without disrupting ongoing production. This feature allows users to make and save incremental changes while ensuring production stability. The draft system enables thorough review and validation before changes go live, reducing the risk of errors impacting the production line.
Draft vs Published Definitions
Draft Version: A temporary version that can be edited and saved without affecting production
Published Version: The active version used in production that determines Workflow V2 and Style Guide V2 behavior
Working with Draft Versions
Single Draft Rule: Only one draft version can exist at a time for each Workflow V2 or Style Guide V2. There will be a pencil icon to show if the Workflow or Style Guide has a Draft version.
Invalid configurations can be saved as drafts
All validation requirements must be met before publishing
Draft vs Published Workflow V2
Save: Save the Workflow as a Published version. All settings must be correct before publishing, otherwise the system will show warning messages.
Save as Draft: Save the Workflow as a Draft version. Draft versions cannot be connected to Style Guides.
Draft vs Published Style Guide V2
Save: Save the Style Guide as a Published version. You cannot save the style guide if the connected workflow is a draft version.
Save as Draft: Save the Style Guide as a Draft version.
Publish: Save the Style Guide as a Published version and at the same time prompt you to the Apply Updates screen.
Best Practices when to use Draft
Making complex changes requiring multiple editing sessions
Testing new configurations
Preparing major workflow updates
Collaborative review processes