User Guide Cancel

Adobe Acrobat Sign for NetSuite: Installation and Customization Guide (v4.0.7)

  1. Adobe Acrobat Sign Integrations
  2. What's New
  3. Product Versions and Lifecycle
  4. Acrobat Sign for Salesforce
    1. Install the Package
    2. Configure the Package
    3. User Guide
    4. Enable Digital Authentication
    5. Developer Guide
    6. Advanced Customization Guide
    7. Field Mapping and Templates Guide
    8. Mobile App User Guide
    9. Flows Automation Guide
    10. Document Builder Guide
    11. Configure Large Documents
    12. Upgrade Guide
    13. Release Notes
    14. FAQs
    15. Troubleshooting Guide
    16. Additional Articles
  5. Acrobat Sign for Microsoft
    1. Acrobat Sign for Microsoft 365
      1. Installation Guide
    2. Acrobat Sign for Outlook
      1. User Guide
    3. Acrobat Sign for Word/PowerPoint
      1. User Guide
    4. Acrobat Sign for Teams
      1. User Guide
      2. Live Sign Guide
      3. Mobile User Guide
      4. Release Notes
      5. Microsoft Teams Approvals
    5. Acrobat Sign for Microsoft PowerApps and Power Automate
      1. User Guide
      2. Release Notes
    6. Acrobat Sign Connector for Microsoft Search
      1. User Guide
      2. Release Notes
    7. Acrobat Sign for Microsoft Dynamics 
      1. Overview
      2. Dynamics Online: Installation Guide 
      3. Dynamics Online: User Guide 
      4. Dynamics On-Prem: Installation Guide 
      5. Dynamics On-Prem: User Guide
      6. Dynamics Workflow Guide
      7. Dynamics 365 for Talent
      8. Upgrade Guide
      9. Release Notes
    8. Acrobat Sign for Microsoft SharePoint 
      1. Overview
      2. SharePoint On-Prem: Installation Guide
      3. SharePoint On-Prem: Template Mapping Guide
      4. SharePoint On-Prem: User Guide
      5. SharePoint On-Prem: Release Notes
      6. SharePoint Online: Installation Guide
      7. SharePoint Online: Template Mapping Guide
      8. SharePoint Online: User Guide
      9. SharePoint Online: Web Form Mapping Guide
      10. SharePoint Online: Release Notes
  6. Acrobat Sign for ServiceNow
    1. Overview
    2. Installation Guide
    3. User Guide
    4. Release Notes
  7. Acrobat Sign for HR ServiceNow
    1. Installation Guide (Deprecated)
  8. Acrobat Sign for SAP SuccessFactors
    1. Cockpit Installation Guide (Deprecated)
    2. Recruiting Installation Guide (Deprecated)
    3. Recruiting User Guide
    4. Cloud Foundry Installation Guide
    5. Release Notes
  9. Acrobat Sign for Workday
    1. Installation Guide
    2. Quick Start Guide
    3. Configuration Tutorial
  10. Acrobat Sign for NetSuite
    1. Installation Guide
    2. Release Notes
  11. Acrobat Sign for SugarCRM
  12. Acrobat Sign for VeevaVault
    1. Installation Guide
    2. User Guide
    3. Upgrade Guide
    4. Release Notes
  13. Acrobat Sign for Coupa BSM Suite
    1. Installation Guide
  14. Acrobat Sign Developer Documentation
    1. Overview
    2. Webhooks
    3. Text Tags

Overview

Adobe Acrobat Sign for NetSuite provides a complete e-signature integration with NetSuite. You can use Acrobat Sign for NetSuite to send agreements such as contracts, quotes, and other documents to recipients directly from NetSuite. You can create and send Adobe Acrobat Sign agreements from customers, leads, quotes, and other NetSuite records. Acrobat Sign updates NetSuite with the status of agreements and stores the agreements with the associated NetSuite records once they are fully executed. You can view the history of all agreements sent from NetSuite from within the product.

For information on the latest updates, refer to the Adobe Acrobat Sign for NetSuite: Release Notes.

To request a 30-day trial, go to Adobe Acrobat Sign trial.

Install the bundle and configure OAuth

Only a NetSuite administrator can install or update the bundle. To configure OAuth, this NetSuite administrator should also have Admin access in Adobe Acrobat Sign. Before installing the bundle in your Production account, you must install and test the bundle in a NetSuite Sandbox account.

