Adobe Sign enables e-signature workflows for Adaptive Forms. E-signatures improve workflows to process documents for legal, sales, payroll, human resource management, and many more areas.
In a typical Adobe Sign and Adaptive Forms scenario, a user fills an Adaptive Form to apply for a service. For example, a credit card application and a citizen benefits form. When a user fills, submits, and signs the application form, the form is sent to the service provider for further action. Service provider reviews the application and uses Adobe Sign to mark the application approved. To enable similar electronic-signature workflows, you can integrate Adobe Sign with AEM Forms.
To use Adobe Sign with AEM Forms, configure Adobe Sign in AEM Cloud Services:
You require the following to integrate Adobe Sign with AEM Forms:
After prerequisites are in place, perform the following steps to configure Adobe Sign with AEM Forms on the Author instances.
On AEM Forms author instance, navigate to Tools > General > Configuration Browser.
On the Configuration Browser page, tap Create.
In the Create Configuration dialog, specify a Title for the configuration, enable Cloud Configurations, and tap Create. It creates a configuration container to store Cloud Services. Ensure that the folder name does not contain any space.
Navigate to Tools > Cloud Services > Adobe Sign and open the configuration container you created in the previous step.
When you create an Adaptive Form, specify the container name in the Configuration Container field.
On the configuration page, tap Create to create Adobe Sign configuration in AEM Forms.
In the General tab of the Create Adobe Sign Configuration page, specify a Name for the configuration, and tap Next. You can optionally specify a Title and browse to select a Thumbnail for the configuration.
Copy the URL in your current browser window to a notepad. The URL is required to configure Adobe Sign application with AEM Forms in a later step. Tap Next.
In the Settings tab, the OAuth URL field contains the default URL. The format of the URL is:
https://<shard>/public/oAuth/v2
For example:
https://secure.na1.echosign.com/public/oauth/v2
where:
na1 refers to the default database shard. You can modify the value for the database shard. Ensure that the Adobe Sign Cloud Configurations point to the correct Shard.
If you create another Adobe Sign configuration for an Adobe Experience Manager feature or component, ensure that all the Adobe Sign Cloud Configurations point to the same shard.
Keep the Create Adobe Sign Configuration page open. Do not close it. You can retrieve Client Id and Client Secret after configuring OAuth settings for the Adobe Sign application as described in upcoming steps.
Configure OAuth settings for the Adobe Sign application:
For step-by-step information to configure OAuth settings for an Adobe Sign application and obtain the keys, see Configure oAuth settings for the application developer documentation.
Go back to the Create Adobe Sign Configuration page. In the Settings tab, specify the [Client ID (also referred to as Application ID) and Client Secret]. Use the Client ID and Client Secret of Adobe Sign application you created in previous step.
Select the Enable Adobe Sign for attachments option to append files attached to an Adaptive Form to the corresponding Adobe Sign document sent for signing.
Tap Connect to Adobe Sign. When prompted for credentials, provide username and password of the account used while creating Adobe Sign application. When asked to confirm access for your developer account
, Click Allow Access. If the credentials are correct and you allow AEM Forms to access your Adobe Sign developer account, a success message similar to the following appears.
Tap Create to create the Adobe Sign configuration.
Select the configuration and click Publish, select the configuration, and click Publish. It replicates the configuration to corresponding publish environments.
Repeat all the above steps on your developer, stage, and production instances (whichever left) to complete configuring Adobe Sign with AEM Forms for your environment.
Now, you can use add Adobe Sign fields to an Adaptive Form. Ensure that you add the configuration container used for the Cloud Service to all the Adaptive Forms being enabled for Adobe Sign. You can specify a configuration container from the properties of an Adaptive Form.
When you use Adobe Sign Workflow step to Sign an Adaptive Form, the form can be passed across signers one after another or can be sent to all the signers simultaneously, depending on the configuration of workflow step. Adobe Sign enabled Adaptive Forms are submitted to Experience Manager Forms Server only after all the signers complete the signing process.
By default, the Adobe Sign Scheduler services checks (polls) signer response after every 24 hours. You can change the default interval for your environment.
To change the default interval, specify a cron expression for the sign.status.exp property of the Adobe Sign Configuration Service configuration.
For example, to run the configuration service daily at 00:00 am, set the sign.status.exp property of the Adobe Sign Configuration Service configuration to specify 0 0 0 1/1 * ? *
. The following JSON file displays the sample to run the configuration service daily at 00:00 am:
{
"sign.status.exp":"0 0 0 1/1 * ? *"
}
To set values of a configuration, Generate OSGi Configurations using the AEM SDK, and deploy the configuration to your Cloud Service instance.