Adobe Sign Integration (via Microsoft Power Automate)


About This Integration

IntegrationIntroduction

You can integrate third-party systems with Product name - ev itsm.png in many ways. The method you select will depend on business requirements, architectural and security constraints as well as the characteristics specific to each third-party application or service.

This document describes an integration process that has already been implemented in a customer context. 

To find out more about this integration (e.g. scripts to be used), please contact the Logo - EasyVista.png Consulting & Professional Services team, the Logo - EasyVista.png Support team, or your service provider and integrator.
 

Overview of the integration

Adobe Sign is an electronic signature service developed by Adobe. Signatures can easily be inserted in any document and replaces the manual completion of forms, signing and validations.

This integration enables you to incorporate an Adobe Sign e-signature process for a ticket created in Service Manager using Microsoft Power Automate (previously Microsoft Flow). An MS Power Automate workflow is created in Microsoft Azure Logic Apps, using the EasyVista Service Manager connector to retrieve the ticket, followed by the Adobe Sign connector to insert an e-signature.
 

Overview of tools used in this integration

  • Microsoft Azure Logic Apps enables you to integrate and connect hundreds of on-premises or cloud-based applications and Web services, data and devices easily.
  • Microsoft Power Automate is used to automate recurrent tasks by building workflows via Web applications. These applications use MS Power Automate connectors (based on Microsoft Azure Logic Apps) or the MS Graph gateway to interface with any termination point via HTTP/HTTPS protocol.
     
Integration Data Feed (direction) Authentication Type Integration Connector Options

Logo - EV Service Manager.png

Down arrow.png

Logo Icon - Microsoft Flow.png

Down arrow.png

Logo Icon - Adobe Sign.png

Down arrow.png

Logo - EV Service Manager.png

  • Depending on the third-party service used (authentication managed by Logic Apps)
  • Basic Authentication for the Service Manager REST API
  • Service Manager:

    EV Integration connector icon - Workflow.png    Workflow

    EV Integration connector icon - Business rule.png    Business rule

  • MS Power Automate:

    EV Integration connector icon - Receive.png   Connector: When a HTTP request is received

    (Service Manager trigger => Logic Apps)

Available versions
SaaS-based On-premises
Service Manager Check icon.png Check icon.png
Third-Party Product Check icon.png N/A

Microsoft Azure Logic Apps flows

A signature request for a Service Manager ticket is performed through two flows in Microsoft Azure Logic Apps.

MS Power Automate flow #1: Request Adobe Sign signature MS Power Automate flow #2: Close Adobe Sign signature request
Data feed diagram 1 - EN.png Data feed diagram 2 - EN.png

Step-by-Step Integration Process

You add an Adobe Sign e-signature to a Service Manager ticket in several steps:

Prerequisites

Best Practice

  • The procedure describes all of the steps for creating the two Microsoft Azure Logic Apps flows. To facilitate integration, the ZIP folders shipped with this integration contain two pre-configured flows. Once you have downloaded them, you should specify the parameters specific to your environment, i.e. Azure account credentials, EasyVista server address, login information of your Service Manager platform, etc.

Microsoft Azure Logic Apps: Create MS Power Automate flow #1 Request Adobe Sign signature

Description of the workflow
         Azure flow description - Request for signature.png

Best Practice icon.png  Download the file below containing the pre-configured flow. Once you have imported it to Microsoft Azure Logic Apps, you can adapt it to your requirements using the procedure below. This procedure describes all of the steps for creating the workflow.

       Download icon.png  Flow Request Adobe Sign signature

Step 1: Create the step to trigger the flow when a document requires a signature.

1. Log in to the Azure portal using your Azure account login.

2. Create a new logic app, then open the Logic Apps Designer.
         Open url.png See Microsoft Azure Logic Apps integration for the detailled procedure.

3. Create a When a HTTP request is received step to trigger the flow.

         Action Azure - Request for signature - When a http request is received.png

