Skip to main content

Playbook Design

Playbooks are the central configuration object in Cotiza CPQ. This guide covers how to design Playbook Questions and Question Groups.

  1. Create and activate the Playbook with a linked Price Book
  2. Create Question Groups
  3. Create Questions within each group
  4. Create Scenarios that reference questions
  5. Create Rules and Approvals
  6. Create View Sections for proposals and emails

See How Many Playbooks? before creating multiple playbooks.

Question groups​

Question Groups are visual containers. Use them to:

  • Organize related questions into collapsible sections
  • Control display order via Display Order
  • Apply group-level rule actions (visibility, read-only state)

Answer types​

Each Playbook Question has an Answer Type that determines the input control shown to users:

Answer TypeUse for
BooleanYes/no toggles
CurrencyMonetary values
DateDate pickers
Decimal / IntegerNumeric input with optional min/max
Picklist / Multi-Select PicklistConstrained choices (semicolon-delimited values)
Record LookupSearch and select Salesforce records via SOQL query
Text / Text AreaFree-form text

Key question fields​

FieldPurpose
Variable NameUnique token used in piped text, rules, and view sections
Display LabelLabel shown to users in CPQ
Proposal LabelAlternate label used in proposal answer tables
Is RequiredMust have a value before save
Is Required With TouchMust be touched (interacted with) even if a default exists
Is HiddenHidden from UI but can still hold rule-stamped values
Is Read OnlyDisplay-only for users
Default Value fieldsPre-populate answers (by answer type)
Default Field ValuePull default from a Quote, Opportunity, or Contract field
Quote Save FieldStamp answer value to a Quote field on save
Help TextInline guidance for users

Record lookup questions​

Record Lookup questions use a Query String (SOQL) to search records. Configure:

  • Record Display Fields — columns shown in search results
  • Record Page Size Default — pagination
  • Maximum Record Selections — single or multi-select
  • Record Selection Behavior — how selections are stored

Bind variables such as Opportunity and Account IDs can be referenced in query strings.

Contract and amendment behavior​

FieldPurpose
Amendments Take Latest AnswerDuring amendments, use the latest Contract Playbook Answer
Do Not Upgrade AnswerPrevent answer upgrades during contract adjustments
Do Not Create AnswerSkip creating a Playbook Answer record

Visibility and validation​

Use Playbook Rules with Adjust question field actions to dynamically show, hide, or lock questions based on Scenario evaluation.

Combine Minimum Value and Maximum Value on numeric questions for validation constraints.

Description