---
title: "Workflow Tasks Based on Contract Status"
slug: "workflow-tasks-based-on-contract-status-1"
updated: 2026-08-27T19:51:27Z
published: 2026-09-23T12:58:39Z
canonical: "wiki.cobblestonesoftware.com/workflow-tasks-based-on-contract-status-1"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://wiki.cobblestonesoftware.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workflow Tasks Based on Contract Status

**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 (as seen in Field Update on Complete/Reject), letting one workflow's outcome become the trigger for the next.

# 2. Key Elements

- Add condition on the **Conditions** tab can target the **Status** field to scope a workflow to records in a particular **status**
- 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
- This **status**-in, **status**-out pattern is how multi-step approval chains (Prepare for Review → Legal Review → Counterparty Review → Send for Signature) are built
- The **Workflow Flow** diagram visualizes exactly this: a task's WHEN TASK COMPLETE / WHEN REJECTED branches, each a field update on **Status_ID**

# 3. Quick Reference Summary

[TODO: content needed]