More > Configuration Manager > Working with Configuration Manager > Automation Policies > Automation Policies User Interface > Automation Policies Page

Automation Policies Page

Note This module is only valid for use by customers who purchased the relevant license for Universal CMDB Configuration Manager versions 9.2 or 9.3. New customers cannot purchase this license.

It is recommended using the UCMDB Browser Automation widget (also available in the embedded UCMDB Browser in Configuration Manager) to configure automated flows that are based on Configuration management conditions. For details, see the section about the Automation widget in the UCMDB Browser online help.

Configuration Manager provides out-of-the-box automation policies. To see a description of each policy, select the required policy in the Policies pane. The description of the policy appears in the Description box in the General pane.

This page enables you to define and edit automation policies.

To access Select Administration > Automation Policies.
Important information You must have Automation Policies permission to work with this module.
Relevant tasks
See also Automation Execution Dialog Box.

User interface elements are described below:

UI Element (A-Z) Description
Edit an action Add New Policy. Create a new policy.
Edit an action Delete Policy. Delete the selected policy.
Edit an action Save All. Save all the changes made to the current policy.
Click Refresh to update the information on the Policy Management page.
ClosedPolicies Pane

User interface elements are described below:

UI Element (A-Z) Description
<List of policies> Displays the list of out-of-the-box and user-defined automation policies.
ClosedGeneral Pane

User interface elements are described below:

UI Element (A-Z) Description
Description Enter the policy description.
Perform validation

Select the scope of the policy's validity. The available options are:

  • Valid From. If only this check box is selected, the policy's validity begins from the date selected in the calendar and is always valid. Click the calendar buttons to select the date and time for the beginning of the period.

  • Valid Until. Select a fixed period for which the policy is valid. To select a fixed period, you must select the check boxes of both Valid From and Valid Until. Click the calendar buttons to select the date and time for the end of the period.

Note If neither of the check boxes are selected, the policy validation is never calculated.
Policy Name Enter a unique policy name.
ClosedScope Pane

User interface elements are described below:

UI Element (A-Z) Description
Assign CI Type

The CI type of the CIs to be tested against the policy.

Click the Edit an action button to open the select CI Type dialog box, which enables you to select the required CI type.

At least one CI of the CI type selected must appear in the impact topology map for policy validation to be calculated.

For example, if there is a collision on a Unix type CI in your view, but in the Assign CI Type box, you selected Windows, the policy is not evaluated for the Unix type CI.

If there is no CI of the type Windows in your topology map, the policy is not evaluated.

Note If no CI type is specified, then the policy applies to all CIs.
Assign policy to views

Enables you to select the views to which the policy applies.

  • All Views. Apply the policy to all managed views.

    Note You need Authorize permission to apply a policy to all views, including the views you are not managing. If you do not have Authorize permission, you can only apply the policy to the view you are managing.

  • Selected Views. Select a view to which to apply the policy. Click the Edit an action button to open the Select Views dialog box.

Note If you do not select either All Views or select a view from the Selected Views option, the policy validity is not calculated.
ClosedRestrictions Pane

User interface elements are described below:

UI Element (A-Z) Description
Automation Restriction Conditions

Describes the automation restriction conditions for this policy.

For example, you can define a policy which stipulates that running your automation for the first time causes a policy breach.

Note The AND operator connects all the conditions defined. Therefore, the policy is breached only if the automation complies with all of the conditions defined for this policy.

For a list of the operators used to define attribute conditions, see Attribute Operators.

For a description of the conditions you can define, see Automation Execution Dialog Box.
CI Restriction Conditions

Describes the CI restriction conditions for this policy.

The AND operator connects all the conditions defined. Therefore, the policy is breached only if the automation complies with all of the conditions defined for this policy.

There must be at least one CI in your impact map that complies with all the conditions defined for the policy to be breached.

  • The breached CI must comply with all conditions in the CI Restriction pane.

  • The CI must be in the view selected in the Scope pane.

  • The CI must be of the CI type, or sub-type of it, selected in the Assigned CI Type box.

For a list of the operators used to define attribute conditions, see Attribute Operators.

The CI Restriction conditions are:

  • Collision exists. Checks whether a collision (direct or indirect) exists.

  • Direct Collision exists. Checks whether a direct collision exists.

  • Impact importance. Checks the impact importance level.

  • Impact severity. Checks the impact severity level.

  • Indirect collision exists. Checks whether an indirect collision exists.

For more information about collisions, see Automation Execution Dialog Box.

For more information on impact importance and impact severity, see Automation Analysis > Impact - <State> Pane.