Compliance Job - General
The General panel lets you provide information that identifies a Compliance Job and provides some options for how the job should execute.
Optional descriptive text.
Folder in which to store the object.
Set execution override
Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.
Clear execution override
Remove an existing execution override.
Number of targets to process in parallel
Choose one of the following options:
Continue despite compliance data collection errors
Whether Compliance evaluation should continue on a target server or component even though it encounters required parts that are missing or that throw errors.
If you select this option and the target server is unreachable (for example, the server is down or the RSCD agent is down), the resulting compliance status depends on exact rule structure.
For example, the following two rules are designed to evaluate file permissions:
Whether to authorize the Compliance Job to perform component discovery for the associated component templates and generate components for use in the Compliance Job. This replaces the need to manually run a Component Discovery Job before running the Compliance Job.
Note: When you are using this option in combination with extended objects and a large number of targets, this can either slow your system performance or the job might fail.
Workaround: Disable the Run auto-discovery option and run a batch job manually where a Component Discovery job is executed before the Compliance job.
See the following video for an example of how to use this option to automatically filter the targets for the job.