For more information about testing, see Create an Adobe Sign agreement.

Caution:

Customers upgrading to v4.0.7 should NOT remove their existing API key.

See Set custom preferences for more information on how the API key is used.

  1. Navigate to Customization > SuiteBundler > Search & Install Bundles.

  2. On the Search & Install Bundles page, Search for  Adobe Acrobat Sign.

  3. Select the Adobe Acrobat Sign bundle name.

    install bundle

  4. On the Bundle Details page, select Install.

    intall sign for netsuite

  5. In the Preview Bundle Install page, click Install Bundle.
    There is no need to change any of the default values on the page.

    preview bundle install

  6. In the install dialog that appears, select OK.

    During installation, the status of the bundle is shown as Pending.

    sign install pending

  7. To view an updated status of installation, select Refresh

    After the bundle installation completes, Adobe Acrobat Sign for NetSuite displays on the Installed Bundles page.

    sign bundle installed

  8. If you are already an Adobe Acrobat Sign customer, proceed to Configure OAuth after installing or upgrading.

    If you don't have an Adobe Acrobat Sign account, you can sign up for Adobe Acrobat Sign trial account

    to test the system.  Follow the online registration steps to enable your Adobe Acrobat Sign account.

Configure OAuth after installing or upgrading

Adobe Acrobat Sign uses OAuth 2.0 to authenticate your Adobe Acrobat Sign account within NetSuite.

This protocol authorizes your installed NetSuite bundle to communicate with Adobe Acrobat Sign without requesting your password. Since sensitive information is not being shared directly between the apps, your account is less likely to be compromised.

This authentication will not impact your implementation, but you must do a one-time configuration after installing or upgrading the bundle in your Production or Sandbox account. 

The NetSuite administrator who configures OAuth must also have account-level admin access in Adobe Acrobat
Sign.

  1. In NetSuite, navigate to the Adobe Sign Config list page.

  2. Search for Adobe Sign Config (a custom record type) using the Search field in the header.

  3. On the Search Results page, select View for the Adobe Sign Config record.

    view acrobat sign config

  4. On the Adobe Sign Config List page, select View for the Using OAuth to Access Adobe Sign APIs record.

    config list

  5. On the Adobe Acrobat Sign Config page, select Login In With Adobe Acrobat Sign.

    Sign config login

  6. When the AdobeAcrobat Sign login page displays, enter your credentials.

    authenticate to Adobe Sign

  7. In the Confirm Access page (for OAuth) that displays, select Allow Access.

    allow access

  8. When the authorization is complete, you are redirected back to Adobe Acrobat Sign Config page in NetSuite as shown below:

    logged in sign

    Note:

    If you are configuring OAuth in your Sandbox account, you will encounter the error “Could not determine customer comp id” when the authorization completes.

    To proceed, you must change the account domain portion of the URL (system.netsuite.com) in your browser to point back to the NetSuite Sandbox as follows:

    Change:

    system.netsuite.com/app/site/hosting/scriptlet.nl?script=745&deploy=1&web_access_point=https://adobesign.com

    To:

    system.sandbox.netsuite.com/app/site/hosting/scriptlet.nl?script=745&deploy=1&web_access_point=https://adobesign.com

Update the bundle (existing users)

Adobe periodically releases updates to the NetSuite bundle. Existing users of the Adobe Acrobat Sign for NetSuite integration can easily update to the latest bundle.

Caution:

Customers upgrading to a newer version should NOT remove their existing API key.

See Setting custom preferences for more information on how the API key is used.

Before updating the bundle

The amount of time required to update to the v4.0.5 bundle depends on the number of agreements that currently have a status of Out for Signature. Under normal circumstances, it takes 7 – 10 minutes to update 100 agreements. To determine how many Out for Signature agreements that you have, do the following:

Note the number of records to estimate your update time.

  1. Navigate to Customization > Lists, Records, and Files > Record Types, then locate Adobe Acrobat
    Sign Agreement.
    (You can also use Global Search).

  2. Click the Search link to the right.

    view record types

  3. Under Status, select Out for Signature and then select Submit.

    Sent agreements search

    Note the number of records to estimate your update time.

