Admins can configure the signature flow for an object with relevant signatures from
multiple roles using signature templates. For example, a signature flow that requires a
signature from the store manager followed by the signature from the sales rep. Customize the
signature flow for processes such as orders, contracts, and daily reports.
Required Editions
Available in Lightning Experience in Professional, Unlimited, and
Enterprise Editions that have Consumer Goods Cloud enabled
The Signature Handling page contains these sections:
Header Attributes: Attributes that identify the user signature belonging to a process
such as an order or a report. These attributes are shown while capturing or reviewing the
signature. You can define the header attributes by using the Attribute Set in a signature
template.
User Signature: The user's signature is shown along with the header attributes.
You can configure multiple signature steps, one for each signature. For each signature step,
the system validates these items:
If
Value
Then
Signature Required
Yes
A signature for the corresponding signature step is mandatory.
Authentication
None
Name (optional)
Name (required)
None: The system doesn’t ask for the name of the contact.
Name (optional): The user can enter the name of the contact, but there’s no
forced validation.
Name (required): The user must enter the contact's name.
Signatures in Print Layout Use signature templates to configure the signature flow for an object and to include signatures of multiple roles in the Print Layout of the relevant process.
Did this article solve your issue?
Let us know so we can improve!
Loading
Salesforce Help | Article
Cookie Consent Manager
General Information
Required Cookies
Functional Cookies
Advertising Cookies
General Information
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.