Adding a Policy with Multiple Actions

You can create policies that perform multiple sequential actions. Policy conditions are reevaluated before triggering each policy action.

Here are sample use cases for multiple action policies:

• Create a policy that starts an environment followed by a scale up action to run every Monday morning at 7 a.m.

  This policy would make sure that the environment automatically starts and adds an extra node to handle more load on the system.

• Create a policy to scale down followed by a stop environment to run Friday at 9 p.m.

  This policy would scale down and stop automatically, thereby eliminating resource usage over the weekend and providing a cost savings.

• Create a policy to back up the environment and then refresh.

  This policy will ensure the environment is properly backed up and available if the refresh fails.

• Create a policy that is run when an Infrastructure CPU DPK is downloaded in the Repository, to back up the environment, apply Infrastructure CPU, and send an email notification.

This is an example of a policy that will back up an environment and then refresh the environment.

This example illustrates the fields and controls on the Add Policy page for a policy containing multiple actions when the Policy Object is Environment.

This is an example of a policy with multiple actions for a Repository Artifact. When a PeopleTools 8.60 Infrastructure CPU is downloaded, the policy will stop the specified environment, take a backup, start the environment, apply Infrastructure CPU patches, and then send an email notification.

This example illustrates the fields and controls on the Add Policy page for a policy containing multiple actions when the Policy Object is Repository Artifact.