4.0.5 update contains several security fixes related to OAuth login.

4.0.4 is fully adapted to use account-specific domains for all newly generated traffic.

The Adobe Sign icon has been updated to the new graphic.

Rebranded to Adobe Sign (from Adobe Document Cloud eSign services)
You’ll see Adobe Sign where you previously saw Adobe eSign Services as evidence of the rebranding.
 

Due to an API regression bug introduced when NetSuite performed their platform update, a new package (v4.0.1) has been released.

Customers are encouraged to update to the newest package.

Added auto provisioning of users through NetSuite

A new custom preferences has been added for v4.0. When enabled, users who send agreements in NetSuite are automatically auto-provisioned with an Adobe Document Cloud eSign services user account.

'Built for NetSuite' certified

This version achieved the 'Built for Netsuite' certification and meets all the latest NetSuite design best practices.

Rebranded to Adobe Document Cloud eSign services (from EchoSign)

You’ll see Adobe Document Cloud eSign Services (or Adobe eSign Services for short) where you previously saw Adobe EchoSign as evidence of the rebranding.

Implemented enhanced security with OAuth

To improve data security, eSign services now uses OAuth 2.0 to authenticate your Adobe Document Cloud eSign services account within NetSuite. This new protocol lets NetSuite talk to eSign services without requesting your eSign services password. Since sensitive information is not being shared directly between the apps, your account is less likely to be compromised. This improvement will not impact your implementation, but you will need to do a one-time setup to authorize your NetSuite package to communicate with the Adobe Document Cloud. This is done during the installation process. For customers upgrading from a previous version of the package—v3.5.9 and prior—the API key previously used will be replaced by an OAuth token generated during the authorization process.

Migrated the eSign services from SOAP APIs to REST APIs

To improve efficiency, flexibility and processing speed, Adobe Document Cloud eSign services—and consequently the v4.0 integration for NetSuite—has migrated from SOAP-based to REST-based APIs.

Advanced Participant Roles - Approver

• One or more recipients can be marked as approver(s) in an agreement
• Approvers are required to reviewand approve the document
• Approvers can also be required to fill data into the agreement before approving

Preview Document or Drag and Drop Form Fields Before Sending

Preview agreement or drag and drop form !elds before sending for signature

Send Reminder to Current Signer

Send immediate reminder to current signer

Advanced Signer Authentication Policies

• Knowledge Based Authentication – Answer questions to verify signer identity
  • Requires Signers to prove their identity by answering questions taken from hundreds of public and commercial databases
  • Name on signature is taken from the user’s authenticated name and cannot be changed at the time of signing
  • Powered by RSA
  • KBA usage is limited per account, per month. Contact Sales for more information.
• Web identity – sign in with Facebook, LinkedIn, Google, etc. before signing
  • Signer can only sign after verifying their identity using a 3rd party Web service
    • Google, LinkedIn, Facebook, Microsoft Live, Yahoo!, Twitter
  • Name on signature is taken from the user’s web service pro!le and cannot be changed at the time of signing
  • Audit trail captures identity verification details
• One Time Password
• Apply authentication methods for internal or external signers or all signers.
  • E.g. External signers need to use a password or use Knowledge Based Authentication while Internal signers do not

Additional Custom Preferences

• Add Signed PDF as a link to the !le URL or as a"achment hosted in NetSuite
• Add Audit Trail to Agreement record a$er agreement is signed
• Use the transaction contact as !rst signer by default, instead of Customer email
• Grant Senders the option to mark recipients as Approvers

Transaction Files

Easily select !les to a"ach from the current transaction with new ‘Transaction Files’ dropdown list

Adobe PDF Certification For All EchoSign Documents

• All PDF files sent or downloaded from EchoSign will be certi!ed with an Adobe EchoSign Digital Certificate
• Acrobat or Reader will display the certi!cation guaranteeing that the document has not been tampered with for additional trust and peace of mind

Collect Supporting Documents

• Senders can collect additional supporting documents from Signers during signing (e.g. driver’s license, business certificate)
• Collected documents become part of the official record of the signed agreement

Conditional Data Fields

• Define conditional logic for agreement fields
• Conditions can be based on values for one or more fields on the agreement
• Conditions can be de!ned through the drag-and-drop forms authoring UI or through text-tags
• Signer is presented with the appropriate !elds when signing a document based on the de!ned conditions

Additional EchoSign Form Fields Enhancements

• Dropdown menus
• Field masking
• Radio buttons
• Create shorter text tags to maintain document structure