A Technical Consultant at the Department of Disaster Assistance is designing a solution for the eSignature related use cases. As part of the…

The Salesforce Public Sector Solutions (PSS) digital signature functionality, which integrates with providers like DocuSign, offers several out-of-the-box capabilities. It allows users to generate documents and send them for signature (A). The framework includes components to track the status of the signature request (e.g., Sent, Completed, Voided) and update the corresponding Salesforce records automatically (B). Furthermore, PSS provides a pre-built, invocable flow named DigitalSignatureVoidEnvelope, which allows for the automatic invalidation (voiding) of an in-flight signature request when triggered by a business process, such as a newer contract superseding an older one (E).

C. An "Approval process" is a specific Salesforce automation tool. The PSS integration provides the mechanism to invalidate a document but does not include a pre-configured approval process for this specific scenario.

D. The standard integration is designed to send finalized documents for signature. The ability for a reviewer to edit the content of the document during the signing ceremony is not a readily available feature.

1. Salesforce Help, Public Sector Solutions Documentation, Send a Signature Request: This document outlines the primary function of the integration. It states, "Send documents for signature to internal and external users with a signature provider such as DocuSign or Adobe Sign." This directly supports option A.

2. Salesforce Help, Public Sector Solutions Documentation, Track a Signature Request: This section details the status tracking capability. It explains, "The Digital Signature record shows the status of the signature request. The status is automatically updated based on the recipient's actions." This confirms the functionality described in option B.

3. Salesforce Help, Public Sector Solutions Documentation, Void a Signature Request: This page describes the invalidation process. It notes the existence of the DigitalSignatureVoidEnvelope flow, stating it can be used in a "custom flow or process to automatically void a signature request." This pre-built flow makes the automatic invalidation described in option E a readily available functionality.