The workflow reads the customer and its contact from NetSuite and fills the credit application, which the customer completes and signs and the credit manager who started the workflow countersigns. It then writes the confirmed email back to the customer and files the signed application on the customer record.
| Data label on the credit application | NetSuite field | Step |
|---|---|---|
Customer_Company | Customer / Company Name | 1 |
Customer_Number | Start input Customer_ID | Start |
Bill_To_Street | Customer / Default Billing Address 1 | 1 |
Bill_To_City | Customer / Default Billing City, State and Zip | 1 |
Customer_Phone | Customer / Phone | 1 |
Payment_Terms | Customer / Terms Name | 1 |
Current_Credit_Limit | Customer / Credit Limit | 1 |
Sales_Rep | Customer / Sales Rep Name | 1 |
Contact_Name | Contact / Contact Name | 2 |
Written back: Email = Customer_Email, as the customer confirmed it; A custom Customer field = Contact / Contact Name
Filed to: Customer drive / {Customer Record ID} / Signed Credit Application - {Company Name} - {Instance ID}.pdf
The highlighted fields are the credit application's data labels, shown here with sample values. The field map lists where each one comes from in NetSuite or the start inputs. Each field sits on a hidden anchor tag, so you can use your own credit application: keep the nine data labels and the workflow keeps working.
Install NetSuite for Docusign IAM from the Docusign App Center and connect it to your NetSuite account. An account admin does this once.
In Docusign, upload the credit application template (.json) under Templates. It carries the document and its fields.
In Agreements, Workflows, Create Workflow, add the steps listed above in order. Use the definition file to check the settings of each step, pick your NetSuite connection, and map the fields as the field map shows.
Run it once on a test record addressed to your own inbox, and check the write-back and the file.
No. It is the definition exported from the tested workflow, kept as a reference. Build the workflow step by step in Docusign Workflow Builder and use the file to check the settings of each step. The account, connection and template ids in it are placeholders.
An account manager or the credit team, on the NetSuite customer with Baton Launcher, or anyone with Run Workflow and the customer's internal ID. Another system can start it through the API with Customer_ID.
The accounts payable email the customer confirmed goes to the customer's Email, and the contact's name goes to a custom Customer field. The decision and the approved limit stay on the signed application unless you map them to fields of your own.
No. Honeycomb Mfg. is a fictional company and every sample value is invented. Put your own company, terms and template in place before you use the workflow.
We adapt library workflows to your stages, approvals and documents, and build private apps when a system has no app yet.
Fills an order form from the quote, its customer and contact, collects both signatures and files the signed copy on the quote.
Fills an onboarding packet from the employee record, collects the new hire's details and signature, and writes their phones back.
Fills a supplier agreement from the vendor, collects the legal name, tax ID and both signatures, and updates the vendor.
Docusign is a trademark of Docusign, Inc. NetSuite for Docusign IAM is published by Fluidlabs. To ask us to remove a mark, email hello@fluidlabs.com.
