Review/Authorize Overview

The Review/Authorize module enables you to review and authorize changes in a view. Review/Authorize displays all the CIs currently contained in the view in either the actual or authorized state. For example, an application owner might want to track and acknowledge changes that occur in their application service tree. CIs that were added to the view, removed from the view, or updated between the two states are indicated by the appropriate indicator icon in the Composite CIs pane and the Topology pane. For details on the indicator icons, see Composite CIs Pane.

You begin the authorization process by analyzing (or reviewing) the changes you want to authorize: check the type and nature of the change, whether there are new policy breaches and whether there are related RFCs. Select the changes you want to authorize from among the CIs marked as changed. When you click Authorize, all of the selected changes are submitted for authorization. After the authorization finishes, the authorized state is updated with the selected changes, and a snapshot of the view is saved. For details on manual authorization, see Authorize Changes to CIs.

It is also possible to authorize views automatically using the automatic state transition feature. The automatic state transition rules are validated against all managed CIs in the view, and the CI changes are automatically authorized if they comply with these rules. For details, see Automatic State Transition.

Before authorizing changes (either manually or during automatic state transition, Configuration Manager checks whether any CI that may be deleted as the result of authorizing a change has any other CIs that are dependent on it. A warning notice will be displayed during authorization for the following situations:

• If the removal of a CI in one view leads to the removal of its dependent CIs in another view.
• If the removal of a CI leads to the removal of a CI that is a component of the composite CI in another view.
• If CI to be removed has any relation in another view.
• If the authorization of a change in one view will cause a policy breach in another view.

Related Information