Adobe Sign for Microsoft PowerApps and Power Automate - Release Notes

Adobe Sign for Microsoft Power Automate v4.0

Improvements

The Adobe Sign For Power Automate connector has been improved to allow for  three connection types:

  • Adobe Sign user
  • Adobe Sign group administrator
  • Adobe Sign account administrator

Actions can be executed in the name of other users from the connection owner's account (or group) when the connection owner is an Adobe Sign administrator (group or account level).

Nota:

Power Automate, Power Apps, and Logic Apps flows can be shared with the created connection by adding new owners of the flow, or as a run-only sharing (with or without sharing the connection).

For more details, see User Guide.

Previous releases

The Adobe Sign For Power Automate connector has been improved to allow for  three connection types:

  • Adobe Sign user
  • Adobe Sign group administrator
  • Adobe Sign account administrator

Actions can be executed in the name of other users from the connection owner's account (or group) when the connection owner is an Adobe Sign administrator (group or account level).

Improvements

Support had been added for array inputs (recipients, documents, and form fields) for the following actions:

  • Create an agreement from an uploaded document and send for signature
  • Create a library template from an uploaded document
  • Create an agreement from a document URL and send for signature
  • Create a library template from a document URL
  • Create an agreement from a library template and send for signature

Actions

Several Actions have been updated to the REST v6 API:

  • Create a library template from a document URL
  • Create a library template from an uploaded document
  • Create an agreement from a document URL and send for signature
  • Create an agreement from a library template and send for signature
  • Create an agreement from an uploaded document and send for signature
  • Get a list of all agreements
  • Get a list of all library templates
  • Get form field data of agreement
  • Upload a document and get a document ID

 

Post-signing redirects

A parameter for a post-signing redirect has been added to the three create and send Actions:

  • Create an agreement from an uploaded document and send for signature
  • Create an agreement from a document URL and send for signature
  • Create an agreement from a library template and send for signature
     
Nota:

The Adobe Sign for Power Automate 3.0 update introduces new REST v6 Actions that are intended as replacements for existing actions of the same name.

Legacy Actions will be hidden and deprecated by January 2021.

The list of Actions being deprecated is:

  • Create a library template from a document URL (Old)
  • Create a library template from an uploaded document (Old)
  • Create an agreement from a document URL and send for signature (Old)
  • Create an agreement from a library template and send for signature (Old)
  • Create an agreement from an uploaded document and send for signature (Old)
  • Get a list of all agreements (Old)
  • Get a list of all library templates (Old)
  • Get form field data of agreement (Old)
  • Upload a document and get a document ID (Old)

Support for Microsoft GovCloud (GCC)

v2.1.1 introduces support for customers who are on the Microsoft Government Community Cloud (GCC).

Functionality is essentially the same, with a few platform limitations as noted by Microsoft.

  • GCC High and DoD environments are not supported in this release.

Improvements

To meet increasing demand from customers with complicated workflows and approval processes, we increase the maximum number of recipients, form fields, and files for Adobe Sign actions:

  • Number of recipients is increased from 7 to 25
  • Number of form fields is increased from 10 to 50
  • Number of files is increased from 8 to 10

Actions

With this launch, we introduce two new actions:

  • Retrieve the Signing URL - Retrieves the URL for the e-sign page for the current recipient(s) of an agreement
  • Get form field data of agreement - Retrieves data entered into the interactive form fields of the agreement

New Templates

For both new actions introduced in this release, we are providing sample workflows (templates):

  • Capture signature on PowerApps (Action: Retrieve the Signing URL)
  • Get form data from a completed agreement (Action: Get form field data of agreement)

Triggers

Adobe Sign for Microsoft Power Automate ver 2.0 introduces the Adobe Sign Triggers!

Five Adobe Sign based triggers have been added to the integration:

  • When a new agreement is created
  • When an agreement is sent to a participant
  • When an agreement workflow is completed successfully
  • When the state of an agreement changes
  • When an event occurs

Introducing Adobe Sign for Microsoft Power Automate

Microsoft Power Automate is a tool that connects different apps and services into coordinated multi-step workflows so that repetitive tasks can be automated without the need for complex API coding. 

There are three Power Automate concepts that drive all workflows. The first is that all services can expose their API through a Connector to the service.  Connectors may have Triggers that start workflows.  Connectors must have Actions that drive what happens within the workflow.  There are common logical connectors between actions that control the workflow based on parameters generated by previous actions.

Adobe Sign is a natural participant in this ecosystem because the nature of signature processes usually involves preparation and review of the agreement prior to signature and notification and archival of the document after the agreement is signed.

Power Automate creates an environment where any supported service can be connected to another.  Use cases for the Adobe Sign connector include:

  • Starting a signature process from a service trigger
  • Getting the status of a Sign process
  • Moving documents from the Sign service to other repositories.

Actions

The Adobe Sign integration comes with twelve Actions.  These actions can be coupled with any relevant Trigger, or added to other workflows as part of a larger process:

  • Upload a document and get a document ID
  • Create an agreement from an uploaded document and send for signature
  • Create a library template from an uploaded document
  • Create an agreement from a document URL and send for signature
  • Create a library template from a document URL
  • Create an agreement from a library template and send for signature
  • Get a list of all agreements
  • Get a list of all library templates
  • Get the status of an agreement
  • Get a list of all the document IDs from an agreement
  • Get a PDF of a signed agreement
  • Get a document from an agreement

Templates

Eleven templates are provided by Adobe Sign with this first release, giving a broad sample of some of the workflows that can be produced using the Actions described above:

  • Get signatures on a new asset in Creative Cloud
  • Get signatures on a new file in Box
  • Get signatures on a new file in Dropbox
  • Get signatures on a new file in OneDrive
  • Get signatures on a new file in OneDrive for Business
  • Get approval on a new file in OneDrive for Business
  • Get signatures on a new file in SharePoint
  • Get signatures for a new SharePoint item using Adobe Sign Library
  • Get signatures for a selected SharePoint item using Adobe Sign Library
  • Get signatures on a selected file in SharePoint
  • Get signatures for a selected SharePoint item

More like this

Logo Adobe

Accedi al tuo account