Workflow Tasks Based on Department

Prev Next

COBBLESTONE SOFTWARE

Contract Insight — User Guide

Workflow Tasks Based on Department

03. Admin User Manual › Workflow Management › Workflow Tasks Based on Department

Note: Each procedure in this guide begins at the Contract Insight homepage, so any section can be followed on its own. Custom fields are configurable, so the exact field list on a contract category record may vary between environments.

1. Overview

Department/Division is available as a workflow condition the same way Status or Contract Type is — a workflow can be scoped to fire only for records tied to a particular department, useful for routing review or approval tasks to the right team automatically as records are created or edited within that department. (An existing workflow’s read-only Conditions summary displays this same field as “Department/Business Unit”; the field-selection dropdown and a contract’s own Details panel both label it “Department/Division.”)

 

2. Key Elements

  • Add condition on the Conditions tab can target Department/Division to scope a workflow to one department’s records
  • This is the same field shown on a contract’s own Details panel (Department/Division); an existing workflow’s Conditions list displays it under the label Department/Business Unit
  • Assign to on a task offers A specific person (the record owner, its manager, or a named employee) or Share out in rotation; a separate Role or group option can route the task to a standing team instead
  • Role or group choices in this environment include Administrators, Blazor Test Group, Contract Intake Form Review Group, and PO Review Group — a practical way to route a department-scoped task to a team rather than one person

 

3. Scoping a Workflow to a Department

On a workflow’s Conditions tab, use Add condition and choose Department/Division as the field, then pick the department the workflow should apply to (optionally alongside other conditions, such as Status). The Conditions list below the form shows each active rule, with Edit and Delete actions for adjusting the scope later.

4. Assigning the Resulting Task

On the Tasks tab, a task’s Edit panel includes a "Who it’s for" section with an Assign to control. Choosing A specific person lets you pick the record owner (Employee), the record owner’s manager, or a named employee; Share out in rotation distributes the task across a group instead. A separate Role or group field can route the task to a standing team — such as Administrators, Blazor Test Group, Contract Intake Form Review Group, or PO Review Group — which is useful when a department’s approvals should go to a team rather than one person.

5. Quick Reference Summary

ActionWhere
Add condition on Department/DivisionWorkflow > Conditions tab > Add condition
View/Edit/Delete an existing conditionWorkflow > Conditions tab > condition row actions
Assign task to a specific person or managerWorkflow > Tasks tab > Edit task > Assign to: A specific person
Share a task out in rotationWorkflow > Tasks tab > Edit task > Assign to: Share out in rotation
Route a task to a standing teamWorkflow > Tasks tab > Edit task > Role or group