Managing Publishing Rules
An administrator can manage a set of reusable publishing parameters by adopting a strategy for creating, saving and deploying publishing rules. Because the type of rule is determined by the publishing process in effect when the rule is created, you need to be aware of the following:
• If the user is using Arbortext Styler or a local Print Composer option license for publishing, the rule is saved as a local rule. A local rule is available to the Arbortext Editor user only when publishing using one of these options. The user can’t select a server publishing rule.
• If the user sends publishing requests to Arbortext Publishing Engine (the Publishing Engine preference for Use Publishing Engine is checked), the rule is saved as a server rule. A server rule is still saved locally. A server rule is available to the Arbortext Editor user only when publishing with Arbortext Publishing Engine. The user can’t select a local publishing rule.
A Arbortext Editor client can display a server publishing rule list consisting of some combination of server rules that were created and saved locally combined with server rules deployed on the Arbortext PE server. The next section describes deployment strategies.
The Publishing Configuration report contains information about publishing rule files. It includes only those publishing rule files that are free of errors. If a rule file is incorrectly formed, has the same unique ID as another rule file, or some other error, that information will be noted in the publishing configuration log, but it will not be included in the Publishing Configuration report. Rule files with errors are not presented as choices to
Arbortext Editor clients. Refer to
Publishing Configuration for information.
For information on customization of Publishing Rules using advanced parameters, consult Customizing Publishing Rules in the Customizer's Guide.