--- title: "Configure task start rules" canonical_url: "https://www.nutrient.io/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/configure-rules-editor/" md_url: "https://www.nutrient.io/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/configure-rules-editor.md" last_updated: "2026-05-23T00:08:18.203Z" description: "Learn how to define and configure start rules for tasks in Nutrient Workflow Automation. Covers the Configure Rules editor, adding and editing rules, grouping conditions, and invalid rules detection." --- # Configure task start rules Every task within a process in Nutrient Workflow Automation requires a starting point. This start rule defines the condition the workflow engine requires to start a task. Start rules function as business rules that determine your process flow based on task completion, form data, or other specific conditions. The **Process Flow** visually represents these relationships. Transition lines between tasks indicate defined start rules.![Transition lines connecting tasks in the Process Flow](@/assets/guides/workflow-automation/files/1377/connecting.gif) All processes in Nutrient Workflow Automation include default **Start** and **End** tasks in the Process Flow. Read a Nutrient Workflow Automation process from top to bottom. A transition entering the top of a task indicates a start rule condition. Follow that line to identify the initiating task. The **Configure Rules** area enables you to define the start rules for a task. These rules determine how and when a task starts during process execution. Start rules typically depend on the status of a previous task, such as completion, or data associated with that task, such as a form question value or an approval option. ## Configure rules editor To view the start rules for any task, right-click the task, hover the pointer over **Configuration**, and click **Configure Rules**.![Right-click menu showing the Configure Rules option](@/assets/guides/workflow-automation/files/1378/config_rules.1022x0-is.png) The Configure rules editor opens and displays the start rules for the selected task.![Configure Rules editor displaying start rules for a task](@/assets/guides/workflow-automation/files/1378/image.png) > When you add a task to the process design canvas, the start rules are empty by default unless you've connected it to another task. The **Configure Rules** editor consists of two areas: - **Rules** — The list of all defined rules that determine how the task starts. - **Add, Edit, or Delete rules** — The area where you manage rules. This area changes based on the **Rule Source Data** you select. ## Adding a start rule Configure the start rule for a task using one of two methods. **Method 1: Transition lines** Drag a transition line from one task to another. Click the perimeter of the source task until a pink line appears, then drag it to the target task.![Dragging a transition line between tasks in the Process Flow](@/assets/guides/workflow-automation/files/1378/connecting.gif) In the example above, we drag the transition line from **Start** to **Form**, then from **Form** to **Approval**. Release the mouse to save the layout. To view the start rule, right-click the task and select **Configure Rules**. Adding a transition line automatically creates a start rule.![Start rule automatically created after adding a transition line](@/assets/guides/workflow-automation/files/1378/image-1.png) > To remove the start rules for a task, select the transition line entering the task and press the Delete key. **Method 2: Configure rules editor** Select a task's **Configure Rules** option. If the task is new and unconnected, the editor displays empty rules. Click **Add Rule**.![Empty Configure Rules editor with the Add Rule button](@/assets/guides/workflow-automation/files/1378/image-2.png) The following options appear for adding a rule:![Add Rule options in the Configure Rules editor](@/assets/guides/workflow-automation/files/1378/image-3.png) To add a new start rule, select an option from the **Source** list. The following example adds a rule for the **Approved** milestone task to start when the approval choice is **Approved**.![Adding a start rule based on the Approval choice](@/assets/guides/workflow-automation/files/1378/image-4.png) The result displays as follows:![Start rule result showing the Approved condition](@/assets/guides/workflow-automation/files/1378/image-5.png) The **Source** list determines if the start rule depends on the **Status** of a task (such as Completed or Failed), the **Data** (such as a form question value or an approval task option), or an attribute associated with the process **Requester** (such as Division or Department). The available **Source** options are as follows: | **Option** | **Description** | | ----------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | **Status** | Displays a list of all available tasks (in the **Tasks** dropdown list) in the process and the corresponding statuses for a start rule. Available status values: **Completed**, **Cancelled**, **Excluded**, **Evaluated**, **Failed**, **Timed Out**. | | **Data** | Displays a list of all available tasks (in the **Tasks** dropdown list) in the process. Selecting a task makes available any data associated with it, such as a form question or an approval task option, for use in the start Rule. | | **Requester, Client, Task Completer, Task Recipient, etc.** | Similar to using Dynamic Recipients for a task recipient. Dynamic Recipients can also determine start rules. Selecting a Dynamic Recipient displays a list of available attributes from that recipient's Nutrient Workflow Automation profile. | | **Request** | Enables you to base a rule on specific attributes associated with a request, such as a start date, last milestone, or request name. | Selecting an option in the **Source** list populates additional options in the **Rule Source Data** area. The **Field** list changes dynamically based on the selected task. For an Approval task, the available choices defined for that task appear, such as Approved, Denied, or Needs more information. After you define the **Rule Source Data** configurations, select how to evaluate the status or data: 1. Select the Operator type, such as Is, Is Not, or Contains. 2. Apply the operator to the Value selected in the corresponding box.![Operator and Value fields in the rule configuration](@/assets/guides/workflow-automation/files/1378/image-6.png) In the example above, the **Is** operator matches a specific **Value**. Select the data from the **Value** list for comparison. Depending on the data type, this field may function as a free-form text field for entering a custom **Value**. In the **Approved Milestone** example, the task executes only when the user selects the **Approved** option defined for that Approval task. After you define the rule, click **Add Rule**. The new rule appears in the rules list.![New start rule added and displayed in the rules list](@/assets/guides/workflow-automation/files/1378/image-9.png) ### Editing a start rule To edit an existing rule, click the **Edit** icon on the rule's row:![Edit icon on a start rule row](@/assets/guides/workflow-automation/files/1378/image-10.png) The **Rule Source Data** area displays the original rule options. Modify the configurations as needed. Click **Update Rule**.![Updating a start rule with new options](@/assets/guides/workflow-automation/files/1378/image-11.png) Don't change business rules if the process has a **Publish** status of **Production** and there are outstanding requests executing the process definition. ## Grouping rules In some scenarios, you must group start rules into a series of conditions. This typically occurs when a task has multiple trigger paths. For example, the **Rework Required** milestone task in the following process starts from either the Manager Approval or the HR Approval task:![Process flow showing the Rework Required Milestone task with multiple trigger paths](@/assets/guides/workflow-automation/files/1378/image-12.png) In the above scenario, add the status and data conditions for the start rules based on both the HR Approval and Manager Approval tasks. Then, group those rules for correct evaluation. Start by adding conditions based on the HR Approval task being **Completed** and the user selecting the **Rework** option:![Start rules with conditions for the HR Approval task](@/assets/guides/workflow-automation/files/1378/image-13.png) To reorder rules, drag and drop them or change the number in the **Order** column. Group the rules after adding them. Without grouping, the system evaluates all four rules as a single condition. 1. Click the text box to the left of the **Status** label on row one. 2. Add an opening parenthesis. 3. Add a closing parenthesis at the end of the condition on row two. Grouping rows one and two tells the Nutrient Workflow Automation engine to evaluate them as one condition. Repeat this grouping for rows three and four: Change the bitwise (and/or) operator where applicable. In this example, change the operator at row three to indicate the task starts if rows one and two evaluate to true, OR if rows three and four evaluate to true. To change the operator: 1. Click the and label to open the dropdown list. 2. Select **OR**. 3. Click **Save** to commit the changes.![Grouped start rules with the Or operator applied](@/assets/guides/workflow-automation/files/1378/image-18.png) ### Compare to option The **Compare To** start rule option enables you to compare similar data from two different forms to evaluate if they match. The following image shows a configured rule:![Example of a Compare To start rule](https://help7.integrify.com/hc/article_attachments/360000751247/mceclip0.png) To configure the above rule, perform the steps below in the editor: 1. Select the **Source** and **Field** for the first data point. 2. Select the **Operator**. 3. Select **Compare To** as the value type. 4. Choose the target **Source** and **Field** for comparison.![Compare To rule being configured in the editor](https://help7.integrify.com/hc/article_attachments/360000740408/mceclip1.png) ### More options The **% Required** field under More options enables you to implement a voting scheme within task rules. To use this feature: 1. Enter a number value in the field. 2. Select a numeric operator, such as **Is Greater Than**.![More Options section in the rule configuration](@/assets/guides/workflow-automation/files/1378/task_rule_-_more_options.882x0-is.png) The following example shows a rule requiring more than 50% of responses:![Example of a majority voting rule using the % Required field](@/assets/guides/workflow-automation/files/1378/task_rule_majority_example-1.399x0-is.png) Enable the **Case Sensitive** slider to compare character values based on capitalization. For example, "use" doesn't equal "Use" when you enable this option. ## Invalid rules detection The system validates task rules each time the **Process Flow** canvas loads. If rules reference deleted transitions, removed tasks, or contain unbalanced grouping parentheses, a warning icon appears on the affected task. > When you delete a transition line or remove a task, any rules referencing those elements become invalid. Always check the **Configure Rules** editor for affected tasks after you make structural changes to your process flow. Common causes of invalid rules include: - **Orphaned transition references** — A rule references a transition line you deleted from the canvas instead of removing it through the **Configure Rules** editor. - **Orphaned task references** — A rule references a task you removed from the process. - **Unbalanced grouping** — Parentheses used for [grouping rules](#grouping-rules) don't match. For example, an opening parenthesis lacks a corresponding closing parenthesis. To fix invalid rules: 1. Right-click the affected task. 2. Select **Configuration** > **Configure Rules**. 3. Update or remove the rules referencing the missing transitions or tasks. --- ## Related pages - [Optimize task display settings for better efficiency](/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/display-settings.md) - [Streamline task management with dynamic naming](/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/dynamic-names.md) - [Task configuration options](/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration.md) - [Mastering the Edit Detail feature for tasks](/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/edit-detail.md) - [Customize task menu email notifications](/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/notification-settings.md) - [Master task management with reminders and timeouts](/guides/workflow-automation/admin-guide/processes/tasks/task-menu/configuration/reminders-and-timeouts.md)