Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Universal CMDB

More > Configuration Manager > Working with Configuration Manager > Explore Views > Explore Views User Interface > Automation Execution Dialog Box

Automation Execution Dialog Box

This dialog box enables you to run a controlled or non-controlled automation.

To access	Select Explorer > Explore Views. In the Composite CIs pane, select the required CI and click the Run Automation button.
Important information	To enable the Run Automation button, ensure that: You select Actual State or Authorized State from the toolbar. There is a managed automation mapped to a CI type in the Automation Setup module that is the same as the CI type of the selected CI in the Composite CIs pane. For details, see Automation Setup Page. Only users with Automation Execution permission are able to run an automation.
Relevant tasks	Run a Controlled or Non-Controlled Automation
See also	Impact Analysis Automation Policies System Operation Automation

Automation Execution Page

This page enables you to select the automation you want to run.

User interface elements are described below:

UI Elements (A-Z)	Description
Automation Details	Name. The name of the automation as defined in Administration > Automation Setup. Flow UUID. The Operations Orchestration instance name that uniquely identifies the Operations Orchestration instance being used by Configuration Manager. Flow Path. The full path and original name of the flow in Operations Orchestration. Description. The description of the automation as defined in Administration > Automation Setup.
Automations	Displays a list of automations you can run. The automations appear after they are imported from Administration > Automation Setup. For details, see Import a flow from Operations Orchestration. The automations that appear are relevant to the CI type you chose in the Composite CIs pane in the Explore Views page.
Execution Parameters	Indicates the execution parameters needed to run the flow. Only required fields, as indicated by a red asterisk, are mandatory. Note Configuration Manager does not allow you to run an automation whose required execution parameters values have not been configured. If you do not configure the required parameters when running a non-controlled automation, the Run Automation button is disabled. If you do not configure the required parameters when running a controlled automation, the Next button is disabled.
Execution Type	Displays whether the automation was configured as controlled or not controlled in Administration > Automation Setup.
Next/Run	This button appears as Next for a controlled automation. Click this button to take you to the Automation Planner. This button appears as Run for a non-controlled flow. This button is disabled if the required fields have not been filled in. If you ran a non-controlled automation, a window opens with the following message: `The automation is running. Click here to view a detailed report.` The word here is a link that opens Operations Orchestration, with the report of the automation result.

Automation Planner Page

User interface elements are described below:

Important information

This page is only available only when you are running a controlled automation.

It contains the following panes:

Implementation Details Pane
Policies Pane
Automation Analysis > Impact - <State> Pane
Automation Analysis > Automation Pane
Automation Analysis > Collisions Pane

Implementation Details Pane

This pane enables you to set the date and time for the planned start of the automation.

User interface elements are described below:

UI Elements (A-Z)	Description
Expected End Time	Displays the estimated time at which the automation process is expected to end. Hold the pointer over the expected end time to display a tooltip showing the expected duration time of the automation process. The first time the automation is run, the duration is 10 minutes. After the automation has been run for the first time, Configuration Manager updates the duration time by calculating the average time each automation took, and adding a safety buffer.
Flow Properties	Displays the automation parameters. Note If you delete the required execution parameters, the OK button is disabled.
Planned Start Time	Enables you to use the calendar to set the date and time you want the automation to start running. You can use the default, which is the current time, or choose a future date to reschedule the automation execution to run at a later time. If you choose a future date, Configuration Manager recalculates all the automation analysis and policy information in the Automation Planner page.

UI Elements (A-Z)

Description

Expected End Time

Displays the estimated time at which the automation process is expected to end.

Hold the pointer over the expected end time to display a tooltip showing the expected duration time of the automation process. The first time the automation is run, the duration is 10 minutes.

After the automation has been run for the first time, Configuration Manager updates the duration time by calculating the average time each automation took, and adding a safety buffer.

Flow Properties

Displays the automation parameters.

Note If you delete the required execution parameters, the OK button is disabled.

Planned Start Time

Enables you to use the calendar to set the date and time you want the automation to start running. You can use the default, which is the current time, or choose a future date to reschedule the automation execution to run at a later time.

If you choose a future date, Configuration Manager recalculates all the automation analysis and policy information in the Automation Planner page.

Policies Pane

This pane enables you to view the status of the policies defined in the Automation Policies module.

See also

Policies

User interface elements are described below:

UI Elements (A-Z)	Description
	Enables you to toggle between hiding/displaying the policy details. Hold the pointer over the policy name and click to display the policy information, as defined in Administration >Policies > Automation Policies. For details, see Automation Policies Page. Description. The policy description. Associated Views. The view(s) assigned to the policy. Associated CI Type. The CI type with which the policy is associated. Restriction. The conditions defined for the policy. Type of condition. The options are Automation Related or CI Related. Condition. The automation/CI conditions defined for this policy. Automation Analysis. The condition value defined for that restriction. The policy is breached only if the automation complies with all of the conditions defined for this policy. Click to hide the policy details.
