Implement Settings

Lists changes which should be implemented. An enforcement job will continuously check tickets in this task and attempt to implement those in configured Enforcement Window, or users may manually implement changes at any time.

Use to override values provided by the workflow pack configuration. Changes apply only to this task configuration.

1. Click Implement.

2. Select the Tasks tab.

   1. Select Editable to allow users to change implementation status and manually automate changes.

   2. Select Validate to enable that all change plans for all requirements must be marked as Staged or Completed before the ticket can advance to the next task.

   3. Select Enable Automation Commit for devices that support a two-stage commit to allow SIP to send a message to commit the change when complete. When enabled, any ticket automatically commit the changes to the device when you click Run Selected. This automation functionality is disabled by default.

   4. Select Use Enforcement Windows for Policy Planner to consider enforcement windows when performing automation changes. ill only push changes that are associated to devices that have active enforcement windows. Using an enforcement window also allows you to enable automatically advancing a ticket if it detects that all changes have been implemented. This automation functionality is disabled by default. Enabling displays the Complete Task if Fully Implemented option.

   5. Select Complete Task if Fully Implemented to enable Policy Planner to automatically advance the ticket if the system detects that all changes have been implemented. This automation functionality is disabled by default, and only is optional when Use Enforcement Window is enabled.
      • You will need to set enforcement window settings on the device.
3. Select the Change Plan tab.
   1. Select the Editable check box to allow requirements and changes to be edited for this task.
   2. Select the Validate Requirements check box to ensure that a ticket has at least one requirement defined.
   3. Select the Validate Change check box to ensure that a ticket has at least one change defined.
   4. Select the Create Changes check box to allow users to add a change. Types of changes allowed are dependent on the requirement type.
   5. Select the Import Requirements from CSV check box to allow this functionality.
   6. Select the Enable Rule Recommendation check box to utilize Policy Planner's tool (Rule Recommendation) to determine which devices and policy rules may need to be modified to implement the requested change.
   7. Select the Auto Run Suggested Devices check box.
   8. Select a Device Group from the Suggested Device Group Default list that will be used for rule recommendation to run against for change plan recommendations.
   9. Select a Requirement Scope to Consider to determine if the requirement should completely match or partially match a route on an interface of the device group.
      • Partial address space will partially match a route on an interface of the device group.
      • Complete address space will completely match a route on an interface of the device group.

10. Select a Modify Recommendation Behavior to use when an existing rule partially matches the requested access:

    • Create will recommend creating a new rule with similar access
    • Modify (set by default) will recommend modifying the existing rule found

11. Select an Auto Select Method for when rule recommendations returns multiple potential objects for a given address space to allow the system to auto select the best match of an object:

    • None (set by default) will not auto select a best match
    • Object Usage: matched based on highest usage
    • Security Rule References: matched based on most referenced rules on the device
    • Match Pattern: requires regex match pattern input

12. Select the Force Auto Select of Objects check box to force the system to choose an object if the auto select method cannot narrow results.

13. Select a Management Station Recommendation Method to use for when recommendations are enabled for management stations and multiple recommendation sets may be possible.

    • Least Access affects as few devices as possible

    • Fewest Changes affects as few policies as possible

    • Balanced affects a median amount of devices

4. Select the Comments tab.

   • Select the Editable check box to allow users to create and edit comments on a ticket.

5. Select the Task History tab.

   • No configurations available at this time,

6. Select the Ticket History tab.

   • No configurations available at this time,

7. Select the Attachments tab.

   • Select the Editable check box to allow users to add and remove attachments on a ticket.

8. Click Add Tab to also include Analysis and Verify tabs to a ticket's implement layout.

   1. Analysis

      • Select the Editable check box to allow requirements to be approved or rejected for this task.
      • Select the Validate check box to ensure that all requirements have a decision of approve.

   2. Verify

      • Select the Editable check box to allow users to associate change logs to changes for verification.

      • Select the Enable Auto Verification check box to allow devices that support automation Queues changes for verification. An auto verify job will continuously check tickets in this task and attempt to verify, or users may manually verify changes at any time.

      • Select the Complete Task on Auto Verification Success check box to enable a Change Plan to be marked as "completed" if auto verification successfully finishes.

      • In the Change Control Field Override box, choose the name of the workflow field variable to use to validate the device rule's Change Control Number field of Rule Documentation.
9. Click Apply.
10. Continue to the next setting or click Save.