Under Community Review

Stop Publishing Button

This idea is aimed at providing administrators with enhanced control over the publication process.

The proposed feature involves the implementation of a "STOP publish" button, essentially serving as a master switch to temporarily halt all publication activities. Here's an analogy: envision an administrator pulling a lever to bring an assembly line to a halt. This functionality would act as a centralized mechanism, providing administrators with a quick and efficient means to suspend publishing processes across the entire system. 

Taking a more granular approach, we could extend this feature to operate on a publication level. This would allow administrators to stop the publication for a specific set of items (X publications) rather than a global halt affecting the entire system (Y publications)

Parents
  • Nice idea. At least at a Content Delivery environment, I could see such a UI feature to working with the Topology Manager ability to mark an environment "offline" (isDisabled=true).

    Another approach could be to offer an easier way to stop select users from publishing, so maybe by group, certain users can't queue items but admins (and publishing queue managers) could continue to publish and manage the queue. That could maybe in the UI or perhaps in Access Management.

Comment
  • Nice idea. At least at a Content Delivery environment, I could see such a UI feature to working with the Topology Manager ability to mark an environment "offline" (isDisabled=true).

    Another approach could be to offer an easier way to stop select users from publishing, so maybe by group, certain users can't queue items but admins (and publishing queue managers) could continue to publish and manage the queue. That could maybe in the UI or perhaps in Access Management.

Children
  • We can disable publishing by toggling BPT Purpose security permissions (Like Use Target Type or not). This way we can prevent some groups from using publishing Targets.

    This needs to be done carefully by taking present group permission screenshot, because while resuming publish we need to add all of them back.