Automatic State Transition

Configuration Manager includes an automatic state transition feature that enables you to define the conditions under which changes in a view are automatically authorized. For a selected view, you define the types of changes approved, the CI types for which changes are approved, and whether or not to allow new policy breaches. You can choose to automatically authorize the changes in a view only when all changes meet the defined conditions, or to automatically authorize individual changes that meet the defined conditions (other changes will not be authorized). All CIs that breach one or more rules will not be authorized, and the CIs that are dependent on them will also not be authorized. The remainder of the CIs will be authorized.

Take the following examples of how authorization is applied: You select the CI types computer and net device as approved for changes, and you select Added CI as the only approved type of change, and you select not to allow any new policy breaches:

  • When view level authorization is specified, the only change approved for authorization is the addition of a CI of type computer or net device. If any other type of CI is added to the view, or if any CI in the view is removed or modified, none of the changes are automatically authorized. Similarly, if new policy breaches are detected in any CI, the authorization does not proceed. If, for example one computer is added and another computer is removed, none of the changes are automatically authorized, even though the added computer CI meets the rules.

  • When CI level authorization is specified, only the addition of computer or net device will be authorized. The rest of the changes will not be authorized.

    If no new policy breaches are allowed and the view contains a new topology policy breach - then none of the changes will be authorized, since there is no way to know which change caused this breach. If there are only new baseline policy breaches, then only the CIs that are in breach against their baseline policy will not be authorized.

You can define different authorization conditions for each individual view. Automatic state transition is executed for all changes that match the relevant authorization conditions in any of the views.