Configuring Change Action Approval Control

You can configure Change Management to ensure that users who perform modifications are not the only approvers required to approve them. Users who perform modifications may still review the changes but their approvals will not be considered for the change action to be approved. Approvals from other users will be required. However, users who perform modifications may still reject the changes, their rejection will be taken into account, and the change action will be rejected.

A user may have one (or more) of these roles for a specific change action:

  • Owner
  • Change Assignee
  • Change Coordinator

Depending on the configuration you select, you can exclude change action approvals from users who have one or more of these roles. After you select the configuration, the users' approvals will not be taken into account but their rejections will continue to be.

Change action approvals can require that the change action approver list include either of:

  • Only Leaders
  • At least one Leader
  • At least Reader

To promote a change action to the In Approval state, at least one approver and the owner must be Leaders in the collaborative space, and the organization in which the change action belongs.

Note: Roles taken into account are restricted to the ones applicable to the collaborative space and organization of the change action. Therefore, in the context of at least one Leader, at least one of the approvers must be a Leader or a restricted Leader in the collaborative space, and the organization to which the change action belongs.

Be aware that it is possible to select a configuration that prevents change actions from being approved. For example, assume that to approve a change action, at least one Leader is required but only the change coordinator has the Leader role. If you select the configuration that ignores the change coordinator's approval, the change action cannot be approved and an error will occur even if everyone on the approver list approves the change.

Here is another example:

  • User1 is a CA owner and makes a change to Product1 under the CA.
  • User2 is an Assignee for the CA and makes a change to Product2 under the CA.
User1 and User2 can approve each other's changes. However, if the configuration requires that approvals for the Owner (User1) and Assignees (User2) be ignored, a third user (User3) must also approve the changes.

To configure change action approval control:

See Also
Configuring Properties
  1. Create or open the text file to contain customized properties. For more information, see Editing Properties Using MQL.
  2. Set the value for this property depending on your business requirements:

    • Remove Change Action owner from approvers checks. Ignore Change Owner in reviews.
    • Remove Change Action assignees from approvers checks. Ignore Change Assignees in reviews.
    • Remove Change Action change coordinator from approvers checks. Ignore Change Coordinator in reviews.

    For the setting that you select, the user (or users) who have the corresponding approver role will not be taken into account. If the setting removes all users from consideration, the approval will fail and an error will appear.