What is Write Back?
Conga Sign Write Back functionality uses Conga Sign tags to configure and map standard and custom Salesforce fields in documents. The information added by signers within documents is sent directly to Salesforce and updates the appropriate records. The Sign Write Back functionality eliminates redundant data entry and possible errors associated with those manual processes.
How it works
The Write Back process consists signers selecting tags, signers selecting Salesforce objects related to those tags, signers adding data to those tags and then the data being directly updated to the appropriate Salesforce record.
A Write Back Configuration tab is located within the Conga Sign setup. On the Configuration tab, signers can search for both standard and custom objects in Salesforce, choose fields associated with those objects that they would like to make available for write back, and define basic properties for how those fields should work when used as tags in a Conga Sign document.
When fields are configured to use with Conga Sign Write Back, signers have two options to get the appropriate tags into documents.
- In the Tagging screen
- A new section of tags is made available under the Write Back heading. The list of write back tags made available in the Tagging screen is based on the fields that were configured for the parent object from which the Conga Sign transaction originated.
- Drag and drop a write back tag onto the document for the signer that is responsible for providing the requested information.
- Add write back tags to a document is through the Conga Sign tagging syntax
- Like standard Conga Sign tags can be added through tagging syntax, any field configured to function with write back can be added to your document templates.
- In order to simplify the process, the write back field properties screen for each write back field has an example of the syntax. RECOMMENDED: Copy and paste the example syntax into your templates. Update the signer index and you’re ready to go.
Only one signer can be assigned each write back tag to avoid any potential data conflicts during the write back process. Ensure only one signer is used per write back tag while updating your templates because any conflicts result in an error and a new transaction must be created.
Conga Sign Write Back enforces a limit of one signer per write back tag in order to eliminate any potential data conflicts if multiple signers were asked to provide the same information. This same limit is not in place for write back tags specific to the signer’s contact, lead, or role record in Salesforce as those are specific to an individual signer.
Write Back Tagging Syntax
The best way to get your newly configured write back tags into your documents is to simply copy and past the tagging syntax from the write back field properties page. Update the signing index to reflect the appropriate signer.