Update the bundle

  1. Navigate to Customization > SuiteBundler > Search & Install > List.

    Locate your current bundle as shown below.

    Note:

    If there is a new version of the bundle, an exclamation point icon displays to the right of the Version number of your current bundle.

  2. From the Action drop-down list, select Update.

    bundle update

  3. On the Preview Bundle Update page, click Update Bundle without changing any of the default values displayed on the page.

    Note: You may get the following warning when updating the bundle. If you have not customized your NetSuite e-signature records, you can proceed. If you are unsure, we suggest that you install the bundle on a Sandbox account to test it before updating the bundle in a production account.

    Error message

    During the update installation process, the status of the bundle displays as Pending.

    To display an updated status, click Refresh.

    pending install

    Note:

    If the update takes a long time because you have many Out for Signature agreements, you can check the Execution Log subtab for the Adobe Acrobat Sign Bundle Installation script to determine the progress of your update.

    See Determining the progress of the update for more information.

    After the bundle update is complete, Adobe Acrobat Sign for NetSuite displays on the Installed Bundles page.

    sign bundle installed

Configure the bundle

Set custom preferences

You can use custom preferences to specify how agreements are created and stored in NetSuite. The Auto Provision User in Adobe Acrobat Sign preference allows you to specify whether NetSuite users are auto-provisioned in Sign services when they send agreements from NetSuite.

  1. Navigate to Setup > Company > General Preferences.

  2. Scroll down the page and select the Custom Preferences subtab.

    setting custom preferences

  3. Enable and configure your Acrobat Sign preferences as needed:

    • Enter EchoSign API Key for Your Account—Do not add or edit any value in this field.
    • Use Parent Record Contact as Signer—If enabled, the parent record contact defaults as the first signer when agreements are created. The sender can remove or edit the default signer or add additional signers to the agreement before sending.
    • Use Trans. Contact as Signer if present— It is valid only if the Use Parent Record Contact as Signer preference is also enabled. If enabled, when generating an agreement from a Transaction Record such as Quote, the primary Transaction contact defaults as the first signer. See Transaction Records for more information. If there is no primary Transaction contact, or if sending from NetSuite object record, such as Customer record or Partner record, the default recipient will be the primary contact for the customer email. The sender can remove or edit the default signer or add additional signers to the agreement before sending.
    • Allow Marking Recipients as Approvers—If enabled, senders can mark recipients as approvers. Recipients marked as approvers can review and approve agreements, but they are not required to sign them. Approvers may be required to enter data into fields during the approval process.
    • Preferred Agreement Folder Id—Used to specify the folder where the final-signed agreements will be stored. If you don’t set a value for this field, final-signed agreements are saved in the same folder as the original document file by default. The Folder Id must be a number.
    • Auto Attach Transaction PDF—If enabled, Transaction PDFs are automatically attached to agreements when new agreements are created from Transaction records.
    • Add Signed PDF as (Attachment or Link)—If List is selected from the drop-down, the Signed PDF is automatically added as a link to the file. If Attachment is selected from the drop-down, the signed PDF is stored in NetSuite as an attachment on the Agreement record.
    • Include Audit Trail PDF with Agreement—If enabled, audit trail PDFs are automatically attached to Agreement records after the agreements are signed.
    • Identity Verification Method Applies to— It allows you to apply the identity verification methods to selective recipients. The options are All Signers, External Signers Only, or Internal Signers Only.
    • Enabled identity verification methods can be selected when creating an agreement. If more than one identity verification method is enabled here, a Verify Signer Identity option displays on the Adobe Acrobat Sign Agreement page.

    ► Enable Password Required to Sign—Require signers to enter a one-time password you specify.

    ► Enable Knowledge Based Authentication—Require signers to provide their name, address, and optionally the last four digits of their SSN and then answer a list of questions verifying the information that they provided. Available only in the United States.

    ► Enable Web Identity Authentication—Require signers to verify their identity by signing in to one of the following sites: Facebook, Google, LinkedIn, Microsoft Live, Twitter, or Yahoo!.

    • Auto Provision User in Adobe Acrobat Sign—If enabled, users who send agreements in NetSuite are automatically auto-provisioned with an Adobe Acrobat Sign user account.
  4. To save your preferences, select Save at the top or bottom of the page.

Configure automatic status updates

