Pre-requisites:
The required role privilege is 'Manage Workflow Rules' on the project where a system task needs to be created.
The 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 a system task for Forms (steps 1 to 5).
2. In the task dropdown, select 'Authorization Integration'.
'Authorization Integration' applies to OAuth integrations (such as Asite Integration with DocuSign) and API integrations (such as Asite Integration with Adobe Sign).
This system task enables you to configure the 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.
As mentioned below, you will get options based on the selected authorization type.
In the case of the 'OAuth' authorization type:
Base URL - Enter the applicable base URL for the relevant third-party service - such as DocuSign.
Token URL - Enter the Token URL applicable for relevant third-party services.
Client ID - Enter the Client ID provided by / generated from the relevant third-party service. E.g. to get the client ID for your DocuSign account, log in to your developer account at 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 the screenshot below. If required, click 'Add App and Integration Key' to create a new one. Copy the 'Integration Key' 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 example, to get the secret key for your DocuSign account, log in to your developer account at https://developers.docusign.com/, and go to the screen for 'Apps and Integration Keys'. Go to the 'Actions' menu for the concerned app and select the 'Edit' option. On the next screen, go to the 'Authentication' section and click 'Add Secret Key' to add a new secret key for the selected app per the screenshot below. Copy the secret key generated and paste it as 'Secret' in your system task configuration.
Scope - Enter the scope of Authorization Integration as applicable. For example, 'signature' for DocuSign Integration.
In the case of the 'API Key' authorization type:
Base URL - Enter a Base URL applicable to the relevant third-party service - like Adobe Sign.
API Key Name - Enter the API key name of authorization integration as 'Authorization'.
API Key - Enter the API key value. provided by / generated from the relevant third-party service. E.g. to get the API key for your Adobe Sign account, log in to your developer account at https://www.adobe.com/in/sign/developer-form.html, go to the 'API' menu:
Next, click the 'Integration Key' link (as seen in the above screenshot).
After that, the Integration key tab will appear on the screen where the integration key name must be specified. You can enter a name for the integration.
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 the integration key will be listed on the 'Access Tokens' page.Click 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 integration key and find it yourself by following the above steps.
4. Once done, click the 'Create' button to create 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 executed automatically according to the conditions outlined in the relevant workflow trigger. The related form audit history and task assignment details indicate that they were performed by the 'Workflow Agent'.