Completing the authorization process

If you use the built-in PMCHGMAIN1 workflow, the workflow conducts a series of steps that ensure completion of the authorization phase. You can modify the workflow to perform authorization in a manner more suited to your needs. The built-in PMCHGMAIN1 workflow uses the PMCHGAUTH1 subprocess by default, but you can substitute the PMCHGAP1 subprocess in its place.

About this task

You can view a graphical representation of the authorization process by opening the Workflow Designer application and examining the steps in either of these authorization subprocess workflows.

  • 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.
  • The PMCHGAP1 authorization process
    The built-in PMCHGAP1 subprocess workflow also conducts a series of steps to ensure that your Change is properly authorized. If this workflow is used, authorization assignments are sent across all of the authorization levels, beginning with the Change Owner and moving up through levels 3, 2, and 1.
  • Manually recording the authorization decision
    You can use the Authorization Decision field, rather than an automated workflow step, to record the completion of authorization phase. In this field, you mark the Change as approved or rejected.
Parent topic: Authorizing a Change

Feedback