Asite + Adobe Sign Integration

This article helps you understand Asite integration with Adobe Sign.

Updated this week

Send your forms for signature directly from Asite.

Users of the Asite platform can develop forms, distribute them, have them executed

with Adobe Sign, and then save them back to Asite for safe storage and sharing.

Make collaboration more easier and less time consuming. This seamless collaboration works with any form on the Asite platform, making it easier for businesses to automate their paper-based processes.

About Adobe Sign

Adobe Sign (also known as EchoSign, eSign & Acrobat Sign) is a cloud-based e-signature service that allows the user to send, sign, track, and manage signature processes using a browser or mobile device. It is a part of the Adobe suite of services.

With Adobe Sign, you can eSign documents and collect signatures faster.

Features

  • Send any type of form for signature

  • The signed copy of the document will be returned to Asite and record will be attached with the Adobe signed version

  • Automate processes for tracking status of the form

  • Full audit tracking

Prerequisites

An active Asite CDE subscription + Asite API permission

An active Adobe E-signature plan + Adobe E-signature API integration

Asite and Adobe Sign Integration - Forms

Currently, Asite integrates with Adobe Sign on Forms via our robust Visual Workflow tool. Below are the steps involved for users to integrate their Asite account with Adobe Acrobat Sign for Forms.

1. Create three system tasks on forms - one for Integration Authorization (OAuth), second for Attach Document, third for Status Change - with required configuration details on the relevant project for the required form type. When creating system task for Attach Document, remember to ensure that 'Adobe Sign' is selected as 'Document Source' to use this integration option.

2. Once the system tasks are created, we need to create triggers on forms based on each of the system tasks configured. See details below:

  • Create a workflow trigger on form for same form type and in the same project. This workflow trigger is meant to be configured in a way that the first system task for 'Integration Authorization (OAuth)' can be triggered upon 'Create App' event in 'Post (Sync)' task mode.
    ​​

  • Create a workflow trigger on form for same form type and in the same project. This workflow trigger is meant to be configured in a way that the second system task for 'Attach Document' can be triggered upon 'Integration Connector' event in 'Post' task mode and 'Adobe Sign Accepted' task type.

  • Create a workflow trigger on form for same form type and in the same project. This workflow trigger is meant to be configured in a way that the second system task for 'Status Change' can be triggered upon 'Integration Connector' event in 'Post' task mode and 'Adobe Sign Rejected' task type.

3. Since the system task is configured to trigger on 'Create App' event, user can now create a form. Below are the relevant help links for reference:

Click here to understand how to create a form. Once the form is created by clicking on the 'Send' link, the Adobe sign-in screen will soon appear in a new browser tab. Based on the integration setup, you can then proceed further on the Adobe website.



Did this answer your question?