Apply bypass tokens to keep specific tokens unchanged in generated documents when no value is provided. For example, an Adobe Sign signature token {{Sig_es_:signer1:signature}} now remains in the generated document when no value is provided instead of being removed and breaking the signing workflow. Define a bypass list of tokens to skip replacement during document generation. Tokens in the bypass list remain unchanged unless a value is provided, while other tokens continue to follow the default behavior and are replaced with empty values.
Where: This change applies to Lightning Experience in Enterprise, Performance, Unlimited, and Developer editions of Agentforce Revenue Management, formerly Revenue Cloud, with the Revenue Cloud Advanced or Salesforce Contracts license.
Why: Previously, document generation replaced tokens without values with empty strings, which removed placeholders required for workflows such as Adobe Sign signature processing. This behavior caused issues when signature tokens needed to remain in the document for later completion. Bypass tokens preserve these placeholders so downstream processes continue without errors and document integrity remains intact.
How: Add a bypass_tokens attribute to the token data payload and list the tokens to preserve as a comma-separated string, for example, "Sig_es_:signer1:signature,Cmpy_es_:signer2:company,!price". Make sure that tokens intended to remain unchanged don’t have values in the token data. Configure bypass_tokens by using token data, Omni Data Mapper, or Context Service mappings based on the document generation setup.