Adobe to eSign migration for Salesforce

About the Client

The client is a technology-enabled information services business powering the global legal industry with intelligence, analytics, and performance data. By applying the latest technology to the fast-moving legal world, they enable users to find their competitive edge and decide with confidence, armed with the insight they need.

migration Business Problem

Business Problem

Up until now, the Client was using Adobe to send Quote documents for signature to their customers. This allowed them to save time and provided a faster turnaround in terms of both business efficiency and compliance.

However, effective June 30, 2025, people in mainland China are unable to use Acrobat Sign. This was a significant hindrance as it would provide friction in business processes. Hence, to keep China operations ongoing, the client is looking to utilise eSignGlobal with its current quotes to Chinese customers

Astrea Approach

The business had workflows and automations already in place, which would use Adobe Sign for sending out Quote documents for customer signatures. The existing workflows needed to be modified to ensure that separate ones could be created for the China region and that did not hinder the existing system. A set of new quote templates needed to be designed as well, along with an Aura component for the eSign workflow, allowing the Sales rep to review the document before sending, and a webhook was also written with a RestAPI to update the “eSignGlobal Agreement” record status, i.e., start, signer signed, all signer signed.

Here are some of the outlined steps:

  • A new custom button was developed and put on the Quote record page; this would, on click, call the QuoteDocumentController class. This class is a managed class from the CPQ package. This would allow the user to be redirected to the Quote Document automatically, with the required fields being populated.
  • An automation will run on the Quote template creation (if this is for China) and create a new record of ‘eSignGlobal Agreement’ object and a file attached with it.
  • After reviewing the document, the user will click on the send button, and it will redirect back to the ‘eSignGlobal Agreement’ record page, and the status set to ‘Sent’.
  • A rest API class was written that is used by the eSignGlobal webhook to update the ‘eSignGlobal Agreement’ record status.
  • Existing templates were modified for the eSign quotations.

Outcome

The outcome was that a new e-signing application was successfully implemented in response to regulatory changes in a country. It was successfully integrated with Salesforce without affecting existing business processes.

Technologies Leveraged

Custom Apex code, LWC components, Custom Objects and Fields, Custom Buttons, restAPI webhooks, eSign software

Need support with a similar project?

*
*
*
*
-
* -


Contact Details