Disabling collision management and impact analysis

If your organization does not use collision management or impact analysis functionality for Change Management, you can choose to disable these features. You do so by running a command line utility that disables the functionality for a specific tenant instance (or for the default tenant, if multitenancy is not enabled). You can also enable the functionality again if you choose to begin using it at another time. 

Related topics

Detecting-collisions-between-change-requests

Analyzing-the-risk-and-impact-of-change-requests-in-the-Review-and-Authorize-stage

When you disable collision management:

  • The change calendar in the universal client still shows change requests in relation to the current change request, but no collisions are highlighted in a red border.
  • The alert banner on change request details does not indicate that there are collisions.
  • Users cannot take actions on collisions.
  • No collision-related notes are added to the Activity feed or Updates feed.
  • No collision-related notifications are sent.

When you disable impact analysis:

  • Users are not prompted to run impact analysis while creating a new change request.
  • The UI does not provide a way for users to run or cancel an impact analysis, or to display impact analysis results.
  • No impact analysis notifications are sent.

To disable collision management or impact analysis

You can disable collision management or impact analysis from the Centralized configuration by using the disableCollisionManagement configuration parameter. For more information, see Setting configuration parameters.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*