4. Specify the information on the trigger.

  • Body: Copy and paste the JSON schema below.

    Display the JSON schema

    {
       "$id": "http://example.com/example.json",
       "type": "object",
       "definitions": {},
       "$schema": "http://json-schema.org/draft-07/schema#",
       "properties": {
           "Description": {
               "$id": "/properties/Description",
               "type": "string",
               "title": "Description",
               "default": "",
               "examples": [
                   "{Description}"
                ]
            },
           "id": {
               "$id": "/properties/id",
               "type": "string",
               "title": "Id",
               "default": "",
               "examples": [
                   "{id}"
                ]
            },
           "Host": {
               "$id": "/properties/Host",
               "type": "string",
               "title": "Host",
               "default": "",
               "examples": [
                   "{Host}"
                ]
          
     },
           "URL": {
               "$id": "/properties/URL",
               "type": "string",
               "title": "URL",
               "default": "",
               "examples": [
                   "{URL}"
                ]
            },
           "Account": {
               "$id": "/properties/Account",
               "type": "string",
               "title": "Account",
               "default": "",
               "examples": [
                   "{Account}"
                ]
            }
        }
    }
  • Method: POST.

5. Save the trigger.

  The following information will be retrieved from Service Manager: Ticket description, Ticket ID, Host, URL, Account.

6. Click Copy icon.png to copy the URL displayed in the HTTP POST URL field and paste it in your text editor in order to store it temporarily. You will be asked for the URL when defining the configuration in Service Manager (steps 2 and 4).

Step 2: Retrieve the file attachments for the Service Manager ticket.

1. Search for the EasyVista Service Manager connector.

2. Select the Get Request – Incident Document List action associated with this connector.

Best Practice icon.png  Use the search field to find the connector and action you want quickly.

         Action Azure - Request for signature - EV SM Get request – Incident (1).png

         Action Azure - Request for signature - EV SM Get request – Incident (2).png

3. Specify the information for the Service Manager account and ticket.

  • Account: Account on the Service Manager platform.
  • ID: Ticket ID in Service Manager.

4. Select the connection to your environment.

         Action Azure - Request for signature - EV SM Get request – Incident (3).png

Step 3: Request an Adobe Sign signature for each file attachment in the ticket.

1. Create a loop to process all of the documents.

  • Create an Apply to each action to start the loop.
  • Select an output from previous steps: Select the dynamic value called Documents returned by the Get request – Incident Document List action.
             Action Azure - Request for signature - Apply to each - Create loop - Information.png

2. Create the action that will retrieve the document and get an ID.
         Action Azure - Request for signature - Apply to each - Loop - Create action 1 - Flow.png

  • Click Add an action.
  • Search for the Adobe Sign connector.
  • Select the Upload a document and get a document ID action associated with this connector.
             Action Azure - Request for signature - Apply to each - Loop - Create action 1.png
  • Specify the information for the document.
    • File Name: Document name.
    • File Content: Select the dynamic variable called Current Item.
               Action Azure - Request for signature - Apply to each - Loop - Create action 1 - Information.png

3. Create the action that will create an agreement for the document.
         Action Azure - Request for signature - Apply to each - Loop - Create action 2 - Flow.png

  • Click Add an action.
  • Search for the Adobe Sign connector.
  • Select the Create an agreement from an uploaded document and send a signature action associated with this connector.
             Action Azure - Request for signature - Apply to each - Loop - Create action 2.png
  • Specify the information for the agreement.
    • Agreement Name: Name of the agreement.
    • Document ID: Select the dynamic value called Document ID returned using the Upload a document and get a document ID action.
    • Signature Type: Select the E-Signature value.
    • Recipient Email: Enter an email address that exists in Service Manager.
    • Recipient Role: Select the Signer value.
    • Message: Select the dynamic values TheURLSchema and TheIdSchema from step 1 (the step for creating the flow trigger).
               Action Azure - Request for signature - Apply to each - Loop - Create action 2 - Information.png
  • Save the action.
    An Adobe Sign signature request is submitted for the ticket.

