Conditional evaluation tokensare designed to control whether document content is rendered based on runtime data and specified conditions. This directly fits the requirement to show or hide contractual clauses according to Account-specific field values.
For example, a clause could be included only when an Account belongs to a particular jurisdiction, customer segment, risk category, or commercial classification. During document generation, the token evaluates the relevant data and determines whether the associated content should appear.
Repeating content tokens, option A, address a different document-generation pattern. They are appropriate when content must repeat for collections or multiple related records, such as generating rows for several quote lines. They do not primarily control conditional visibility. Variable tokens, option C, insert dynamic field values into document text—for example, an Account Name or Contract Date—but do not inherently determine whether an entire clause should be shown.
Therefore, conditional evaluation provides the runtime branching required by the contract-document design.
Study Guide Reference:Contracts and Orders — Contract Document Templates; conditional evaluation tokens; dynamic clause inclusion.
===============
