Auto-Generate Template Document

Prev Next

COBBLESTONE SOFTWARE

Contract Insight — User Guide

Auto-Generate Template Document

03. Admin User Manual › Workflow Management › Auto-Generate Template Document

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

Workflow tasks in this environment can trigger document generation when answered, matching the legacy behavior described here. The workflow Contract: 5. Prepare for Signature (Legal Rep) states directly on its Overview tab, under AND ONCE ANSWERED: “Send Executable Document to Vendor generates Standard Signature Process as soon as it’s created.” On the workflow’s Tasks tab, the same task’s WHEN ANSWERED column summarizes this as “1 field change · 1 document,” confirming that answering the task both updates a field (Status_ID) and triggers the generation. What actually gets generated here is an Approval & Signing Process (Administration → Approval & Signing Processes) — a reusable signing route, followed by its own set of document templates — rather than a single merge template.

 

2. Key Elements

  • Configured per task inside a workflow’s Tasks tab in Workflow Manager (Administration → Workflows)
  • A task’s Overview tab description states plainly when this fires, e.g. “[Task] generates [Process/Template Name] as soon as it’s created”
  • The Tasks tab’s WHEN ANSWERED column summarizes a task’s field changes and document-generation count together (e.g. “1 field change · 1 document”)
  • Example observed live: workflow Contract: 5. Prepare for Signature (Legal Rep), task Send Executable Document to Vendor, generates the Standard Signature Process — a Contracts signing process (Administration → Approval & Signing Processes) with 4 steps and followed by 4 templates

 

3. Confirming What a Task Generates

A workflow's Tasks tab (Administration → Workflows → a workflow → Tasks) lists every task the workflow creates, with a WHEN ANSWERED column summarizing each task's field changes and document generation together, e.g. 1 field change · 1 document. The workflow's own Overview tab spells out the same behavior in plain language under AND ONCE ANSWERED, naming exactly what gets generated and confirming it fires as soon as the task is answered.

 

4. Reviewing the Generated Process

When a task generates something other than a single merge template, Administration → Approval & Signing Processes is where to look it up. Each process shows what area it's For (e.g. Contracts), its Kind (Approval or Signing), how many ordered Steps it has, and how many document Templates follow it. Opening a process shows who signs, and in what order — each step's signers, source, and reason — along with the full list of templates that share that process.

 

5. Quick Reference Summary

AreaWhere
Configure a task that generates a document on answerAdministration → Workflows → a workflow → Tasks → Edit a task
See whether a task generates something, and how muchWorkflows → a workflow → Tasks tab → WHEN ANSWERED column
Read the plain-language description of what a task generatesWorkflows → a workflow → Overview tab → AND ONCE ANSWERED
Look up a generated signing/approval processAdministration → Approval & Signing Processes
See who signs and in what order for a processApproval & Signing Processes → Manage on a process
See which templates follow a given processApproval & Signing Processes → Manage → Templates count / banner
Example observed liveContract: 5. Prepare for Signature (Legal Rep) → Send Executable Document to Vendor → generates Standard Signature Process
Standard Signature Process (this environment)Contracts · Signing · 4 steps · followed by 4 templates