The Adobe Acrobat Sign integration bundle allows you to automatically receive updates in NetSuite regarding the status of the agreements that have been sent from NetSuite. When this feature is enabled, NetSuite always reflects the status of your agreements. You can enable automatic status updates as follows:

  1. Navigate to Setup > Company > Enable Features.

  2. Select the SuiteCloud subtab.

  3. Enable the following options:

    • In the SuiteBuilder section, enable Custom Records option.
    • In the SuiteScript section, enable the Client SuiteScript and Server SuiteScript options and agree to the terms of service for both.
  4. Click Save.

    Your options should be set as shown in the image below:

    enable features

Objects and record types

The Adobe Acrobat Sign integration bundle exposes the Acrobat Sign Agreement object with many standard NetSuite objects including: Customer, Estimate, Lead, Opportunity, and Partner records. You can use the Adobe Acrobat Sign bundle with other record types as well, including custom records.

The Agreement tab can appear with two types of NetSuite records: Entity and Transaction records. For our purpose we can usually assume that a Transaction record is a record that can be converted into a PDF document— for example, a Quote—whereas an Entity record cannot.

Transaction records

If the agreement is created from a Transaction record, the first document on the agreement record will be the PDF version of the record it came from and the first recipient will be the email address of the record. If you don’t want the first document to be a PDF version of the record it came from, disable the Auto Attach Transaction PDF option under Setup > Company > General Preferences > Custom Preferences subtab (See Setting Custom Preferences for more information.)

Under Custom Preferences, you can also enable the Use Trans. Contact as First Signer preference if you want the primary transaction contact to be added automatically as the first signer.

When associated with a Transaction record, both the Agreements tab and a Send for Signature button display.

quote send for sign

Entity records

If the agreement is created from an Entity record the first recipient will be the email address from the record. When associated with an Entity record, only the Agreements tab displays.

Customize the bundle

To customize the bundle, you must:

  • Deploy the scripts for the Agreements subtab and the Send for Signature button for the appropriate record types.
  • Set role permissions for your Adobe Acrobat Sign record types.
  • Modify permissions to grant access to the Agreements subtab and the Send for Signature button.

Configure Adobe Acrobat Sign agreements for other record types

To deploy the Agreements subtab and the Send for Signature button for the appropriate record types, follow the steps below.

  1. Navigate to Customization > Scripting > Scripts.

    The Scripts list page displays.

    view new scripts

  2. On the Scripts list page, locate the script you must deploy and then select View.

    • To add the Send for Signature button, select the Adobe Acrobat Sign Estimate Button script.
    • To add the Agreements tab, select the Adobe Acrobat Sign Agreement Loader script.
  3. On the Script page, select Deploy Script.

    script deploy

  4. On the Script Deployment page, do the following:

    • From the Applies To list, select the type of record.
    • Optionally, enter script deployment ID. (See the Creating a Custom Script Deployment ID topic in the NetSuite Help Center for more information.) If you do not enter an ID, one is generated.
    • Check the Deployed check box.
    edit script deployment

    • Set Status to Released.
      • You do not need to specify an Event Type or Log Level.
    • From the Execute As Role drop-down, select Execute as Admin.
    • With the Audience subtab active (it is active by default), select the specific roles or users that you want to grant access to. If you want to grant access to all roles and users, enable the respective Select all options.
    • Click Save. When the change confirmation displays, click Go Back.
  5. From the top of the Script Deployment page, select List.

    It takes you back to the Scripts list page.

  6. Repeat steps 2 and 3 above for the other script.

Set role permissions for Adobe Acrobat Sign record types

