Navigate to Customization > SuiteBundler > Search & Install Bundles.
Adobe Acrobat Sign for NetSuite provides a complete e-signature integration with NetSuite. You can use Acrobat Sign for NetSuite to send agreement such as contracts, quotes, and other documents to recipients directly from NetSuite. You can create and send Adobe Acrobat Sign agreements from customer, lead, quote, 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.
Refer to the Adobe Acrobat Sign for NetSuite release notes for more information.
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, we recommend installing and testing the bundle in a NetSuite Sandbox account.
See Creating an Adobe Acrobat Sign agreement for more information about testing.
Customers upgrading to v4.0.7 should NOT remove their existing API key.
See Setting custom preferences for more information on how the API key is used.
Navigate to Customization > SuiteBundler > Search & Install Bundles.
On the Search & Install Bundles page, Search for Adobe Acrobat Sign.
Select the Adobe Acrobat Sign bundle name.
On the Bundle Details page, select Install.
In the Preview Bundle Install page, click Install Bundle.
There is no need to change any of the default values on the page.
In the install dialog that appears, select OK.
During installation, the status of the bundle is shown as Pending.
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.
If you are already an Adobe Acrobat Sign customer, proceed to Configuring OAuth after installing or upgrading.
If you do not have an Adobe Acrobat Sign account, you can sign up for an enterprise trial account to test the system.
If you have an Adobe Acrobat Sign account, proceed to Configuring OAuth after installing or upgrading. Else, sign up for an enterprise trial account to test the system and follow the online registration steps to enable your Adobe Acrobat Sign account.
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.
In NetSuite, navigate to the Adobe Acrobat Sign Config list page:
On the Adobe Acrobat Sign Config List page, click View to the left of Using OAuth to Access Adobe Sign APIs.
On the Adobe Acrobat Sign Config page, select Login In With Adobe Acrobat Sign.
When the AdobeAcrobat Sign login page displays, enter your credentials.
In the Confirm Access page (for OAuth) that displays, select Allow Access.
When the authorization is complete, you are redirected back to Adobe Acrobat Sign Config page in NetSuite as shown below:
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
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.
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.
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.
Navigate to Customization > Lists, Records, and Files > Record Types, then locate Adobe Acrobat
Sign Agreement. (You can also use Global Search).
Click the Search link to the right.
Under Status, select Out for Signature and then select Submit.
Note the number of records to estimate your update time.
Navigate to Customization > SuiteBundler > Search & Install > List.
Locate your current bundle as shown below.
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.
From the Action drop-down list, select Update.
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.
During the update installation process, the status of the bundle displays as Pending.
To display an updated status, click Refresh.
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.
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.
Navigate to Setup > Company > General Preferences.
Scroll down the page, then click to select the Custom Preferences subtab.
Enable and configure your Acrobat Sign preferences as needed:
► 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!.
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:
Navigate to Setup > Company > Enable Features.
Click to select the SuiteCloud subtab.
Enable the following options:
Click Save.
Your options should be set as shown in the image below:
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.
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.
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.
Customizing the bundle includes the following:
To deploy the Agreements subtab and the Send for Signature button for the appropriate record types, follow the steps below.
Navigate to Customization > Scripting > Scripts.
The Scripts list page displays.
On the Scripts list page, locate the script you must deploy, then click View.
On the Script page, click the Deploy Script Button.
On the Script Deployment page, do the following:
Click List at the top of the Script Deployment page to get back to the Scripts list page.
Repeat steps 2 and 3 above for the other script.
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.
Navigate to Customization > Lists, Records, & Files > Records Types.
If you do not see the Record Types item, navigate to Setup > Company > Enable Features > Suite Cloud tab and enable the Custom Records option.
On the Record Types page, click Adobe Acrobat Sign Agreement to select it.
On the Custom Record Type page, select Use Permission List from the Access Type drop-down.
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.
Click to select the Permissions subtab.
The list of roles and permissions displays.
Set permissions as follows for the additional custom roles added to the “Adobe Acrobat Sign Agreement” record type.
See the Setting Up a Permissions List for a Custom Record Type topic in the NetSuite Help Center for more information.
Repeat above steps for all additional custom roles.
The Customer Record Type page displays again.
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:
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.
Navigate to Customization > Scripting > Scripts.
The Scripts list page displays.
On the Scripts page, locate the Adobe Acrobat Sign Estimate Button script (controls the Send for Signature button), then click View.
On the Script page, do the following:
Navigate to Customization > Scripting > Scripts
On the Scripts page, locate the Adobe Acrobat Sign Agreement Loader script and select View.
On the Script page, do the following:
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.
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.
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.
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.
Click New Agreement.
On the Adobe Acrobat Sign Agreement page, click Edit.
Specify the options for your agreement as follows:
► 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 that 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.
Click the Documents tab.
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.
Click the Recipients subtab to specify recipient by either selecting from the contact list or typing an email address.
Each of your recipients can be marked as Signer or CC. If the Allow Marking Recipients as Approvers Signers custom preference is enabled, recipients can also be marked as Approvers. (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.
Click Add after entering each recipient.
Click Save to save the agreement.
When the agreement is ready to be sent, click the Send for Signature button.
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.
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.)
After you send an agreement:
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.
After the agreement is signed:
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.
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.
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:
Navigate to Customization > Scripting > Scripts.
On the Scripts page, locate the Adobe Acrobat Sign Bundle Installation script then click Edit.
On the Script page, click to select the Execution Log subtab.
Click Refresh.
The Execution Log updates to reflect the status. The Details column displays the progress of the updates to your agreements.
Users may encounter an “Access token provided is invalid or has expired” message when interacting with agreements.
This may occur for the following reasons:
You can easily resolve this issue by executing the OAuth configuration process again. See Configuring OAuth after installing or upgrading for more information.
If automatic status updates have been configured, but agreement status is not updating after sending agreements, try the following:
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:
Check the deployment execution log for the Adobe Acrobat Sign Update Agreements script to see if there are any errors as follows:
Lastly, check the execution log for the Adobe Acrobat Sign Manager script for errors by following the instructions in step 2 above.
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.
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.
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
Sign in to your account