Configuring Dynamic Assignment

Workflow Owner This topic is intended for SecureChange workflow owners, who are responsible for creating and maintaining workflows.

Overview

When creating a task with Assignment mode, for a given step, you can configure multiple, parallel tasks for different handlers or handling groups. The step's fields are duplicated for each task. For example, for an Approval step, you can have parallel Approve/Decline tasks, to require approval from multiple corporate departments.

You can also configure conditional tasks according to Access Request content, labels and/or ticket fields, including SLA status, Verification Status, and Risk Status. For example, you can send separate tasks to different security groups depending on the affected networks or target firewalls. When multiple conditions are met, multiple (parallel) tasks are created. For example, if the access request contains multiple traffic pattern values so that more than one network or target firewall is affected, you want the security groups for each network to approve the change that effects their network. Each task contains only the access request traffic pattern values that meet the condition. All access request traffic pattern values that result from the step's tasks are passed on to the next step.

Workflows and Configuration Options

The workflow you create determines which configuration options are available for dynamic assignment: conditions list and/or custom script.

For the following workflows, when multiple tasks are opened on the same step by Dynamic Assignment, no changes can be made to the rules or objects within the rules, and all tools (such as Designer and provisioning) are disabled for the handlers, even if the same handler is configured for all the tasks in the step: 

  • Rule Decommission
  • Rule Modification
  • Rule Recertification
  • Decommission Network Object

In the Access Request workflow, when more than one task is created, the Designer results will not be copied to the current or subsequent steps. If only one task is created, there are no restrictions and the single task proceeds according to the configured permissions.

Dynamic assignment by script is supported for all workflow types.