Rules for Schedule Publish

Existing rules that affect Schedule Publish

Content hierarchy rules: 

• Users cannot publish a draft with an unpublished parent page.
• Users cannot unpublish a page when published sub-pages are present.

The required Seated user roles / permissions are the same as those for on-demand publish / unpublish:

• Publish: Author, Editor, Admin 
• Unpublish: Editor, Admin 
• Reporting: Admin (for all pages)

Allowed actions by page type

• Publish is only supported on a draft of a page. 
  
• Unpublish is only supported on a published / live page. 
  
• No publication is supported on a page placeholder.
  
• A schedule inherited by a sub-page through the "Apply schedule to all sub-pages" checkbox can only be modified where it was initially created. 

Allowed actions by publication status

• Publish requires the parent page to be published, and needs to be completed from top to bottom.
• Unpublish requires sub-pages to be unpublished, and needs to be completed from bottom to top.
• Unpublished hierarchy is currently supported – unpublished parent with unpublished sub-pages.

Timing

• A schedule must be created more than 15 minutes ahead of the target time, and cannot be modified or deleted less than 15 minutes from the scheduled date / time.
• Drafts must have publish schedule created for a future date / time.
• Published pages must have unpublish schedule created for a future date / time.
• There is a one-year limit on scheduling. The latest date and time a publication can be scheduled is 11pm UTC-GMT 365 days from the present date / time.
• When a page has both a publish schedule (on its draft) and an unpublish schedule (on its live), the schedule set for the later date / time will be the resulting state.
  • When unpublish is scheduled later than publish, page will be unpublished.
  • When publish is scheduled later than unpublish, the draft will be published.

Validation

Expert validates that earlier scheduled states will cause hierarchical conflicts for new scheduled states, and that new scheduled states will not cause hierarchical conflicts for later scheduled states.

The hierarchy is validated from root to terminal nodes, and from terminal nodes to root. This occurs:

• At schedule creation  
• As changes occur within the system
  Example: When a published page is moved with a scheduled unpublished page
• At schedule execution