Most NetSuite roles should have permission to use Adobe Acrobat Sign without additional customization. However, you may must grant permissions for any additional custom roles that have been created.

  1. Navigate to Customization > Lists, Records, & Files > Records Types.

    SiteBuilder - Custom Records

    Note:

    If you do not see the Record Types item, navigate to Setup > Company > Enable Features > Suite Cloud tab and enable the Custom Records option.

  2. On the Record Types page, click Adobe Acrobat Sign Agreement to select it.

    Record Types list

  3. On the Custom Record Type page, select Use Permission List from the Access Type drop-down.

    custom record type

    Note:

    The Adobe Acrobat Sign Agreement record type is the only Adobe Acrobat Sign record type that required the Uses Permission List access type.

    See step 6 for instructions on setting the access type for the other Adobe Acrobat Sign record types.

  4. Select the Permissions subtab.

    It displays the list of roles and permissions.

    custom record types permissions

  5. Set permissions as follows for the additional custom roles added to the “Adobe Acrobat Sign Agreement” record type:

    1. Select the role from the Role list.
    2. Set Level to Full.
    3. Set Default Form to Custom Adobe Acrobat Sign Agreement Form.
    4. Select the Restrict Form check box.
    5. To save the changes for the role row, select Add.
    6. Repeat steps 1 to 5 above for all additional custom roles.
    7. When permissions for all roles are set, select Save on the Custom Record Type page The Customer Record Type page redisplays.
    Note:

    See the Setting Up a Permissions List for a Custom Record Type topic in the NetSuite Help Center for more information.

    custom record type permissions

  6. Repeat steps 1 – 3 above to set the Access Type for all the other Adobe Acrobat Sign record types to.

    No Permission Required. This applies to following record types:

    • Adobe Acrobat Sign Config
    • Adobe Acrobat Sign Document
    • Adobe Acrobat Sign Event
    • Adobe Acrobat Sign Language
    • Adobe Acrobat Sign Script Errors
    • Adobe Acrobat Sign Signed Agreement
    • Adobe Acrobat Sign Signer

Grant access to the Agreement tab and Send For Signature button

The Adobe Acrobat Sign integration bundle already exposes the Adobe Acrobat Sign Agreement object with many standard NetSuite objects (Customer, Estimate [Quote], Lead, and so on). The Agreement subtab is automatically enabled for the following types of objects: Customer, Lead, Opportunity, Partner, Prospect, Quote, and Vendor Bill.

The Send for Signature button is automatically enabled only for the Quote object.

NetSuite administrators can extend the ability to create agreements to other CRM objects by modifying permissions to add the Agreement subtab, Send for Signature button, or both to those objects.

Modify permissions to grant access to the Send for Signature button

  1. Navigate to Customization > Scripting > Scripts.

    The Scripts list page displays.

    • If necessary, use the filters to locate the Adobe Acrobat Sign scripts.
  2. On the Scripts page, locate the Adobe Acrobat Sign Estimate Button script (controls the Send for Signature button), then click View.

    View Scripts

  3. On the Script page:

    1. Select the Deployments subtab.
    2. Under “Applies to”, select the link for the entity that you want to modify [Quote in this example].
    3. On the Script Deployment page, select Edit.
    4. With the Audience subtab active, select the specific roles or users that you want to grant access to. 
    5. To grant access to all roles and users, enable the respective Select all options.
    6. Select Save.
    Script Deployments

    edit script deployment

    script deployment audience

Modify permissions to grant access to the Agreements tab

  1. Navigate to Customization > Scripting > Scripts

  2. On the Scripts page, locate the Adobe Acrobat Sign Agreement Loader script and select View.

  3. On the Script page, do the following:

    1. Select the Deployments subtab
    2. Under “Applies to” click the link for the entity that you want to modify access for.
    3. On the Script Deployment page, select Edit.
    4. With the Audience subtab active (it is active by default), select the specific roles or users that you want to grant access to. 
    5. To grant access to all roles and users, enable the respective Select all options.
    6. Select Save.

Send agreements using Acrobat Sign for NetSuite bundle

To send agreements from NetSuite and receive updates on those agreements, users must have the same login ID (email address) in NetSuite and in Adobe Acrobat Sign.

Creat an Adobe Acrobat Sign agreement

After installing a new bundle in a Sandbox or Production account, you should test the bundle by creating an agreement. You can create Adobe Acrobat Sign agreements from an entity record, from a transaction record, or as a stand-alone agreement.

Note:

