Run All Actions as an Evaluation

When you want to test your system against all Actions, such as when you add new security technologies, you can easily do so using the Run All Actions option. This option identifies all Actions that can be run between the source and destination Actors you select, and creates an Adhoc Evaluation. This Evaluation includes groups of Actions based on Action type, with each group containing a max of 100 Actions. Therefore, you may have multiple groups for the same Action type. Before running the Job, you can set runtime parameters based on Group or Actions. When you run and View the Job, it looks like any Job that contains multiple Actions. If an Action Errors, the Job continues to the next Action, ultimately running through all Actions in the Job.

1. Go to Library > Evaluations.
2. Click Run All Actions. This launches the Actor selection window.
3. Select your Source and Destination Actors.
4. Click Run Now. The system identifies all Actions that can be run between the Actors and the Assign Actors. The Map page is displayed. Review the details.
   1. The title includes how many Actions are included and the current day and time.
   2. The Actions are grouped by Action type, with a max of 100 Actions per group, so you may see multiple groups of the same Action type.

   3. The Actors are pre-assigned to each group.

      While you can adjust the Actor assignment, it is not recommended because that goes against the purpose of running all Actions.

   4. When only one Actor is required, the Source Actor was assigned.
5. Click Run to bring up the Job Definition page.
6. (Optional) Configure runtime parameters for Actions in each group. The Action type in the group determines if you configure an overall runtime parameter for the group or if you can configure runtime parameters for each Action.

7. Click Run Now. This will take you to the Job details and start the Job.

   • This Job may take several hours to run, based on the Actor selection and total number of Actions. If an Action errors, the Job continues to the next Action until all Actions have run.
   • Similar to running Actions directly from the Queue, this Job is not associated with a VID that you can access again in the Library.
   • If there is only one Actor required, such as for DNS and Host CLI Actions, the Job uses the source Actor.