Workflow Tasks Based on Contract Status

Prev Next

COBBLESTONE SOFTWARE

Contract Insight — User Guide

Workflow Tasks Based on Contract Status

03. Admin User Manual › Workflow Management › Workflow Tasks Based on Contract Status

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

A workflow's Conditions tab can key off a contract's Status field the same way any other field is used in an Only when rule — and the reverse is just as common in this environment's own workflows, where a task's answer sets Status_ID directly (a field update on Task Complete or Rejected), letting one workflow's outcome become the trigger for the next. For example, Contract: 1.1 Employee Approval runs when Status is Owner Approval; when its Owner Approval task is completed it sets Status_ID to 57, which starts the next workflow in the chain (1.2 Manager Approval), and when the task is rejected it sets Status_ID to 1.

2. Key Elements

  • Add condition on the Conditions tab can target the Status field to scope a workflow to records in a particular status (for example, "Status is Legal Review").
  • Several workflows in this environment write to Status_ID when their task is answered, which can in turn satisfy another workflow's status-based condition.
  • These field updates are set per task under What happens when "task" is answered → Change a field on the record, with one rule per answer (for example, Task Complete or Rejected).
  • A workflow's Overview tab lists them under And once answered, noting that "a field change here is what can start the next workflow in a chain."
  • This status-in, status-out pattern is how multi-step approval chains (for example, 1.1 Employee Approval → 1.2 Manager Approval → 2. Procurement Review → 3. Legal Review) are built.
  • The Workflow Flow diagram (See it as a diagram) visualizes exactly this: a task's When task complete / When rejected branches, each a field update on Status_ID, leading to the Next step workflow.

3. Finding Status-Based Workflows

  1. From the Contract Insight homepage, click the Administration (sliders) icon at the bottom of the left navigation bar, search for workflow, and click Workflows.
  2. Type Status_ID in the Search name, task, person or field box. The list filters to workflows that reference the status field in a condition or a field update.
  3. Click a workflow's row to expand it and review its Overview tab. Only when shows the status that starts the workflow.

Administration page filtered to Workflows

Workflows list searched for Status_ID

Workflow Overview showing a Status is Legal Review condition

4. Starting a Workflow When a Contract Reaches a Status

  1. Expand the workflow and click the Conditions tab.
  2. Click Add condition (or Edit on an existing Status condition).
  3. In the Edit condition panel, set Field to Status.
  4. Choose the status from Has to be (for example, Legal Review).
  5. Click Save condition. To cover several statuses in one condition, use Several, with AND / OR with Match set to ANY.

Conditions tab with a Status condition

Edit condition panel with Field set to Status

5. Changing the Status When a Task Is Answered

  1. Expand the workflow and click the Tasks tab. The When answered column shows how many field changes each task makes.
  2. Click Edit on the task and scroll to How it finishes. Under Answers to offer, tick the answers the assignee can give (for example, Task Complete and Rejected), then click Save task.
  3. Back on the Tasks tab, click the rules (two-arrow) icon next to the task's Edit button to open What happens when "task" is answered.
  4. Under Change a field on the record, click Add a field change, choose the answer (for example, Task Complete), set the field to Status_ID, and pick the new status. Add a separate rule for each answer, such as a Rejected rule that sends the contract back to an earlier status.

Tasks tab showing 3 field changes when answered

Edit task panel How it finishes section with Answers to offer

Field changes that set Status_ID when a task is answered

6. Chaining Workflows by Status

Because the status set by one workflow's task can match another workflow's Status condition, a series of workflows forms an approval chain. The expanded Overview shows both halves on one screen: Only when (the status that starts this step) and And once answered (the status that starts the next step).

  1. Set the first workflow's condition to the starting status (for example, Owner Approval).
  2. On its task, add a Task Complete field change that sets Status_ID to the next step's status, and a Rejected field change for the fallback status.
  3. Give the next workflow a Status condition matching the value the previous step sets, and repeat for each step in the chain.

Workflow Overview showing Only when and And once answered status changes

7. Viewing the Chain as a Diagram

  1. On the workflow's Overview tab, click See it as a diagram.
  2. The Workflow Flow page shows the workflow, its Criteria, the Task, the When task complete and When rejected field updates, and the Next step workflow they lead to.
  3. Use the drop-down to switch workflows, Fit / + / – to zoom, and PNG or SVG to download the diagram. Click View Workflow Configuration to return.

Workflow Flow diagram of a status-based workflow chain

8. Quick Reference Summary

TaskHow to Complete It
Find status-based workflowsAdministration → Workflows → search Status_ID.
Start a workflow at a statusConditions → Add condition → Field: Status → Has to be: status → Save condition.
Choose the answers a task offersTasks → Edit → How it finishes → Answers to offer.
Change the status when a task is answeredTasks → rules icon → Add a field change → Status_ID.
See what starts and what follows a stepOverview tab → Only when / And once answered.
View the chain visuallyOverview → See it as a diagram.