Help Center User GuideGetting StartedFAQRelease Notes
 
X
User Guide
Getting Started
FAQ
Release Notes
Contents  

Approving and Updating Changes Submitted

Procedure

To approve the change requests and update the policy changes:

  1. Select Configure > Change Management > Change Requests.

    The Changes Submitted page appears.

  2. Select the change request and click Approve.
  3. The submitted change request is displayed in the approvers workspace.
  4. The approver reviews the change request and checks for any dependencies. Dependencies can be viewed by clicking the View link.
  5. If there are no dependencies, the approver enters the comments in the Approve Request window and then clicks Yes. A pop-up message shows the status as approval successful.
  6. The change request workspace of the firewall administrator shows all the change requests that were approved or rejected.
  7. The administrator then selects an approved change request and schedules it to publish and update.
  8. The administrator selects Update to update immediately or schedule to update later. If the selected change request has dependencies, then the user is notified that update of dependency change requests will also be scheduled (if they have not been already) or advanced (if they have been scheduled for a later time) to the same time as that of the selected change request. The list of dependency change requests that are also updated will be displayed. A new snapshot of the policy is created. This snapshot is used as the source for publish and update. This new snapshot is essentially the previously updated snapshot of the policy along with the changes from the selected change request. This snapshot is visible in the Manage Snapshots list.

    Updating a change request is same as publishing and updating together. If either of publish or update jobs fail, the change request is moved to the Update Failed state. You can reupdate the failed change requests.

  9. The administrator views and verifies the job status.

Note:

  • You must approve all the parent change requests before approving a child change request, if there is a dependency.

  • You must deny all child change requests before denying a parent change request, if there is a dependency.

Related Documentation

Ask questions in TechWiki

Check documentation in TechLibrary

Rating by you:      
X

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:
Email:

Need product assistance? Contact Juniper Support

Submit