The PMCHGAUTH1 authorization process
The built-in PMCHGAUTH1 subprocess workflow conducts a series of steps to ensure that your Change is properly authorized. If this workflow is used, authorization assignments are sent according to authorization level. In the built-in PMCHGMAIN1 workflow, the PMCHGAUTH1 subprocess workflow is used by default for the authorization phase.
About this task
The PMCHGAUTH1 workflow performs the following operations to ensure that your Change is authorized:
- Sets the Change status to Auth, provided that the Change has a specified owner and the current status is
a synonym of
waiting for approval
. If either of these conditions is not present, you are asked to set these values correctly. - Determines the authorization level, according to the risk value for the Change. If the risk is 1, the authorization level is set to 1; if the risk is 2, the authorization level is set to 2; the risk is 3, the authorization level is set to 3; the risk is 4, the authorization level is set to 4. If the risk value is none of these, the Change Owner receives an assignment to specify the authorization level.
- Depending on the authorization level, does one of the following:
- For authorization levels of 1, 2, or 3, issues the approval records that are specified for that level. The owners of the approval records, and members of owner groups, receive the assignments. If there are no approvers specified for that level, or if the records at that level do not have specified owners or owner groups, the Change Owner can either specify approvers at this level or specify a different level.
- For an authorization level of 4, sends an approval assignment to the Change Owner.
- For all authorization levels, does one of the following:
- Sets the Authorization Decision field to Approved if all approvers approve the Change.
- Sets the Authorization Decision field to Rejected if any approvers reject the Change; also sets the Change status to rejected.