Publishing Validated Content

By assigning release states to the structure builder you can enforce validation at selected points during content creation cycle. You can also use the publishing profile to enforce release state compliance on objects. Using both actions ensures that topics must meet validation to publish.

To extend the release state use through the publishing process select the Applies To tab on the publishing profile, then select the release state and select the option to enforce the release state during publishing - publishing will only complete if the objects are in the selected release state. Alternatively, you can select warn to allow the book to publish and check the publishing log for any objects that are not in the selected release state.

Object relationships and the enforce release state

When the enforce release state is used Author-it checks all objects with a relationship to the content before publishing the book. This means that all object with a relationship to content in the book (templates, style objects, hyperlinks, and so forth) are also checked, and must also have the release state applied.

Examples:

• A topic in the book contains an embedded topic. The topic that has been embedded must also have the release state applied in order for the book to publish.
• A topic in the book contains a link based on the Expanding Block template. The target topic containing the text displayed in the expanded block must be in the released state.
• The library content has been translated and the translated content is being published. A topic in the book contains a cross reference link to another topic. The reference text on the hyperlink object's Print tab must be translated. Once the reference text is translated the hyperlink template has the release state applied.