Adobe Sign Release Notes: 2021

Note:

This document highlights the new features,  experience changes, and resolved issues in the current release.

Not all features/changes are guaranteed to be enabled on the date of the release.

If you would like to be notified of release notes via email, please subscribe here >

Adobe Sign: October 2021  

Improved Functionality

  • Report Abuse Links - Small business and individual tier accounts now include a link for recipients to access a method to report potentially abusive activity regarding inbound agreement requests.
  • Notarize Integration - Adobe Sign integration with  Notarize, Inc.'s Remote Online Notarization(RON) platform allows customers to add remote online notarization service as part of their Adobe Sign transactions. Available for enablement for US customers in enterprise and business tiers sold directly by Adobe via the ETLA program. Notarize Transactions can be purchased as an add-on at an additional cost for these customers only.
    • Send page updates - Customers with notary enabled can select the Requires notarization option on the recipient record, just to the right of the authentication method:
Note:

Customers that use the embedded Send page in their applications or integrations will also have access to the notary functionality.

Notarize Interface on the Send page

After the agreement is configured and the sender clicks Next, the sender is presented with additional configuration options for the notarization process:

Configure Notarize options

  • API updates - There are significant updates to the APIs to support the Notarize Integration:

POST /agreements

The POST /agreements API has been updated to support sending an agreement for notarization.

  • A new role, NOTARY_SIGNER, should be used to indicate a notary session participant.
  • A new NotaryInfo attribute has been added to the AgreementInfo definition to contain all of the options associated with creating a new agreement that requires notarization.

Parameter Name

REST Object

Description

memberInfos

ParticipantInfo[]

Array of ParticipantInfo objects, containing participant-specific data (email, e.g.). All participants in the array belong to the same set.

role

Value

Description

SIGNER

Signs the Agreement

APPROVER

Approves the Agreement

DELEGATE_TO_SIGNER

One who herself can not sign but delegates the agreement to another signer

DELEGATE_TO_APPROVER

One who herself can not approve but delegates the agreement to another approver

SHARE

Participant with whom this agreement has been shared

DELEGATE

Participant to whom the Agreement was delegated. This role can not be used at the time of creating or updating agreement through POST/PUT call on agreement resource. Delegation happens separately by participants.

NOTARY_SIGNER

Notary Session Participant

Role assumed by all participants in the set (signer, approver, etc.)

 

FileInfo extension

The FileInfo definition will need to be expanded to indicate which documents should be notarized.

FileInfo

Parameter Name

Type

Default

Required

Description

document

Document

optional

A document that is associated with the agreement.
This field cannot be provided in POST call.
In case of GET call, this is the only field returned in the response

label  

String

optional

The unique label value of a file info element. In case of custom workflow this will map a file to corresponding file element in workflow definition.

libraryDocumentId

String

optional

ID for an existing Library document that will be added to the agreement

transientDocumentId

String

optional

ID for a transient document that will be added to the agreement

notarize

true

false

optional

Indicates that this document needs to be notarized.

 

ParticipantInfo extension

The ParticipantInfo definition has been expanded to allow the notary authentication method to be specified.

ParticipantInfo

Parameter Name

Type

Default

Required

Description

email

String

N/A

required

Email of the participant.

notaryAuthentication

Enum

MULTI_FACTOR_AUTHENTICATION

optional

MULTI_FACTOR_AUTHENTICATION - Notary authentication is performed using a two-factor authentication method
NONE - No authentication is required.

 

NotaryInfo

A new optionanotaryInfo field has been added to the AgreementInfo definition to contain the NotaryInfo object that specifies additional options associated with notarization.

NotaryInfo

Parameter Name

Type

Default

Required

Description

notaryType

Enum

If only Notarize Notary on Demand Service is enable on the account,
then the notaryType will default to NOTARIZE_NOTARY, otherwise it will default to BYON_NOTARY

required

NOTARIZE_NOTARY - Notarize Service provides the notary
BYON_NOTARY - Account provides the notary

payment

Enum

BY_SENDER

optional

Only applies if type == NOTARIZE_NOTARY
BY_SENDER - Sender pays for the notarization
BY_SIGNER - Signer pays for the notarization

appointmentStart

String

""

optional  

ISO_DATE_TIME formatted string See ISO_ZONED_DATE_TIME

note

String

none

optional  

Notes for notary session.

notaryEmail

String

""

optional  

email of the bring your own notary

 

Example /agreement

{
    "fileInfos": [
        {
            "transientDocumentId": "",
            "notarize": true
        }
    ],
    "name": "notary_agreement_name",
    "participantSetsInfo": [
        {
            "memberInfos": [
                {
                    "email": "someone@somewhere.com",
                    "securityOption": {
                        "notaryAuthentication": "MULTI_FACTOR_AUTHENTICATION"
                    }
                }
            ],
            "order": 1,
            "role": "NOTARY_SIGNER",
            "name": "participant_set_name"
        }
    ],
    "signatureType": "ESIGN",
    "state": "IN_PROCESS",
    "notaryInfo": {
        "appointment": "2021-10-29'T'13:00",
        "notaryEmail": "notaries@email.com",
        "notaryType": "PROVIDER_NOTARY",
        "note": "This is a note for the notary.",
        "payment": "BY_SIGNER"
    }
}

 

PUT|GET /agreements/{aid}

PUT /agreements/{aid} API will support updating an agreement with notarization options. GET /agreements/{aid} API will return any options set for agreement notarization. See POST /agreements section to view updated attributes.

 

Error Codes

Existing error codes for POST /agreements remain unchanged. We have defined a new error code as given below:

REST Error Code

