Adobe Sign spoke

Adobe Sign integration setup

Once the Adobe Sign spoke is set up, you can configure the integration for HR. The integration has a single flow that branches out into sub flows, one for signing an adhoc document (HR PDF document template) and another for signing an Adobe Sign template. The sub flow triggered for a document depends on the PDF template type that is configured for that document.

For each document that you want to make available for signing through the Adobe Sign service, configure as follows.

Each adhoc document is configured as a standard HR PDF document template. You can add signers to the document with Mark Signatures, and then map each signature field to an appropriate user field in a table. The positioning of the markings are not used, and the Adobe Sign integration allows the signer to sign anywhere in the document. You can also parse the PDF to map document fields to corresponding table fields to auto-populate the document when it is generated for signing. The generated document is static, which means that it is read-only and the signatory cannot update any of the fields.

Each Adobe Sign template is brought into the ServiceNow system, and then configured into an HR PDF document template to enable mappings. Map each signature field from the Adobe Sign template to an appropriate user field in a table. The generated document is dynamic, which means that the signatory can write in editable fields, such as to update an address or provide W-4 information. However, any updates made are saved to the document only.

Requesting electronic signatures through the Adobe Sign service

Once the integration setup is complete, HR agents from your organization can request electronic signatures through the Adobe Sign service.

• Request an electronic signature through the Adobe Sign service.