Publishing Changed Pages

Changed pages are published after authors modify the document by checking out, editing, and checking in document fragments.

1. Right-click the SGML document, and choose Publish > Publish Change Pages.
   The Publish Change Package dialog appears.
2. In the Package Location field, specify the repository folder where the change package will be stored.
   You can change the default value that appears here on a document-by-document basis from the Show Change Packages dialog.
3. Verify the Package Name meets your naming conventions.
   The Package Name field is supplied with a default name. This name acts as a label for the name of the change package that displays in the Show Change Packages dialog. You can change this name from the default to match your own naming conventions. However, if you leave the default string, Astoria will automatically generate the next sequential package name when you publish an update.
4. Verify that the Change Pages check box is selected.
   If not, an initial baseline has probably not been published for this document. See Publishing the Initial Baseline for more information.
5. Verify the Change Level field displays a value that is incremented one from the previous publish operation.
   The Change Level field should display a default value calculated from the previous change cycle. If this is the first set of change pages published since the baseline, the default value is 1.

   Important: Change packages must be published in sequential order, since Arbortext CPD uses this change level to determine which pages to display and how to label the changes in the List of Effective pages.
6. Select the Change Pages Only check box.
   Selecting this option generates just the pages that have changed in this release. If the check box is cleared, both the changed pages and all the pages will be generated in two separate PDF documents.
7. Set the Issue Date field to the date you want to display in the document.
   This does not need to match the date you actually run the publish command, and usually reflects the official release date of the document. The time is not included in the printed date.
8. Click OK.