<List of automation policies >	Displays the list of the automation policies defined in the Automation Policies module. Each policy is determined to be either in-breach or not breached. Denotes a situation in which the automation does not fulfill all of the conditions defined for this policy. Denotes a situation in which the automation fulfills all of the conditions defined for this policy. You can choose to either ignore the breached policies if you find that the breach does not pose a risk to your IT environment and run the automation despite the breach, or decide not to run the automation if the breach is critical. In addition, you can choose to reschedule the automation to run at a later time. For example, if a breached policy defines that an automation whose elapsed time since the last execution is greater than a month causes a breach, you might decide that this does not pose a risk, as opposed to a breach which causes server downtime. Note Configuration Manager enables you to run the automation even if there are automation policies that are breached.

UI Elements (A-Z)

Description

Enables you to toggle between hiding/displaying the policy details. Hold the pointer over the policy name and click to display the policy information, as defined in Administration >Policies > Automation Policies. For details, see Automation Policies Page.

Description. The policy description.
Associated Views. The view(s) assigned to the policy.
Associated CI Type. The CI type with which the policy is associated.
Restriction. The conditions defined for the policy.
- Type of condition. The options are Automation Related or CI Related.
- Condition. The automation/CI conditions defined for this policy.
- Automation Analysis. The condition value defined for that restriction. The policy is breached only if the automation complies with all of the conditions defined for this policy.

Click to hide the policy details.

Displays the list of the automation policies defined in the Automation Policies module. Each policy is determined to be either in-breach or not breached.

Denotes a situation in which the automation does not fulfill all of the conditions defined for this policy.

Denotes a situation in which the automation fulfills all of the conditions defined for this policy.

You can choose to either ignore the breached policies if you find that the breach does not pose a risk to your IT environment and run the automation despite the breach, or decide not to run the automation if the breach is critical. In addition, you can choose to reschedule the automation to run at a later time.

For example, if a breached policy defines that an automation whose elapsed time since the last execution is greater than a month causes a breach, you might decide that this does not pose a risk, as opposed to a breach which causes server downtime.

Note Configuration Manager enables you to run the automation even if there are automation policies that are breached.

Automation Analysis > Impact - <State> Pane

This pane describes how to view the impact analysis calculation results for an automation. It displays the business and system CIs that are affected by the automation. This includes general information about the affected business or system CIs and an indication of the severity of the impact of the automation.

Important information

The title of the pane indicates whether analysis calculates the effects of the automation on CIs from the Actual or Authorized state of the view. The default is Actual.

To select the state by which you want to manage your view, navigate to Administration > Settings > Application Management > Impact.

See also

User interface elements are described below:

UI Elements (A-Z)	Description
Highest Business Criticality	Displays the CIs having the highest business criticality level of the CIs impacted by the automation. The Business Criticality attribute is defined in Universal CMDB, in which levels of importance are assigned to your business CIs. Each business CI can be assigned an importance level between 1 and 10. The business criticality level of a CI in Universal CMDB is mapped as follows: 0-2 in Universal CMDB ---> Low in Configuration Manager 3-5 in Universal CMDB ---> Medium in Configuration Manager 6-8 in Universal CMDB ---> High in Configuration Manager 9-10 in Universal CMDB ---> Critical in Configuration Manager The following icons indicate the business criticality levels: Critical High Medium Low Click the drill down arrow to display a table that contains a list of the CIs that have the highest business criticality level. The table includes the CI name, CI type, impact severity level, and business criticality level of each CI in the table. A tooltip indicating the impact severity and business criticality levels of the CI is visible when you hold your pointer over the severity and criticality icons. Click this arrow to hide the table.
Total Business CIs	Displays the total number of business CIs impacted by the automation. Click the drill down arrow to display a table that contains a list of the impacted business CIs. The table includes the CI name, CI type, impact severity level, and business criticality level of each CI in the table. For information on the icons that indicate the impact severity levels, see Worst Impact Severity in this table. A tooltip indicating the impact severity and business criticality levels of the CI is visible when you hold your pointer over the severity and criticality icons. Click this arrow to hide the table.
Total System CIs	Displays the total number of system CIs that were impacted by the automation. Click the drill down arrow to display a table that contains a list of the impacted CIs. The table includes the CI name, CI type, and impact severity level of each CI in the table. A tooltip indicating the impact severity level of the CI is visible when you hold your pointer over the severity icon. Click this arrow to hide the table.
Worst Impact Severity	Displays the CIs that have the highest impact severity level of the business CIs that have been impacted. The following icons indicate the following impact severity levels: Critical High Medium Low Very Low Click the drill down arrow to display a table that contains a list of the business CIs that have the highest impact severity level. The table includes the CI name, CI type, impact severity level, and business criticality level of each CI in the table. A tooltip indicating the impact severity and business criticality levels of the CI is visible when you hold your pointer over the severity and criticality icons. Click this arrow to hide the table.

