Skip to main content
All CollectionsSystem TasksCreate a System Task in a ProjectCreate a System Task for Forms in a Project
Create a System Task - Authorization Integration on Forms (in a Project)
Create a System Task - Authorization Integration on Forms (in a Project)

This article helps you understand how to create a system task for setting up authorization integration on forms in a project.

Updated over a week ago

Pre-requisites:

Steps to create a system task for setting up authorization integration on forms in a project are as mentioned below:

1. Follow the steps to create system task for Forms (steps 1 to 5).

2. In the task dropdown, select 'Authorization Integration'.

'Authorization Integration' is applicable for OAuth integrations (like Asite Integration with DocuSign) and API integrations (like Asite Integration with Adobe Sign).

This system task enables you to configure required integration details for OAuth integration or API integration with Asite.

3. Below are the fields available to configure in this system task:

Authorization Type - Select the authorization type - 'OAuth' in case of Asite Integration with DocuSign, or 'API Key' in case of Asite Integration with Adobe Sign.

Depending on the selected authorization type, you will get relevant options as follows.
โ€‹

In case of 'OAuth' authorization type:

  • Base URL - Enter Base URL applicable for the relevant third party service - like Docusign.

  • Token URL - Enter Token URL applicable for relevant third party service.

  • Client ID - Enter Client ID provided by / generated from the relevant third party service. For e.g. to get the client id for your DocuSign account, login to your developer account on https://developers.docusign.com/, go to the below screen for 'Apps and Integration Keys' and find the 'Integration Key' for the concerned app as per below screenshot. If required, click on 'Add App and Integration Key' to create a new one. Copy the 'Integration Key' that shows on your screen and paste it as 'Client ID' in your system task configuration.

  • Secret - Enter the Secret Key provided by the third party service to connect their data with Asite for integration. For e.g. to get the secret key for your DocuSign account, login to your developer account on https://developers.docusign.com/, go to the below screen for 'Apps and Integration Keys'. Go to the 'Actions' menu for the concerned app and select 'Edit' option. On the next screen, go to 'Authentication' section and click on 'Add Secret Key' to add a new secret key for the selected app as per below screenshot. Copy the secret key generated and paste it as 'Secret' in your system task configuration.

  • Scope - Enter scope of Authorization Integration as applicable. For e.g. 'signature' for DocuSign Integration.

In case of 'API Key' authorization type:

  • Base URL - Enter Base URL applicable for the relevant third party service - like Adobe Sign.

  • API Key Name - Enter API key name of authorization integration as 'Authorization'.

  • API Key - Enter API key value. provided by / generated from the relevant third party service. For e.g. to get the API key for your Adobe Sign account, login to your developer account on https://www.adobe.com/in/sign/developer-form.html, go to the 'API' menu:

    Next, click on the 'Integration Key' link (as seen in above screenshot).
    After that, Integration key tab will be displayed on the screen where integration key name is to be specified. Enter integration name as needed.
    Then select scopes for permissions as required and click 'Save'.
    Once the integration name and its permissions are saved, a new key will be generated and integration key will be listed on the 'Access Tokens' page.

    Click on the 'Integration Key' hyperlink to view the key details:

    Note: The key in the screenshot is greyed out, as such integration keys are specific to the users who create it, and not meant to be shared with anyone else. You can create your own key and find them yourself by following the above steps.

4. Once done, click on 'Create' button to complete creating a system task.

You can create independent system tasks which can be executed using workflow triggers without adding them to a complex workflow.

All system tasks are performed by system automatically based on the condition defined in related workflow trigger. It appears in related form audit history & task assignment emails as performed by 'Workflow Agent'.



Did this answer your question?