The process for creating an agreement differs slightly depending on how it is created. The general process involves specifying the options for your agreement, adding one or more agreement documents, and specifying the recipients. The process described below assumes that you are creating the agreement form a customer record.

  1. Select or create a customer record you would like to send an agreement from, or you can select another NetSuite record type that has the Agreements tab enabled.

  2. Select New Agreement.

    customer new agreement

  3. On the Adobe Acrobat Sign Agreement page, select Edit.

    edit agreement

  4. Specify the options for your agreement as follows:

    • Agreement Name—Enter a name for the agreement.
    • Message—Enter a custom message for the recipient.
    • Signature Type—Select the type of signature accepted for the document. The options are e-signature and Fax Signature.
    • I Also Need to Sign This Agreement—Enable this option to indicate that the sender also must sign the agreement.
    • Signature Order—If the I Also Need to Sign This Agreement option is enabled, select the order the sender and recipients should sign. The options are “I sign, then recipients sign”, “Recipients sign, then I sign” and “None”.
    • Preview Document or Position Signatures (or form fields)—Enable this option to allow senders to preview the agreement and to allow them to add fields (drag-and-drop signature, initial fields, and other form fields) to the agreement before it is sent to recipients.
    • Verify Signer Identity—Enable this option, then select one of the following identity verification options:
      • Password Required to Sign: Require Signers to enter a one-time password you specify.
      • Knowledge-Based Authentication: Require signers to provide their name, address, and optionally the last four digits of their SSN and then answer a list of questions verifying the information they provided. Available only in the United States.
      • Web Identity Authentication: Require signers to verify their identity by signing in to one of the following sites: Facebook, Google, LinkedIn, Twitter, Yahoo!, or Microsoft Live.
    • Password Required To View PDF—Enable this option to require that a recipient enter a password before opening a PDF of the agreement or the signed agreement. The PDF file sent to everyone will be encrypted, and this password will be required to open it. Don't lose your password, as it's not recoverable. If you lose the password, you must delete that transaction and begin again.
    • Password/Confirm Password—If the Password Required To View PDF option is enabled, enter the password that should be used to view the agreement.
    • Remind Recipients to Sign—Specify if and how often reminders are sent to recipients. The options are Never, Daily, or Weekly.
    • Language—Specify how the signing page and email notifications will be displayed to the recipients.
    • Host Signing for the First Signer—Enable this option to allow the sender host in-person signing for the first signer.

    Note: KBA, Adobe Sign, and Phone authentication require you to turn on 3rd party cookies in your browser.

    • Days Until Signing Deadline—Enter a whole number to indicate the signing deadline for the agreement (Today’s date + number of days).
    • Parent Record—Optionally, select a parent record to link it to the agreement.
    edit agreement details

  5. Select the Documents tab.

    add document to agreement

  6. On the Documents subtab, attach an existing document from the file cabinet using the Adobe Acrobat Sign Document drop-down and clicking Attach.

    Or, upload a new document by clicking on the New Adobe Acrobat Sign Document button to access the Adobe Acrobat Sign Document page (shown below) where you can type the name of a document in your NetSuite file cabinet, select files from your Transaction record (if applicable), or attach a new document.

    You can add multiple documents to an agreement.

  7. Click the Recipients subtab and enter the following details:

    • Specify the recipient by either selecting from the contact list or typing an email address.
    • Assign one of the following roles to each recipient:
      • Signers must sign the agreement.
      • Approvers must approve, but not sign the agreement, and may optionally add data to an agreement.
      • CC'd Recipients are notified of agreement updates and when the agreement is signed and completed. CC recipients are not a party to the signature or approval process.

    See Setting custom preferences for more information.

    • If the Use Parent Record Contact as Signer custom preference is enabled alone or with the Use Trans. Contact as Signer preference, the first recipient is defaulted, but can be changed.
    • After entering each recipient, select Add.
    add recipient to agreement

  8. To save the agreement, select Save.

Send agreements for signature

When the agreement is ready to be sent, click the Send for Signature button.

  • If the Preview document or position signatures option is enabled, clicking the Send for Signature button opens a pop-up window that allows the sender to preview the document or drag form fields on to the document before it is sent. Remember to click the Send button in that window to send the agreement to the recipient.
  • If the Host Signing for First Signer option is enabled, clicking the Send for Signature button opens a pop-up window to allow the signer to sign the document with the sender present.
    • A Host Signing for Current Signer link also appears next to the Host Signing for First Signer field, which can be accessed until the document is signed. Use this link to host agreement signing for multiple signers, or to reopen the pop-up window if it accidentally closed.

Once the agreement is sent, recipients receive an email informing them of the documents awaiting their signature.

After the recipients have signed the document, the sender receives a notification by email that the document has been signed.


Send Agreement from a quote

Adobe Acrobat Sign has a direct integration with Quotes in NetSuite so that a PDF of the quote is automatically generated and attached to the agreement record.

When viewing a Quote, click the Send for Signature button. The quote will be generated and automatically attached to the agreement. You can also add the Send for Signature button to other transaction record types. (See Objects and record types for more information.)

quote send for signature


Track status and send reminders

