Limiting Task Actions by Environment

Task action rules set global limits on the available deployment and failure task actions for selected environments and environment groups.

One example where action rules for environments are important is when you execute deployment tasks that use the ChangeMan ZMF plugin. The final approval of change packages should be limited to only production environments, because upon this approval, the installation is immediately started. Therefore, the Approve (PROD) action should be allowed only on production environments.

Another example is when you execute deployment tasks that use the Deployment Automation plugin. You may want to disallow running component processes on production environments.

All task action rules apply to all future release items. The main purpose for this feature is to set rules that should apply across the system. However, if necessary, administrative users can select just specific rules for a release item if they don't want all of the rules to apply.

Viewing the Rules for a Release Item

To view the task action rules that are set for a release package or deployable release train, view the release package and in the History tab, expand the System section. The list of rules appears in the Task Action Rules field. If no rules are listed, all rules that are defined apply.

Rules and Task Templates

Task action rules are not enforced in task templates at the time their tasks are created. Instead the rules are enforced for tasks created from task templates, based on the rules set for the release package or deployable release train. Even if the rule is not visually apparent at the time the deployment or failure task is created from the task template by grayed out environments, it will be enforced at the time of deployment.

For more details, see the following:

• Adding Global Task Action Rules
• Filtering Rules for Specific Release Items