Integrating with the Adobe Sign service

  • Versão de lançamento: Australia
  • Atualizado 12 de mar. de 2026
  • 3 min. de leitura

    • Request electronic signatures through the Adobe Sign service with the Adobe Sign integration. This integration depends on the Adobe Sign spoke in IntegrationHub, and is enabled for the signing of adhoc documents (HR PDF document templates) and Adobe Sign templates.

    Importante:

    Starting with the Australia release, HR Document Templates is being prepared for future deprecation. It will be hidden and no longer activated on new instances, but will continue to be supported.

    Use Document Templates and Document Template integration with AdobeSign that provide the latest experience for this functionality. For migration guidelines, see Migrating from HR Document Templates to Document Templates.

    For deprecation details, see the Deprecation Process [KB0867184] article in the Now Support knowledge base.

    A preconfigured HR service, flow, and HR case template for both the adhoc document and Adobe Sign document are available to use.
    Nota:
    The Adobe Sign Integration flow will be completed (or not in waiting state) only after all the HR tasks created for the HR case are signed or expired or cancelled by the users.

    Adobe Sign spoke

    The Adobe Sign integration depends on the Adobe Sign spoke in IntegrationHub. Before you begin, your administrator must have:

    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.

    Tabela 1. Adobe sign integration configuration requirements
    Type of document Configuration requirements
    Adhoc document (HR PDF document template)
    1. Create a managed document that you want to make available for signing. See Managed Documents for more information.
    2. Configure an HR service for the adhoc document.
    3. Configure an HR PDF document template for an adhoc document.
    Adobe Sign document
    1. Create an Adobe Sign template that you want to make available for signing.
    2. Configure an HR service for the Adobe Sign integration.
    3. Configure an HR PDF document template for an Adobe Sign template.

    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.

    For more information, see Request an electronic signature through the Adobe Acrobat Sign service.