The Marketplace Team is transitioning from DocuSign to Adobe Sign as the eSignature solution. Adobe Sign was successfully implemented in the test environment, and the primary differences are summarized below.

Overall, users will find Adobe Sign very similar to DocuSign and should be able to begin using it with minimal adjustment once it goes live.

1. Marketplace functionality remains unchanged.
2. During the approval workflow, eSignature activation occurs in the background.
3. Once Adobe Sign is active, contract managers will launch eSignature as they do today.

1. Signatory selection
   Signatories appear in a list format instead of a drop-down menu.
2. Signature fields and required fields
   In DocuSign, contract managers manually drag fields onto the PDF. In Adobe Sign, signature, date, and other required fields are pre-placed on the signature page.
   • When Signatory 1 is selected, clicking the light blue signature box automatically assigns it to them. Similarly, clicking a date box assigns it to the selected signatory.
   • Contract managers can still drag and drop fields from the left menu if needed, just as in DocuSign.
3. Additional fields in the left menu
   The left menu includes more fields, some hidden under an expanded view. For example, the “Title” field only appears when the list is expanded.

1. This change will be rolling out over the weekend of June 22, 2025.
2. Switching eSignature solutions will not affect contracts already out for signature. The system will continue using the original solution for those in-flight contracts.

With its familiar functionality, users should experience a seamless shift to Adobe Sign. The Procurement Team is confident that this change will maintain the ease of use everyone relies on. Thank you for your flexibility during this transition.

When a draft contract is submitted in JAGGAER, it follows the currently active contract workflow. In user integration testing (UIT), this means draft contracts use the workflow with Adobe Sign steps instead of DocuSign. The workflow configuration itself was not changed; only the step names were updated. Whether using DocuSign or Adobe Sign, JAGGAER performs the same actions at those steps.

When a contract returns to JAGGAER from the e-signature provider, it does not reauthenticate. This means switching providers will not impact contracts already out for signature; they will continue with the original provider. To ensure those signatures are completed, keep the old provider’s account active.

If needed, you can return a contract in the “Out for Signature” step to draft and resubmit it through the workflow to trigger the new e-signature provider.