Microsoft Azure Logic Apps: Create MS Power Automate flow #2 Close Adobe Sign signature request

Description of the workflow
         Azure flow description - End action signature waiting.png

Best Practice icon.png  Download the file below containing the pre-configured flow. Once you have imported it to Microsoft Azure Logic Apps, you can adapt it to your requirements using the procedure below. This procedure describes all of the steps for creating the workflow.

       Download icon.png  Flow Close Adobe Sign signature request

Step 1: Create the step to trigger the flow once a document is signed.

1. Search for the Adobe Sign connector.

2. Select the When the state of an agreement changes action associated with this connector.
         Action Azure - End action signature waiting - When the state of an agreement changes.png

3. Specify the information for the flow.

  • Name: Flow name.
             example  EasyVista
  • Scope: Select the Any of my agreements value.
  • Events - 1: Select the When an agreement workflow is completed successfully value.
             Action Azure - End action signature waiting - Information.png

Step 2: Retrieve the number of the ticket with a signature request.

1. Define the Compose_RFC_NUMBER variable that will retrieve the ticket number. Create the following actions in the order listed below.

Action Details
1.a Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable EZV - Information.png

  • Name: Variable name.

    example   EZV

  • Value: Select the dynamic value called Agreement Message from the When the state of an agreement changes action.
1.b Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable EZV tab - Information.png

  • Name: Variable name.

    example   EZV array

  • Value: Enter the following formula.
    split(variables('EZV'),';')
1.c Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable EZV tab - Information.png

  • Inputs: Enter the following formula.
    variables('EZV Array')[0]
1.d Create a Compose action that will store the ticket number.

Action Azure - End action signature waiting - Compose rfc_number - Information.png

  • Inputs: Enter the following formula.
    variables('EZV Array')[1]

2. Retrieve the ticket number using the variables you just created.

  • Create a HTTP GET Action action.
  • Specify the information on the action.
    • Method: Enter the GET value.
    • URI: Enter the following formula.

      concat(concat(concat(outputs('Compose_URL'),'actions?search=request.rfc_number:'),outputs('Compose_RFC_NUMBER')),',ACTION_LABEL_EN:" Wait Adobe Sign"')

         Action Azure - End action signature waiting - Http get action - Information.png

Step 3: Close the Wait for Adobe Sign signature action for the ticket.

1. Define the Action_ID variable that will retrieve the ID of the action to be closed. Create the following actions in the order listed below.

Action Details
1.a Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable Body - Information.png

  • Name: Name of the Body variable.
  • Value: Select the dynamic value called Body from the HTTP GET Action action.
1.b Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable Body tab - Information.png

  • Name: Name of the Body Array variable.
  • Value: Enter the following formula.
    split(variables('Body'),',')
1.c Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable Action ID string - Information.png

  • Name: Name of the String Action_ID variable.
  • Value: Enter the following formula.
    variables('Body Array')[5]
1.d Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable Action ID tab - Information.png

  • Name: Name of the Action_ID Array variable.
  • Value: Enter the following formula.
    split(variables('String Action_ID'),'"')
1.e Create an Initialize variable action.

Action Azure - End action signature waiting - Initialize variable Action ID - Information.png

  • Name: Name of the Action_ID variable.
  • Value: Enter the following formula.
    variables('Action_ID Array')[3]

2. Update the ticket using the variables you just created.

  • Create a HTTP PUT action.
  • Specify the information on the action.
    • Method: Enter the PUT value.
    • URI: Enter the following formula.

      concat(concat(outputs('Compose_URL'),'actions/'),outputs('Compose_RFC_NUMBER'))

    • Body: Enter the following JSON code.

      {
        "end_action": {
          "action_id": "@{variables('Action_ID')}"
        }
      }

         Action Azure - End action signature waiting - Http put - Information.png