Automation Analysis > Automation Pane

This pane provides general information regarding previous automation runs.

Important information	Statistics are calculated for controlled and non-controlled automation runs, but only the statistics for controlled executions are displayed in the Automation Analysis > Automation pane.
See also	Policies

User interface elements are described below:

UI Elements (A-Z)	Description
Causes Configuration Change	Specifies whether the automation causes a change to the CI in Universal CMDB.
Causes Downtime	Specifies whether or not the managed automation causes the CI to become unavailable during the execution.
Execution Ratio	Displays the percentages of successful and failed runs for this automation. The success ratio is displayed in green. The failure percentage is displayed in red.
Expected Duration	Displays the estimated time duration of the automation process. The first time the automation is run, the expected duration is 10 minutes. After the automation has been run for the first time, Configuration Manager updates the duration time by calculating the average time each automation took, and adding a safety buffer.
Last Execution	Displays the date and time, or just date, on which the last automation execution ran. If the automation ran in the last 48 hours, it displays both the date and the time. If it ran more than 48 hours before the current time, it only displays the date.
Number of Executions	Displays the number of times the automation has run.
Risk Evaluation	Displays the level of risk in the managed automation. Valid values are: Unknown None Low Medium High
Successful Consecutive Executions	Displays the number of consecutive times the automation has run successfully.

Automation Analysis > Collisions Pane

This pane displays the details of the factors causing the automation collision.

Relevant tasks	Run a Controlled or Non-Controlled Automation
See also	Automation Collisions Requests for Change

User interface elements are described below:

UI Elements	Description
<Collision exists> <Collision does not exist>	Indicates whether or not the automation is colliding with another automation/RFC. A collision occurs when a common CI is impacted by more than one automation/RFC running over the same period of time. The collision can be caused due to an automation that is: Colliding with other automations currently running or scheduled to run in Configuration Manager. or Colliding with an RFC that is currently being implemented or scheduled to be implemented in Micro Focus Service Manager.
Total Collisions on CIs	Displays all the commonly affected business/system CIs that are involved in collisions. Click the drill down arrow to display a table that contains a list of the CIs involved in collisions. The table includes the CI name, CI type, collision type. The following icons indicate the collision types: Direct collision. The business/system CI is directly affected by the collision. Indirect collision. The business/system CI is indirectly affected by the collision. A tooltip indicating the collision type of the CI is visible when you hold your mouse over the collision type icons. Note regarding system CIs only: Only top level (composite) CIs are displayed. If colliding automations cause collisions on more than one CI, the severity is determined by the collision with the highest severity. Click the arrow to hide the table.
Total Colliding Activities	Colliding Automations Indicates the total number of colliding automations running or scheduled to run in Configuration Manager. Colliding RFCs Configuration Manager imports from Universal CMDB requests for change (RFCs) that were opened in Micro Focus Service Manager. Every RFC is associated with at least one CI. Colliding RFCs refer to the total number of automations currently running or scheduled to run in Configuration Manager that collide with RFCs that are currently running or scheduled to run in Micro Focus Service Manager. For information on how Configuration Manager retrieves RFCs, see Requests for Change.

UI Elements

Description

Indicates whether or not the automation is colliding with another automation/RFC.

A collision occurs when a common CI is impacted by more than one automation/RFC running over the same period of time.

The collision can be caused due to an automation that is:

Colliding with other automations currently running or scheduled to run in Configuration Manager.

or
Colliding with an RFC that is currently being implemented or scheduled to be implemented in Micro Focus Service Manager.

Total Collisions on CIs

Displays all the commonly affected business/system CIs that are involved in collisions.

Click the drill down arrow to display a table that contains a list of the CIs involved in collisions. The table includes the CI name, CI type, collision type.

The following icons indicate the collision types:

Direct collision. The business/system CI is directly affected by the collision.

Indirect collision. The business/system CI is indirectly affected by the collision.

A tooltip indicating the collision type of the CI is visible when you hold your mouse over the collision type icons.

Note regarding system CIs only: Only top level (composite) CIs are displayed.

If colliding automations cause collisions on more than one CI, the severity is determined by the collision with the highest severity.

Click the arrow to hide the table.

Total Colliding Activities

Colliding Automations

Indicates the total number of colliding automations running or scheduled to run in Configuration Manager.
Colliding RFCs

Configuration Manager imports from Universal CMDB requests for change (RFCs) that were opened in Micro Focus Service Manager. Every RFC is associated with at least one CI.

Colliding RFCs refer to the total number of automations currently running or scheduled to run in Configuration Manager that collide with RFCs that are currently running or scheduled to run in Micro Focus Service Manager.

For information on how Configuration Manager retrieves RFCs, see Requests for Change.