E-Sign Order Forms with DocuSign

the nue docusign integration is now available as a preview feature this integration connects your nue order forms with docusign so that customers and internal stakeholders can review and sign documents electronically, directly from your nue workflows during the preview functionality focuses on order forms going through docusign admin configuration, template based e signature components, and sending order forms for e signature are supported we may introduce breaking changes and add additional capabilities, including support for other e signature components in the future if you’re interested in joining the preview, please contact your nue representative or customer success manager overview the docusign integration for nue order forms enables your team to generate, send, and track electronically signed order documents directly from nue so deals move from quote to signature without manual handoffs or switching between tools with the integration enabled, your sales and revops teams can design reusable, docusign ready order form templates; send documents for e signature in just a few clicks; automatically route envelopes to the correct internal and external recipients; and deliver a polished, compliant signing experience for customers overall, this integration turns nue into a single, streamlined workspace for quoting and signing, reducing manual steps, shortening sales cycles, and creating a smoother, fully digital contract process for your team and your buyers the docusign integration lets you connect nue to your docusign account using oauth and an integration key add e signature components (signature, initial, date signed, full name) to the order form in the nue template builder generate pdfs with e signature components so docusign can place signature fields automatically in your order forms send order forms for e signature from the quote detail page to both internal approvers and external customers docusign licenses to use nue’s native docusign integration, you’ll need a docusign account that includes api access for example, a docusign api plan or an enterprise esignature plan with api capabilities all envelopes sent from nue are routed through a single api enabled docusign integration user within your docusign account this means you do not need to purchase individual docusign seats for each sales rep additionally, your internal and external signers do not need docusign licenses recipients will simply receive a docusign email request and can complete their signature directly in their browser docusign pricing for api use is primarily based on the number of envelopes you send via the api we recommend selecting an api plan tier that aligns with your expected monthly envelope volume to confirm the correct sku or plan, please consult your docusign representative for more detailed technical information, you can also refer to docusign’s developer documentation configuration this section is for administrators to configure the docusign integration in nue prerequisites before configuring the integration, ensure you have a docusign account with permissions to create apps and manage connect settings create a new app in your docusign account and generate a secret key add the following uri in the app under redirect uris sandbox https //app sandbox nue io/e signature/docusign/callback production https //app sandbox nue io/e signature/docusign/callback enable docusign integration in nue grant permission to manage the integration go to nue system settings → user roles under the integration section, enable the “manage docusign integration” permission for the system administrator role activate the docusign integration in system settings → integrations → docusign integration , populate the docusign integration key and secret key select the production environment click the activate button to enable the integration set up the order form template with e signature components this step lets you place e signature components in your order form templates navigate to the order form list and open the order form template you use to generate your customer facing pdfs in the template builder, add e signature components to the template currently, the following e sign components are supported signature enables the recipient to sign a document initial enables the recipient to initial the document date signed displays the date that the recipient signed the document full name displays the recipient's full name text enables the recipient to provide additional information title displays the recipient's job title for each e sign component, you can configure the following attributes tag a unique identifier used to associate this component with a specific recipient (e g , “customer”, “internal user”) signing order indicate when the recipient is allowed to receive and sign the document by default, it is set to 1 required indicate whether this field must be completed before the e sign process can be completed description a tooltip describing the field in docusign’s signing ui send for e signature once the order form template is configured with e sign components, on the quote detail page, sales reps can send the order form to external and internal signers by clicking the “send for e signature” button after clicking send for e signature , a guided flow opens step 1 – select a document if the order form pdfs already exist in the quote’s attachments, the system defaults to “select a pdf file from the attachments” and preselects the latest pdf if there are no existing pdfs, nue defaults to “select a template to generate a new pdf file” and chooses the latest published template you can change both the choice and selection as needed step 2 – configure recipients nue automatically generates required recipients based on the signature components configured in the pdf/template for each required recipient, sales reps can select from the account's contacts and salesforce users, or specify the name and email directly the default signing order for each recipient can be configured in the order form template by default, all recipients are set to parallel signing (order 1); however, sales representatives can configure strict sequential or mixed (parallel + sequential) workflows by assigning custom signing order numbers they can also add more recipients to receive a copy or as reviewers additionally, sales reps can customize the email subject and message that is sent to the signers sign order form after clicking the 'send' button at step 2 in the guided flow, recipients will receive an email from docusign, and they can sign the order form through docusign's e sign process signing history the signing history feature lets sales reps quickly see the full signing journey for each quote pdf directly from the quote detail page this helps them track progress, follow up with customers, and keep a clean audit trail for every document you send for e‑signature configure layout to display the signing history on the quote detail page, administrators can follow the steps below go to the quote detail page in salesforce click 'edit page' from the 'setup' menu in the lightning app builder, add the custom component 'quote pdf viewer' to the page save the changes the signing history will be shown under each generated file users can click "show history" or "hide history" to expand/collapse the timeline document status for each generated pdf file, nue tracks key events in the signing process and shows them as a timeline of bullet points, including created pdf file was generated sent document was sent for e‑signature opened the recipient opened the document completed all required signers have signed declined a recipient declined to sign corrected the e signature process was corrected (e g , recipient info updated) canceled the e signature process was canceled behind the scenes, each time an action occurs, the latest version of the file is uploaded, replacing the existing version when downloading the file, users will always receive the latest version edit e signature process nue allows sales reps to fix recipient details (name, email, role, signing order) for an order form that has already been sent for e‑signature via docusign this avoids canceling and restarting the entire signing process when a typo or wrong recipient is discovered after sending once the e‑signature process starts, the 'edit' button will be available when clicking the button, users can correct the information of the recipients who haven't completed the signing action in addition, users can update the email subject and email message for the envelope if they want to clarify the change or add additional instructions after clicking "save and send", nue will call docusign’s correct envelope api and update the existing envelope with the changes, rather than creating a new one please note that the e signature process can only be corrected while it is in sent or opened status once it is in completed, declined, or canceled status, further corrections are not allowed cancel e signature process sales reps can also cancel the e signature process for an order form if the wrong pdf was sent or if the quote terms have changed after canceling, they can generate a corrected pdf and initiate a new signing request however, they can cancel the e signature process only while it is still in progress when canceling an e signature process, a reason is required once users confirm the cancellation, nue will call docusign’s void envelope api to void the in‑progress envelope, and the signing process stops for all remaining recipients recipients who have already signed or are still in the routing order will receive an email notification from docusign informing them that the envelope has been voided, along with the reason please note that a canceled process cannot be resumed if you still require signatures, you must send a new e signature request upload new pdf version sometimes, customers prefer wet signatures over e signatures nue enables sales reps to upload manually signed order forms to the quote, ensuring a complete digital record and signing history—even when customers sign offline to enable manual uploads for new versions, administrators can navigate to nue system settings → lifecycle manager → order forms → general settings and turn on the option “ allow uploading new versions of the order form manually ” on the quote detail page, sales representatives with the appropriate permissions should be able to see the 'upload' button for the generated pdf file in the quote pdf list upon clicking the button, they will see a pop up window with the following options file chooser select the file that will be uploaded (e g , a signed document file received from the customer) notes (optional) add context such as “signed by customer via wet signature ” mark as completed (optional) if checked, the document’s status will move to completed after upload after clicking "yes," the new file is stored as the latest version of the order form, and the additional history item will be automatically added to the quote’s signing history please note that only files with created, completed, declined, or canceled statuses are permitted for a newly uploaded version users cannot upload a new version during a signing convert and download word nue supports the conversion of an order form pdf file to a word type document this feature is limited and not available by default in the tenant if you would like to try or enable this feature, please contact the nue support team with this feature, sales representatives can download an order form as a word ( docx) file directly from the quote, making it easier to redline, edit, or share documents with customers who prefer word over pdf, or to send the word documents to any external systems once the feature is enabled, administrators can go to nue system settings → lifecycle manager → order forms → general settings , and turn on “ allow downloading the order form as a word document ” on the quote detail page, sales representatives with the appropriate permissions should be able to see a new button labeled 'convert to word' for the generated pdf file in the quote pdf list when clicking the button, the system will convert the latest pdf file to a word version and download the docx file directly to the browser permissions administrators can control which users are permitted to perform specific actions on quote pdfs during the docusign esignature process (for example, who can cancel an esignature process or download the document) permissions are managed through custom permissions, allowing customers to align capabilities with their internal policies and approval workflows each action icon in the quote pdf file list is controlled by a dedicated custom permission to grant these permissions to a specific user, go to the permission set assigned to that user and add the custom permissions accordingly action action custom permission custom permission convert to word download order form as word document cancel cancel e signature request edit edit e signature envelope download download order forms upload signed document upload signed order forms system settings admins can configure the following general settings in nue system settings → integrations → docusign integration based on their business needs use only the default quote pdf or template for sending documents for e signature when this setting is enabled, nue enforces the use of a default quote pdf or template for e signature processes sales reps are no longer presented with the option to manually select a template or pdf while sending documents for e signature instead, the system automatically chooses the appropriate document according to a strict priority order the latest generated pdf, the quote level default template, the entity level default template, or the system default template allow multiple active e signature requests per quote by default, sales reps cannot send the same quote for e signature more than once while another signing request is active nue enforces a strict rule to ensure that only one active e signature request can exist per quote at any given time if businesses allow their sales reps to initiate multiple e signature processes simultaneously, they can enable this setting recipient options when sending a quote for e signature, sales reps can select a user or contact as the signer, add the recipient by their name and email, or choose from a predefined list of recipients administrators can manage the available options by selecting the relevant checkboxes for more details regarding 'predefined recipients,' please refer to docid\ i2uoxjkirteiel rez4ua email subject and message administrators can set the organization level default email subject and message, which will be utilized for e signature email notifications additionally, they can configure the default email subject and message at the quote level when a quote is sent for e signature, sales representatives will observe the default email subject and message automatically populated in the e sign flow, with the flexibility to modify it as needed configure default recipients use default recipients to automatically populate common signers, viewers, and copy recipients when sales reps send order forms for e‑signature this reduces manual data entry and helps ensure the right people always receive the document how default recipients work when a sales rep opens the send for e‑signature flow and reaches step 2 – configure recipients nue looks at the e‑signature components and tags in the order form template to determine how many recipients are required for each required recipient, nue searches the recipient records in salesforce and auto‑fills matching recipients based on tag – matches the tag on the signature component in the template action matches the action of the added recipient account – when a recipient is configured for a specific account if more than one record matches the same tag and account, nue uses the latest match (last modified) as the default sales reps can still change any pre‑filled recipient and add more recipients (for example, to receive a copy) before sending create default recipients in salesforce, go to the recipients tab for the recipient object click new and fill in the following fields name – name of this default recipient email email address of this default recipient tag – a text value that links this recipient to a specific e‑signature component in the template the tag must match the tag configured on the e‑signature component in your order form template for signers (for example, customer, sales manager) action – indicates what this person does in the envelope, usually needs to sign for signers, and needs to view or receives a copy for additional recipients role optional role of this default recipient account – optional use this if the recipient is specific to one account, such as that account’s primary signer if empty, the same recipient can be reused across all accounts contact or user – optional link the recipient to a salesforce contact or user when linked, the contact's or user's name and email are used instead of the values stored on the recipient record itself, so changes to the user or contact are automatically reflected save the record repeat for each common signer or viewer you want to default (for example, customer signer , sales manager , legal reviewer ) test the configuration by opening a quote in salesforce, clicking send for e‑signature , and confirming that required recipients are automatically populated based on your recipient records nue does not create or update recipient records for you customers typically manage these records through salesforce ui, flows, or triggers based on their own business rules predefined recipients the predefined recipients feature lets system admins control which recipients are available during the docusign e‑signature flow you can customize the predefined recipients from the recipient object or through a registered recipientselectionplugin , ensuring that sales reps always pick from the right people for each quote or customer configure recipient options navigate to nue system settings → integration → docusign integration locate the recipient options section check the option predefined recipients use predefined recipients in the e‑signature flow when predefined recipients is enabled in settings, users can choose recipients from a curated list for different recipients (e g , customer or internal user) during the e‑signature step the list is based on recipient records ( ruby recipient c ) defined for the tag (e g , customer) that are either associated with the current account (ruby account c = current account), or global recipients without a specific customer (ruby account c = null) dynamic recipient selection via plugin for more complex requirements, admins or developers can register a recipientselectionplugin that dynamically computes the available recipients for each e‑signature request based on the business needs how the plugin works create a global apex class and implement the ruby custompluginmanager recipientselectionplugin interface register the plugin from salesforce system settings → custom settings > nue system setting click the 'manage' button find the entry with the name 'recipientselectionplugin' edit the entry and set your global apex class name to the value field, then save the changes for each recipient row, nue calls the plugin’s getrecipients method with the quote id, and a map of recipient info, such as tag, action (e g , “needs to sign”), and signing order the plugin returns a list of recipient objects that define id, name, email, and role, which nue then presents as the available predefined recipients for selection when a plugin is registered, it will override the default recipient list associated with the recipient records (ruby recipient c), and admins or developers must maintain the predefined recipients via the plugin sample plugin the sample plugin below demonstrates how businesses can predefine a dynamic recipient list for different recipient types sales reps can select external recipient (customer) from a dynamic list (recipient records + static external recipients) internal recipient (internal user) from a static list additional recipient from a different list global class predefinedrecipients implements ruby custompluginmanager recipientselectionplugin{ global list\<ruby custompluginmanager recipient> getrecipients(string quoteid, map\<string, object> recipientinfo){ system debug('recipientinfo ' + recipientinfo); // get the current quote quote currentquote = \[select id, name, accountid from quote where id = quoteid]; // retrieve default external recipients list\<ruby recipient c> defaultexternalrecipients = \[select id, ruby tag c, name, ruby email c, ruby action c, ruby role c, ruby account c, ruby user c, ruby contact c from ruby recipient c where ruby account c = currentquote accountid and ruby tag c = 'customer']; list\<ruby custompluginmanager recipient> recipients = new list\<ruby custompluginmanager recipient>(); if(string valueof(recipientinfo get('tag')) == 'customer'){ // add the default external recipients to the available recipient list for(ruby recipient c r defaultexternalrecipients){ ruby custompluginmanager recipient defaultexternalrecipient = new ruby custompluginmanager recipient(r id, r name, r ruby email c, r ruby role c); recipients add(defaultexternalrecipient); } // add additional recipients ruby custompluginmanager recipient externalrecipient1 = new ruby custompluginmanager recipient('1', 'john', 'john\@nue io', 'cio'); recipients add(externalrecipient1); ruby custompluginmanager recipient externalrecipient2 = new ruby custompluginmanager recipient('2', 'mike', 'mike\@nue io', 'cfo'); recipients add(externalrecipient2); } else if(string valueof(recipientinfo get('tag')) == 'internal user'){ // add available options for internal recipients ruby custompluginmanager recipient internalrecipient1 = new ruby custompluginmanager recipient('000001', 'alex', 'alex\@nue io', 'manager'); recipients add(internalrecipient1); ruby custompluginmanager recipient internalrecipient2 = new ruby custompluginmanager recipient('000002', 'kate', 'kate\@nue io', 'sales'); recipients add(internalrecipient2); } else{ // add the available recipients for additional recipients (recieves a copy / needs review) ruby custompluginmanager recipient additionalrecipient1 = new ruby custompluginmanager recipient('additionalrecipient1', 'peter', 'peter\@nue io', 'vp of sales'); recipients add(additionalrecipient1); } return recipients; } } webhook events when the docusign integration is enabled in nue, the system will automatically create a docusign connect configuration (“nue connect”) in your docusign account subscribe that configuration to a set of envelope and recipient events (sent, delivered, completed, declined, etc ) convert those docusign events into standardized nue webhook events, such as document sent, document completed, recipient sent, and recipient signed once the system administrators register the events through a nue webhook endpoint, it will provide the downstream systems (e g , crm, billing, data warehouse) with real time visibility into the status of documents sent for e signature through nue