HTTP Status Code

Message

Scenario

PERMISSION_DENIED

403

User setting or OAuth scope token do not permit sending agreement for notarization.

This error will be thrown when role is set to NOTARY_SIGNER and the API caller (i.e prospective sender) does not have notary feature enabled and/or if notary service provider is not set.

 

Documentation impact

In the request's AgreementInfo object, "status" element will include the new agreement status "WAITING_FOR_NOTARIZATION".

 

POST /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/signingTokens

The API can be used by customers (notary signers) to obtain a signing token that allows them to complete the esign phase of the flow. 

  • New signing capability has been added to capture the new role - ACCEPT_BEFORE_NOTARIZATION. 
  • Signing tokens should not be obtained to complete the notarization phase.
{
  "securityInfo": {
  "authenticationMethod": "NONE"
},
  "signingCapabilities": [
    "ACCEPT_BEFORE_NOTARIZATION"
  ]
}

 

PUT /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/status

The API can be used by customers (notary signers) to complete the esign phase of the flow. To accommodate the new role, new enum status value has been introduced - ACCEPTED_BEFORE_NOTARIZATION.

Attribute

Type

Description

Status

Enum<String>

Value

SIGNED

APPROVED

ACCEPTED

DELIVERED

FORM_FILLED

ACCEPTED_BEFORE_NOTARIZATION

                                         

This status indicates that recipient with role SIGNER completed agreement.

This status indicates that recipient with role APPROVER completed agreement.

This status indicates that recipient with role ACCEPTOR completed agreement.

This status indicates that recipient with role CERTIFIED_RECIPIENT completed agreement.

This status indicates that recipient with role FORM_FILLER completed agreement.

This status indicates that recipient with role NOTARY_SIGNER completed agreement without notarizing it

The notary signer can follow the below sequence of API calls to complete the esign phase:

  1. GET /agreements/{agreementId}/members - to fetch the notary signer's participant ID & participant set ID
  2. POST /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/signingTokens - to request signing token for notary signer with ACCEPT_BEFORE_NOTARIZATION capability
  3. POST /transientDocuments - to upload document that was reviewed
  4. PUT /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/status - to submit reviewed document and complete esign phase.

New webhook event

Customers can subscribe to new webhook event, AGREEMENT_READY_FOR_NOTARIZATION, to be notified when agreement is ready for notarization. The event is not visible on the webhooks UI & can be subcribed to via POST /webhooks API call.

Documentation impact

The following APIs are not modified but their documentation has been updated to include new agreement status "WAITING_FOR_NOTARIZATION" or new role "NOTARY_SIGNER".

GET /agreements

In response UserAgreements/UserAgreement object, "status" element now includes corresponding status "WAITING_FOR_NOTARIZATION".

GET /agreements/{agreementId}

In response AgreementInfo object, "status" element now includes corresponding status "WAITING_FOR_NOTARIZATION".

GET /agreements/{agreementId}/events

API is updated to support new READY_TO_NOTARIZE and NOTARIZED events.

In response Event object

  • "participantRole" element now includes new role NOTARY_SIGNER.
  • "type" element includes new events READY_TO_NOTARIZE and NOTARIZED. "description" element will be  "Document sent for notarization" and  "Notarized document received" respectively

GET /agreements/{agreementId}/members/participantSets/{participantSetId}

In response DetailedParticipantSetInfo object, "status" element now includes corresponding status "WAITING_FOR_NOTARIZATION".

PUT /agreements/{agreementId}

Request AgreementInfo object now includes "WAITING_FOR_NOTARIZATION" status.

PUT /agreements/{agreementId}/members/participantSets/{participantSetId}

WAITING_FOR_NOTARIZATION status is one of the "status" element values in the DetailedParticipantSetInfo object.

POST /agreements/{agreementId}/view

WAITING_FOR_NOTARIZATION status has been added as one of the allowed views.

GET /agreements/{agreementId}/members/participantSets/{participantSetId}/participants/{participantId}/signingInfo

If the participant specified in request path has notary signer role, the API will return ACCEPT_BEFORE_NOTARIZATION signing configuration, inline with all of the other signing configurations for this agreement/participant.

Resolved Issues

Issue Description
4308901 Corrected an issue where delegating an agreement with phone authentication would prompt an error if the delegated phone number had the same country code.
4314113 Fixed an issue where default expiration dates could not be edited by users when sending a new agreement
4318558 Corrected an issue where replacing a recipient with phone authentication would prompt a "The participant set ID specified is invalid" error
4319038 Fixed an issue where the Sender was not getting the option for 'External recipients Identity verification' when sending using the 'Send in Bulk' workflow.
4319798 Fixed an issue that could cause the selection of a radio button to jump cursor focus to a different field.
4320154 Fixed an issue that could prevent a library template from saving to a new group relationship.
4323013 Fixed an issue where opening a web form on the manage page would trigger an error: "The document is not yet available or will have no pages to view."
4323554 Fixed an issue where the event time/date stamps for updating admin rights could produce two records with the same time values.
4323609 Fixed an issue where uploading a signed agreement in the manage page would not trigger the AGREEMENT_WORKFLOW_COMPLETED webhook.
4325142 Fixed an issue where custom email templates would not reflect the correct name value for a participant if they canceled the agreement.
4326747 Fixed an issue that could result in the Send in Bulk page not completing the load process, omitting the Upload and Send actions.
4326855 Fixed an issue that could prevent recipients from declining the approval of an agreement.
4327000 Corrected an issue that could cause Smart-Id credentials to fail, with the error indicating that no algorithms were found.
Adobe logo

Sign in to your account