Automated publishing and unpublishing
Automated publishing and unpublishing uses rules to schedule and sequentially execute actions for your assets, such as publishing, unpublishing, or information enrichment. This reduces manual effort and makes rule-based management more efficient.
Prerequisites
Table assets: You have enabled the Intelligent R&D Edition or purchased the asset operations - Standard Edition add-on module.
Metric assets and dashboard assets: You have enabled the Intelligent R&D Edition or purchased the asset operations - Advanced Edition add-on module.
API assets: You have purchased the data service feature and either enabled the Intelligent R&D Edition or purchased the asset operations - Advanced Edition add-on module.
Automated publishing rules
Automated action settings consist of rule groups and rules. A rule group contains a set of rules that apply to the same assets. To prevent conflicts and unexpected results, the asset scopes of different rule groups cannot overlap.
First, you define a broad asset scope for the rule group. Then, within each rule, you can narrow this scope to target specific assets.
A rule group can contain multiple rules. Different rule groups run in parallel, while rules within a single rule group execute sequentially. You can set the execution order of rules within a group, and this order can affect the final outcome. We recommend the following order: do not publish > information enrichment > auto-publish > auto-unpublish.
do not publish: To avoid unnecessary resource consumption, we recommend running the do not publish rule before the information enrichment rule.
information enrichment: For a specific asset, we recommend running the information enrichment rule before the auto-publish rule.
auto-publish: Publishes assets sequentially based on the rules in the specified rule group.
auto-unpublish: Unpublishes assets sequentially based on the rules in the specified rule group. This action is typically applied to assets that have been deleted.
Execution results are affected by rule order: The available actions depend on the state of an asset. For example, an auto-publish rule cannot process an asset marked as 'do not publish'. Similarly, a 'do not publish' rule can only target a candidate asset. Because of these dependencies, changing the execution order of rules can lead to different outcomes.
Execution result: For each asset that a rule processes, the system creates a record detailing the execution result and any exceptions. You can filter these records to view the impact of a specific rule on all its target assets, or to trace the complete history of an asset across all rules in its rule group.