Approving ChangeMan ZMF Change Packages

Approve/Reject Package allows predefined approvers to review change package information, components, and test results and approve or reject the change package for installation to a promotion site.

Approval may be required in your ChangeMan ZMF implementation. If so, you'll need to set up an approve deployment task.

Tip: Notification can be set up in SBM so that approvals can be done in Release Control. This way ChangeMan ZMF approvers do not need to logon to ChangeMan ZMF directly to give their approval.

To configure an approve change package action in a deployment task:

In the UI, point to each field for additional information.

Some of the fields are described in the following table.

Field Description Example Values
Package Name

Click the link icon to select a change package. From here, you can:

<select a change package>
Environment Select each environment in which you want to execute the task. These are the environments configured in the deployment path. For example, Dev, Test, and Prod. <select Test>
Approver For each selected environment, select from the approvers. These are the approvers set up in ChangeMan ZMF. <select approver>
Schedule Options

For each selected environment, select the schedule option and fill out the additional fields that open based on your selection. Options include the following:

  • None
  • Specific Time
  • Opportunity Window
  • Time Window
  • Delay
  • Hold Until Released
Important: Dynamic approvers are added only when change packages are frozen, so approval tasks that rely on dynamic approvals will fail if the package is not yet frozen. Dynamic approvers are added by ChangeMan ZMF only when the package is frozen. ChangeMan ZMF checks to see if there are component types in the package that are associated with an approver. If there is a match and the approver is not already part of the package approver list, it will add the approver.
Note: After you create the deployment task, if you have not linked a change package, the task appears in the list in red, and you must then associate the related change package with the deployment task.

Related Topics

Related Topics

Linking Change Packages to Deployment Tasks

Creating Change Packages