Hey Ann

When a user hits the publish button (in Publication Manager or Web Client), a background process is started that initiates the publishing process. The publishing process is a sequence of plugins that get executed (determine what objects to export to the file system, resolve conditions, resolve variables, check the status of all objects, check if all hyperlinks can be resolved in the collection, ...). The status of any object in the publication is taken into account and if any of the objects is not "released", you will get an output in a draft status, with indication of warnings telling the user why the output is draft.

Users can publish any time to check what the output currently looks like or to check what warnings there are.

Not sure what the business reasons are behind your question, but in theory you could create a custom publishing plugin that could cause publishing to "fail" early in the process if certain criteria are not met. For instance, you could create a plugin that abandons publishing (and causing it to fail) if for instance the map is not released. But not sure if that would be practical/usable as users should be able to publish output even when not all content is released. If you release the map to get publishing going and then you find out that a topic is missing, you would have to create a new version of the map.

If the business reason is that there is too much load on the publishing server, you could on the one hand ask users to only publish if they really have a compelling reason. Or you could consider adding an additional publishing server so that more publishing jobs can be processed in a given amount of time.

BR

Kurt

Very useful answer Kurt, thank you for the advice.

Regards,

Ann

 In Publication Manager, the publishing process typically includes all content regardless of its status. However, it's worth checking if there are any settings or configurations that allow you to filter out unpublished or incomplete maps and topics before finalizing the output.