Skip to main content

System Settings

The CPQ System Settings record controls org-wide Cotiza CPQ behavior. Create one record after installation and configure it before rolling out to users.

See CPQ System Settings for the complete field reference.

Core settings​

FieldPurpose
Default PlaybookPre-select a Playbook when creating Quotes
Display Playbook as ModalShow Playbook configuration in a modal vs. full page
Approval SubmitterDefault submitter behavior for approval workflows
Line Item Pricing Fields RefreshControls pricing recalculation timing

Quote table configuration​

FieldPurpose
Quote Table Display ColumnsSemicolon-delimited Quote fields shown in the Quotes table
Quote Table ActionsAvailable actions: View, Edit, Sync, Proposal, Clone, Delete
Quote Table Sort By DefaultDefault sort column and direction
Quote Table Page Size DefaultPagination size (blank = no pagination)

Proposal settings​

FieldPurpose
Proposal Table ActionsActions on the Proposals table
Proposal Table Page Size DefaultProposals table pagination
Proposal Quote Piped FieldsAdditional Quote fields available in piped text
Proposal Allowed Override FieldsQuote fields Proposal Power Users may override

Approval settings​

FieldPurpose
Approval Allowed Override FieldsQuote fields submitters may override when submitting approvals

Contract settings​

FieldPurpose
Contract Table Display ColumnsContract table columns on Account/Contracts UI
Contract Table ActionsView, Amend, Replace, Renew, Void
Contract Table Sort By DefaultDefault contract sort
Contract Table Page Size DefaultContract table pagination
Amendments Maintain ContractAmend in place vs. new Contract per amendment
Force Quote From ContractRequire contract context for adjustment Quotes
Show Most Active Contract SnapshotDisplay snapshot on Account contract views

Semicolon-delimited field lists​

Many System Settings and Playbook fields use semicolon-delimited API name lists. Conventions:

  • Use valid field API names
  • Prefix with #Label to create section headers in display views
  • Use invalid tokens as blank spacers
  • Append ;Down or ;Up to sort field names for default sort direction