---
title: "Field Update on Complete/Reject"
slug: "field-update-on-competereject-1"
updated: 2026-08-27T19:53:11Z
published: 2026-09-23T12:58:39Z
canonical: "wiki.cobblestonesoftware.com/field-update-on-competereject-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.

# Field Update on Complete/Reject

**COBBLESTONE SOFTWARE**

Contract Insight — User Guide

**Field Update on Complete/Reject**

*03. Admin User Manual › Workflow Management › Field Update on Complete/Reject*

**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 **Overview** tab spells out its "**AND ONCE ANSWERED**" logic in plain language: for the example "01. All Contract Types - Prepare for Review" workflow, setting its task to **Task Complete** sets **Status_ID** to 165, setting it to **Rejected** sets **Status_ID** to 1, and setting it to a custom status like "CK Contract Status" sets **Vendor_ID** to 531 — each possible task answer can drive its own distinct field update.

# 2. Key Elements

- **AND ONCE ANSWERED**, on a workflow's **Overview** tab, lists every field update tied to a specific task answer
- Different answers can update different fields — **Status_ID** on complete/reject in the example, **Vendor_ID** on a custom status
- A field update here is what can trigger the next workflow in a chain, since other workflows can condition on that same field
- The **Workflow Flow** diagram color-codes these as green (field update, complete) and red (field update, reject) boxes branching off the task node

# 3. Quick Reference Summary

[TODO: content needed]