Service Manager: Create a resource called Adobe Sign e-signature used in a REST step in the ticket creation process

Step 1: Manage rights for using the Service Manager REST API.

    Open url.png See the description of profiles.

1. Select Administration > Access Management > User Profiles in the menu.

2. Select a user profile authorized to use the REST API.

3. Tick the REST API box.
Your modifications will automatically be saved.

4. Repeat the procedure for all authorized profiles.

Step 2: Create a resource called Adobe Sign e-signature associated with a Microsoft Power Automate service.

       Open url.png See How to define a new resource and associate it with a REST action.

1. Select Administration > REST > Services in the menu.

2. Create a new service.
         Service Manager - Microsoft Flow Service.png

  • Service Name: Microsoft Power Automate.
  • Authentication Method: None.
  • Service URL: URL for accessing the new Microsoft Power Automate service.
    • Copy and paste the URL you stored in your text editor in step 1 when creating the MS Power Automate flow called Request Adobe Sign signature in Logic Apps.
    • You should keep only the text displayed in yellow below.

      https://prod-55.westeurope.logic.azure.com:443/workflows/a903f9140a874277be8b9dd39b5c4305/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=R-FJw5q_MEn-I-98MNF794bVtN91QIWFt8gixg-8

    • Replace prod-55.westeurope with {subdomain}.
       

3. Create a connection to the Microsoft Power Automate service.
         Service Manager - Microsoft Flow Connection.png

  • Connection Name: Adobe Sign Power Automate.
  • Authentication Method: None.
  • Service Name: The Microsoft Power Automate service you created earlier.
    The URL of the Microsoft Power Automate service will automatically appear.
  • subdomain: Copy and paste the prod-55.westeurope value of the URL you stored in your text editor.
     

4.  Create a resource associated with the Microsoft Power Automate service that will request an Adobe Sign e-signature.
         Service Manager - Microsoft Flow Resource.png

  • Label: Name of the resource.
  • Resource URI: ID of the new resource.
    • Copy and paste the URL you stored in your text editor in step 1 when creating the MS Power Automate flow called Request Adobe Sign signature in Logic Apps.
    • You should keep only the text displayed in yellow below.

      https://prod-55.westeurope.logic.azure.com:443/workflows/a903f9140a874277be8b9dd39b5c4305/triggers/manual/paths/invoke?api-version=2016-06-01&sp=%2Ftriggers%2Fmanual%2Frun&sv=1.0&sig=R-FJw5q_MEn-I-98MNF794bVtN91QIWFt8gixg-8

  • Content: Body of the request containing the data to be updated. Copy and paste the text below without inserting any spaces or line breaks.

    Note: If you paste a JSON schema copied from a third-party editor such as Microsoft Word, Notepad++, etc., invisible characters may be inserted. This will create an error in the processing of the REST step using the resource.

    {"Description": "{Description}","id": "{id}","Host": "{sys.EVSM_HOST}","URL": "{sys.EVSM_REST_SERVICE_URL}","Account": "{sys.EVSM_ACCOUNT}"}

Step 3: Use the resource called Adobe Sign e-signature used in a REST step in the ticket creation process.

       Open url.png See How to define a new resource and associate it with a REST action.

1. Open the workflow or the business rule-related process you want.

  • Workflow: References > Other References > Workflows (Operation/Transition)
  • Business rule: Administration > Business Rules > Related Processes

2. Click and drag the new resource from the REST Actions category to the graphic editor of the process.
A new step will be added to the process.

3. Double-click to define the properties of the new step.

Links to other integrations

Tags:
Last modified by Unknown User on 2020/07/30 09:19
Created by Administrator XWiki on 2020/06/23 13:37

Shortcuts

Recent changes
•  Service Manager
•  Service Apps
•  Self Help

Glossary

Powered by XWiki ©, EasyVista 2020