Auto-generated RPs are created by a separate job that has three parameters
# delay since application start till first job iteration
# delay between iterations
# define if separation is needed for critical and non critical patches
There are two types of auto-generated RPs (based on the "unified" parameter):
- Security-Critical patches
- Non critical (all other patches)
Each job iteration checks whether there are required patches not governed by other RPs
and adds (if not added) the patches to an automatically created RP by severity (critical, non critical)
If separation by severity is not required then setting the value 'true' to the property (rp.unified.auto.plan.for.all.updates) will create only one auto-generated RP for all patches
Setting the property to 'true' has no backwards influence, i.e. the previously created RPs by severity will not be unified.
An auto-generated RP may be activated like any other RP, with setting patching actions are remediation cycle.