After you send an agreement:

  • The document status changes to Out for Signature in the Agreement details section
  • The Send for Signature button is replaced by the Update Status, Cancel Agreement, and Send Reminder buttons, which function as follows:
    • Update Status—Click this button to manually update the status if status updates have not been configured. (See Configuring automatic status updates for more information.)
    • Send Reminder—Click this button to send a reminder to the current signer.
    • Cancel Agreement—Click this button to cancel an agreement. An agreement may be canceled after it has been sent for a signature if all recipients have not yet signed.

A new Events subtab displays in the agreement record where you can track the agreement’s status.

You can see a history of the agreement events, which includes information about when the agreement was sent, viewed, and signed.

sent agreement status

After the agreement is signed:

  • Its status changes to Signed.
  • You can link back to the Parent Record for this agreement using the link.
  • You can use the “download” links under Signed Document and Audit Trail to access these documents.
  • An additional Signed Document subtab displays to view thumbnails of the signed document.
signed-agreement-status

Note:

After an agreement has been sent for signature, you will not be able to edit the record. This is to preserve the record of events.

Uninstall the Bundle

To uninstall the bundle, follow the steps provided in the NetSuite Help. (See the Uninstalling a Bundle topic in the NetSuite Help Center for more information.)

Please note that if you uninstall the bundle, unsigned agreements will be deleted.

Signed agreements and their corresponding audit PDF files will not be affected.

Do NOT uninstall the bundle if you must retain your unsigned agreements.

Troubleshoot

Determine the progress of the update

If the update appears to be taking longer than, you can check the Execution Log subtab for the Adobe Acrobat Sign Bundle Installation script to determine the progress of your update as follows:

  1. Navigate to Customization > Scripting > Scripts.

  2. On the Scripts page, locate the Adobe Acrobat Sign Bundle Installation script then click Edit.

  3. On the Script page, click to select the Execution Log subtab.

  4. Click Refresh.

    The Execution Log updates to reflect the status. The Details column displays the progress of the updates to your agreements.

    script execution log refresh

Resolve access token issues

Users may encounter an “Access token provided is invalid or has expired” message when interacting with agreements.

This may occur for the following reasons:

  • The NetSuite/Adobe Acrobat Sign administrator who configured OAuth has revoked the access token.
  • The access token has expired because no agreements have been sent from NetSuite in the past 60 days.
  • The NetSuite/Adobe Acrobat Sign administrator has not successfully completed the initial OAuth configuration.

You can easily resolve this issue by executing the OAuth configuration process again. See Configuring OAuth after installing or upgrading for more information.

access-token-invalid

Resolve document status issues

If automatic status updates have been configured, but agreement status is not updating after sending agreements, try the following:

  1. Check the deployment execution log for the Adobe Acrobat Sign External Update script to see if you are receiving calls from Adobe Acrobat Sign as follows:

    1. Navigate to Customization > Scripting > Script Deployments.
    2. On the Script Deployments page, locate the Adobe Acrobat Sign External Update script, then click Edit.
    3. On the Script Deployment page, click to select the Execution Log subtab.
      • You should see an Updated Agreement Record entry for each agreement ID.
  2. Check the deployment execution log for the Adobe Acrobat Sign Update Agreements script to see if there are any errors as follows:

    1. Navigate to Customization > Scripting > Script Deployments.
    2. On the Script Deployments page, locate the Adobe Acrobat Sign Update Agreements script with the “Scheduled” status, then click Edit.
    3. On the Script Deployment page, click to select the Execution Log subtab
    4. Under Type, select Error to filter the results.
  3. Lastly, check the execution log for the Adobe Acrobat Sign Manager script for errors by following the instructions in step 2 above.

Resolve MIME type errors

If you are receiving a MIME type error when attempting to send an agreement, this may be because the name in the filename field does not match the filename and extension of the uploaded file. If you leave the filename field blank, it will automatically be populated with the correct filename and extension.

View script logs

You can also view the deployment execution logs for scripts that are not related to document status issues. (See Resolving document status issues for more information.)

1.         Navigate to Customization > Scripting > Scripts. The Scripts list page displays. If necessary, use the filters to locate the appropriate script.

2.        Select View for the corresponding script.

3.       Click to select the Execution Log subtab on the page to display the script log.

Support

Go to the Adobe Support portal to access FAQs, documentation, knowledge base articles, and contact Adobe Support: https://helpx.adobe.com/sign/user-guide.html

Get help faster and easier

New user?