Nintex DocGen for Salesforce

Security updates and resolved issues

• Fixed an issue that was preventing Mass documents from generating when specifying the Contact field as ContactId.

• Added support for GiftTransaction Salesforce object.

• Updated Salesforce API version to v64.

• Security enhancements.

Important: In order to upgrade to package version 20.15, you will need to first upgrade to package version 20.10.5. This does not impact users doing a fresh install of package version 20.15. For more information refer to Multi-step upgrades for Nintex DocGen.

Resolved issues

• Fixed an issue where the Field Tagger displayed the wrong tag for some Apex Data Relationships.

• Fixed an issue preventing the use of the "AccountPlan" Salesforce object in a DocGen Package.

• Fixed an issue preventing some recipient types for esignature deliveries from being used in automation.

• Updated wording on the eSign Envelopes list to differentiate between not having a reference field to show related envelopes vs having no envelopes to display.

Security updates and resolved issues

• Fixed an issue causing an error when using specific SOQL Relationship configurations to get large numbers of records.

• Fixed an issue that was preventing packages from running using Nintex Workflow as a delivery method in Nintex Government Cloud tenants.

• General security updates.

Resolved issues

• Fixed a Salesforce bug that was preventing the update for a packaged Apex classes API version, which was preventing the automatic deployment of the Salesforce ICU locale release update.

Performance improvements and updates

• Updated Apex components API versions to facilitate ICU locale update.

  For more information refer to the following Nintex Community article: Salesforce ICU Locale Formats

• General improvements and bug fixes.

Stability improvements and resolved issues

• Updated API versions to facilitate ICU locale update.

  For more information refer to the following Nintex Community article: Salesforce ICU Locale Formats

• Fixed an issue that was causing generated PDFs to be larger in file size than expected.

• General improvements and maintenance for stability.

Stability improvements and resolved issues

• Improvements to API to increase file size. Increased file size limit from 50mb to 500mb.

• Fixed an issue that was causing repeating data when using Generate Document in some scenarios.

• General updates for stability and performance improvements.

Nintex DocGen Agentforce connector now available in the Salesforce AppExchange

You can use the Docgen Agentforce connector to:

• Generate documents from any Agentforce agent - the default Agentforce agent, Salesforce's service agent , or any custom agent you build.

• Use Agentforce for your existing Nintex DocGen packages - ask Agentforce to generate your proposals, contracts, quotes, licenses, summaries and more.

You need Agentforce enabled in your Salesforce Org to install and use the DocGen Agentforce connector. For more information, see our Agentforce help documentation.

Stability improvements and resolved issues

• General improvements and maintenance for stability

Added support for DocuSign Template ID for use in DocuSign delivery options in Lightning designer

Users can now specify a DocuSign Template ID when creating a document package using the DocuSign delivery option in Salesforce Lighting. This feature was previously only available for use with the DocuSign (Legacy) delivery option.

Resolved issues

• Fixed an issue where the Field Tagger was not pulling the correct SOQL Name tag when generating the document when using an Owner field.

• Fixed an issue that was preventing loopMessage from processing batches greater than 200.

• Fixed an issue that was causing the Contact Look Up to appear on the screen incorrectly when using a DocuSign delivery option in the Lightning component.

Stability improvements and resolved issues

• Fixed an issue that was preventing the default values for DocuSign Secure fields from displaying correctly in the preview.

Added support for DocuSign Custom Envelope Fields in Lightning designer

DocuSign Envelope Custom Fields can now be used when creating a document package in Nintex DocGen while using the DocuSign delivery option. This feature was previously only available for use with the DocuSign (Legacy) delivery option.

Added support for Brand ID for use in DocuSign delivery options in Lightning designer

Users can now specify a Brand ID when creating a document package using the DocuSign delivery option in Salesforce Lighting. This feature was previously only available for use with the DocuSign (Legacy) delivery option.

Resolved issues

• Fixed an issue where updated Snippets, connected to one or more document packages, were not updating with the most recent changes when generating the document.

• Fixed an issue that was preventing error notifications from being sent when running a package via Apex in Sandbox environments in some scenarios.

• Fixed an issue that was preventing Nintex eSign connection information from being completely removed when deleting a connection.

• Fixed an issue that was causing dates to be labeled as one day behind when viewing automated data reports for packages set for automation.

• Fixed an issue that was causing an error when viewing Recipients for DocuSign delivery options that were migrated from DocuSign (Legacy) delivery options.

• Fixed an issue that was preventing users from using the "Authorize Nintex DocGen" link when setting up Individual Consent.

Stability improvements and resolved issues

• Fixed an issue that was preventing DocuSign envelope status from writing back to Salesforce while in a sandbox environment.

• Fixed an issue causing certain document package runs to fail when using the Pause to edit feature.

• Fixed an issue causing errors when trying to run a document package set up for use with the DocuSign delivery option, while set up for OAuth – Individual Consent, and not specifying a Contact in the delivery option.

DocuSign OAuth Individual Consent option

The DocuSign and DocuSign Legacy integrations now support a user-based authentication option, OAuth - Individual Consent. With this option, users will be prompted with a DocuSign authorization screen when generating a DocGen Package using the DocuSign delivery option. Admins can also share the authorization URL available at set up to allow users to authorize their DocuSign accounts.

For more information, see:

• DocuSign Delivery Option

• Integration - DocuSign with Nintex DocGen

• Integration - DocuSign Legacy with Nintex DocGen

• Authorize a service account or individual users for OAuth - Individual Consent

Preview feature: Nintex Forms component in Nintex DocGen

Nintex DocGen now has a Forms component that uses the powerful data-capture functionality provided by Forms in Nintex Workflow. This component can be used to create Nintex Workflow forms in Salesforce pages and capture accurate record and user data from Salesforce within the form. For more information, see NintexForms component in Nintex DocGen.

Feature modifications and resolved issues

• Fixed an issue with the Field Tagger not displaying correctly.

Stability improvements and resolved issues

• Fixed an issue with stalling of the generate document action due to special characters in file names.

OAuth authentication for the latest version of the DocuSign for Salesforce app

Fixed an issue where OAuth wasn't working for the latest version of DocuSign's legacy app, DocuSign For Salesforce (DFSF).

OAuth authentication added for DocuSign Legacy

DocuSign Legacy integration now supports OAuth authentication as DocuSign will be deprecating basic authentication on September 30, 2024. Due to this deprecation, the 'Legacy authentication' and 'Specify Credentials for Sign on behalf of' authentication options will not work. For more information on this change and how you can switch to OAuth authentication, see DocuSign retiring Legacy Authentication - Get Ready!

Localization support for Nintex DocGen for Salesforce

The Nintex DocGen runtime experience is now available in French, Spanish, and German. For more information, see the Localization help topic.

Feature modifications and resolved issues

• Fixed an issue where using the Nintex Workflow external start type delivery option would not skip the progress bar.

• Fixed an issue with an error reported in RDLC when using a Quote with no related Opportunity.

• Fixed an issue where using special characters would prevent saving SOQL relationships in Lightning.

Additional DocuSign Custom Document Field types supported in DocGen Package templates

You can now use additional DocuSign Document Custom Field types in your DocGen Package templates to send out documents for signing using the DocuSign delivery method. Besides the text field type that is currently available, you can now add field types such as signature, dropdown, checkbox, and formula. For more information on the additional custom field types, see the Document Custom Fields section in the DocuSign Delivery Option help topic.

Stability improvements and resolved issues

• Fixed an issue loading sample DocGen Packages on old versions of Nintex DocGen for Salesforce (sample DocGen Packages were removed in v20.1).

• Fixed an issue with loading form steps in the Classic Designer.

Sample DocGen Packages removed

We've removed the legacy Sample Packages functionality from Nintex Admin and the onboarding wizard, as we now have the Package Templates to choose from when you create a new package (introduced in our last release).

Performance improvements and resolved issues

• Fixed an issue where some SOQL relationships could not be saved in Lightning.

• Fixed an issue where the "Authorize and Run" button would not work unless the page was refreshed.

• Fixed an issue where the Button Wizard in Nintex Admin would not load correctly.

• Fixed an issue that prevented migrating DocGen Packages from v20.0.1.

Template Gallery

Introducing the Template Gallery! The Template Gallery accelerates the document creation process by providing you with templates you can use to create a new Document Package based on what is contained within those templates. Simply choose a package template to start from. We're shipping with a handful of great examples, with more to come!

From version 20.0 and onwards you will receive updates to the Template Gallery, all without even needing to update your Nintex DocGen version! For more information on how the Template Gallery works, refer to the Template Gallery help topic.

Feature modifications and resolved issues

• Added the ability to choose whether decimals are included on 'Number' fields in the field tagger

• Fixed an issue where the "Grant Login Access" button was not visible in Nintex Admin

• Fixed an issue that was preventing the pop-out window for the Field Tagger from loading in developer orgs

• Fixed an issue that was preventing SOBO (Send-on-behalf-of) integration option from saving correctly when using legacy DocuSign integration options

• Fixed an issue that was preventing the use of the "Add Availability" function in Document Packages

• Fixed an issue that was causing the "Type" field to display as blank when cloning a Document Package

• Fixed an issue that was requiring the "To" field to be filled out on the Email Page and was preventing Document Packages from sending

• Fixed the help topic link for the Migration help topic

• Fixed an issue that was causing an error when using Email as a delivery method in certain circumstances

• Fixed an issue where the "Update Available" button was not properly displayed

Stability improvements and resolved issues

• Fixed an issue that was causing time outs on certain large reports

• Fixed an issue that was causing scheduled document packages to send out twice due to daylight savings time

• Fixed an issue that was preventing certain recipient tags from filling out if the first name and last name were the same

• General stability and resiliency improvements

Performance improvements and resolved issues

• Updated Box integration to work on any environment

• Updated API to account for Chrome phasing out third-party cookies

• Updated error messaging around attempting to generate a document with a template that has been deleted

• Fixed an issue that was causing longer document generation times for certain scenarios involving images

• Fixed an issue that was causing licensing errors in some Sandbox environments

• General stability and security updates

Addition of Nintex Assistant for DocGen Help

Introducing our latest innovation for DocGen: the Nintex Assistant! Pumped full of all our training and Help content, this AI-based tool answers your DocGen questions with just a few keystrokes. A new button has been added to the Nintex Admin screen and the Document Package Designer screen that can take you directly to the Nintex Assistant.

Give it a try!

Migration of DocGen Document Packages now available in Salesforce Lightning Designer

You can now migrate Document Packages from one Salesforce Organization to another directly from the Salesforce Lightning Designer and no longer need to switch to Classic designer. All of the options available in our Classic designer are also available in our Lightning Designer.

For more information on how to migrate Document Packages refer to our Migrate DocGen Packages help topic.

DocuSign Document Custom Field writeback

DocuSign Document Custom Fields have been updated in the Salesforce Lightning Designer to now show up in the Field Tagger list and allow signers to writeback data related to the field and record in Salesforce. For more information on how to use Document Custom Fields refer to our DocuSign Delivery Option help topic.

Performance improvements and resolved issues

• Fixed an issue that was preventing the pop-out window for the Field Tagger from loading in developer orgs.

Performance improvements and resolved issues

• General improvements and minor bug fixes.

Deprecation of bypass of Salesforce Lightning Designer option

Nintex DocGen is deprecating the option to turn off the use of Salesforce Lightning Designer. The Lightning Designer interface now loads by default for all users.

For users who would like to use the Classic interface, you can manually switch to the Classic interface using the switcher in your Salesforce User Profile.

Performance improvements and resolved issues

• Deprecated the option to bypass the Salesforce Lightning Designer option in Nintex Admin to improve performance while using Lightning Designer.

• Fixed an issue where DDPs with the same name would cause an issue with connecting Snippet Groups.

• Fixed an issue where Field Tags for Snippet Groups were not generated correctly in the Lightning DDP Designer.

Features

Introducing "Snippets" - Conditional and reusable content in Lightning Designer

• Changed naming of Components and Component Groups to Snippets and Snippet Groups in Lightning Designer and Classic Designer.

• Added "DocGen Snippet Group" tab in Lightning Designer. This tab allows you to create new and reusable content inside of the Lighting Designer interface. For information on how to add this tab, see Add and Customize Tabs on Lightning Pages Using the Lightning App Builder.

• Snippets and Snippet Groups can now be created in Lighting Designer. Utilize Snippets and Snippet Groups to create reusable content that can be applied across multiple s. Snippets and Snippet Groups can be linked to Document Packages and you can set conditional filtering to further refine how and when this content displays. For more information on the usage of Snippets and Snippet Groups see Snippet and Snippet Groups on the help site.

DocuSign now available as a Mass delivery option

Mass support has been added for Document Packages. Mass allows you to generate a batch of documents for signing as it pertains to a record list. can now be selected as a delivery option. For more information on how to use DocuSign with Mass, see DocuSign Delivery Option on the help site.

Performance improvements and resolved issues

• General improvements and minor bug fixes.

Features

• Added support for DocuSign Delivery Option to our Lightning Designer. This is our integration with DocuSign's newest Salesforce package, the DocuSign App Launcher. The delivery option can be selected when creating a new DocGen Package. For more information how to use the DocuSign integration inside of the Lightning Designer, see the DocuSign Delivery Option on the help site. To update Nintex DocGen to version 19.1 use the Upgrade button in Nintex Admin (requires DocGen Package 18.25+).

Performance improvements and resolved issues

• Increased page load and document generation performance via implementing the standard feature parameters approach in packages rather than the legacy custom Loop Services Object.

• Fixed an issue where running a package with form inputs via loopPlus would fail.

• Fixed an issue where there was an error when reordering Document templates in LEDD.

• General improvements and bug fixes.

Performance improvements and resolved issues

• Fixed an issue where automated DocGen instances would report as -1 day.

Features

• Updated DocuSign integration to support OAuth - Admin Consent authentication method. This option is available in the integration options when setting up a DocuSign integration. For more information review the set up guide for integrations.

• Added a link in the Nintex Admin section to upgrade your DocGen for Salesforce app when applicable upgrades are available.

Performance improvements and resolved issues

• Increased page load and document generation performance via implementing the standard feature parameters approach in packages rather than the legacy custom Loop Services Object.

• Fixed an issue where running a package with form inputs via loopPlus would fail.

• Fixed an issue where there was an error when reordering Document templates in LEDD.

• General improvements and bug fixes.

Performance improvements and resolved issues

• Fixed an issue where migrating a DDP between Salesforce orgs wouldn’t complete successfully if the DDP had a Nintex Workflow delivery option.

• Updated DocGen to support changes to Salesforce’s Croatian (Croatia) and English (Sierra Leone) locale.

Performance improvements and resolved issues

• Introduced a What’s new panel to keep you up to date on new features, announcements, and releases.

• Updated branding of AssureSign to Nintex eSign.

• Fixed an issue where Nintex eSign envelope status and history were not updating.

• General improvements and bug fixes.

Performance improvements and resolved issues

• General improvements and bug fixes.

Performance improvements and resolved issues

• General improvements and bug fixes.

Performance improvements and resolved issues

• Fixed an issue where DocGen Packages failed to run in Salesforce Experience Cloud (formerly Salesforce Communities).

• Updated the Salesforce API version that DocGen is using due to recent deprecation by Salesforce.

• General improvements and bug fixes.

Features

• Added the ability to integrate with Nintex eSign (previously AssureSign) GovCloud infrastructure when setting up the Nintex eSign integration in DocGen Admin.

• Added a link to DocGen Designer for customers to submit ideas to the DocGen product team.

• Added a useful error message when a Nintex eSign template that is too large to be processed is selected in a delivery option.

• Added seven days of history to the Automated DocGen Instances section inside DocGen Admin, including completed, error, and pending runs.

Performance improvements and resolved issues

• Fixed an issue in DocGen Admin's Automated DocGen Instances section causing timeouts when loading data.

• Fixed an issue causing an error when browsing document templates in some Salesforce libraries.

• Fixed an issue that prevented download of a generated document from the runtime Lightning Component for some customers.

Features

• Added the ability to save signer data back to Salesforce if you are using Nintex eSign as a delivery option for your DocGen Package. Any Jotblocks that your customer fills out in your Nintex eSign document can now be written back to a starting object (or objects with relationships to the starting object) used in your DocGen Package.

Performance improvements and resolved issues

• Fixed an issue where fields from "Contact Role" Objects were not showing in the Lightning designer's Field Tagger.

• Fixed an issue where running a Document Package using the Lightning Component did not require optional documents when configured to do so.

Performance improvements and resolved issues

• Improved intermittent DocGen Package run failures by adding retry logic into Salesforce calls.

• General improvements and bug fixes.

Performance improvements and resolved issues

• Fixed an issue affecting package runs with organizations using Veeva Vault and Enhanced Domains.

• Enabled signer delegation functionality with the Nintex eSign delivery option.

Performance improvements and resolved issues

• Fixed a bug where the Field Tagger displayed incorrect text for objects from lookup relationships.

• Fixed a bug where the DocGen integration user (configured on the DocGen Admin tab) would incorrectly provide the context user for Nintex eSign delivery options.

• Fixed a bug where the Preview DocGen component would error in some scenarios.

• Fixed a bug where templates wouldn't load on the Documents tab in the package designer due to templates with a null value in the Order field.

• Fixed an issue that was requiring a contact to be chosen in the To field at runtime for the email delivery option in 18.12.

Features

• Added the ability to generate documents on a scheduled basis (daily, weekly, or monthly).

• Added the ability to clone an existing DocGen Package in LEDD to create a new DocGen Package.

• Updated the DocGen Setup Wizard. Configuration of the Nintex eSign integration can now be completed as part of the initial DocGen setup.

• Added a section in DocGen Admin which indicates if your Nintex eSign license has expired or in how many days it will expire. Nintex eSign Delivery Options are disabled when the Nintex eSign license expires.

• Updated the Nintex eSign Envelope History log to update after each signing step.

Performance improvements and resolved issues

• Fixed an issue where the To field for the DocGen Package email delivery method shows an error for recipient not found.

• Fixed an issue where the context user for a Nintex eSign integration was being set at the profile or organization level rather than the user level. When creating a Nintex eSign integration, the context user will now automatically be set to the current user's email address.

• Fixed an issue running automated DocGen Packages using field tags in Nintex eSign recipients.

• Fixed an error occurring when trying to load an email page with merge fields when the locale of the user is set to Turkey.

• Fixed an error when creating a Nintex eSign Delivery Option.

• Removed the edition step from the setup wizard and Admin tab.

• Added the ability to disable automatically downloading Nintex eSign documents in Salesforce.

• Added support for newer standard Salesforce objects.

Performance improvements and resolved issues

• Added an error notification for DocGen Package owners to help resolve common integration errors that can occur between Nintex DocGen for Salesforce and Nintex eSign.

• Fixed an issue where users in the Salesforce Government Cloud environment could not log in via the standard domains login.salesforce.com or test.salesforce.com because of additional security features.

Features

• Added the in-person signing feature which allows for on-site signatures to be collected immediately after preparing a document for signature.

• Added the ability to cancel Nintex eSign envelopes from the Salesforce application.

• Updated the user interface for adding PDF Stamps.

Performance improvements and resolved issues

• Fixed an error occurring when navigating sections of a new DocGen Package.

• Fixed an error occurring when running a DocGen Package which uses an Nintex eSign template in which the default signer name has been changed manually.

• Fixed an error occurring when testing Nintex eSign delivery options using a Nintex eSign trial license.

Performance improvements and resolved issues

• Fixed an issue causing a report download failure when running a DocGen Package in Salesforce Classic and Classic-in-Lightning with the Salesforce Winter 2023 release.

Performance improvements and resolved issues

• Enabled Salesforce communities to work with the enhanced domains Salesforce feature.

• Resolved an issue when trying to use custom Salesforce fields with Hierarchy Assistant Nodes.

• Fixed an issue with the AssureSign Delivery Option where Date Jotblocks were not being pre-filled.

• Expanded the Hierarchy Assistant Nodes feature to allow for checkboxes in addition to the current simple text fields. A checked checkbox (a true value) marks a node as being an Assistant node, and an unchecked checkbox (a false value) marks a node as being a Standard node.

Features

• Updated the Field Tagger panel to automatically refresh anytime there is an addition or deletion in a Relationship, or if there is an update to an alias or the Repeat By field.

• Added the ability for Document Package designers to add Enclosures to Document Packages.

Performance improvements and resolved issues

• Updated metadata to align terminology for the feature called Insert-Updates in Classic and Create or Edit a Record in Lightning.

• Fixed an issue where a button that selects a specific Delivery Option chooses the wrong Delivery Option ID.

• Fixed an issue where deleted attachments on Salesforce Chatter posts continued to show up on the run page.

• Removed deprecated S-Controls from the Salesforce package.

Features

• Added the PDF Stamp feature to the Lightning Designer to insert text, images, or rectangles into output files of DocGen Packages.

• Added the Create and Edit (previously Insert-Update) feature to the Lightning Designer to configure actions to create or edit a record when generating documents from a DocGen Package.

• Updated the Automated DocGen Instances to replace the static job queue status page with a downloadable report.

• Added a feature allowing designers to choose an additional record to attach a signed document to when using an AssureSign Delivery Option.

• Added a feature to allow administrators to configure which AssureSign user is used in AssureSign Delivery Options.

• Updated the user permission set to include permission for specifying the hierarchy node type.

Features

• Added support for AssureSign Delivery Options to send generated documents for e-signature in automated instances; this uses loopMessage and Flow components. Users now have access to AssureSign as an automated delivery option from DocGen.

• Added the ability to track and view Envelope history for Nintex AssureSign Envelopes.

• Added a Lightning component that displays AssureSign Envelopes related to a Salesforce Record.

• Added support for specifying the node type (assistant or standard) in MS Office Organization Charts.

Performance improvements and resolved issues

• Fixed an issue where the field tags displayed were not formatted for the indicated document type after refreshing.

• Fixed an issue where text in conditions for conditional templates overlapped.

• Fixed an issue where extra objects would appear in the field tagger.

• Fixed an issue where the button sections in the DocGen Admin tab were unresponsive.

• Fixed an issue were field tags for AssureSign JotBlocks were not correctly generated.

• Fixed an issue where the field tagger would not display the recipients section.

Resolved issue

• Fixed an issue where Rich Text dynamic images on child-level objects were unable to be downloaded.

Performance improvements and resolved issues

• Fixed an issue with tag filling for secure fields containing SOQL Dot Notation for DocuSign and ESignLive DocGen runs.

• Fixed an issue for when users uploaded images in rich text fields and the Use Post Requests for cross-domain sessions check box is selected in the session settings.

• Fixed various issues to improve overall improvements and efficiency.

Resolved issue

• Fixed an issue where invalid tags were created for Lookup Relationships in the Field Tagger (Lightning Experience).

New Features

Lightning Experience DocGen Package Designer (LEDD)

• Added support for Field Tagger.

Performance improvements and resolved issues

• Updated Nintex DocGen with security enhancements.

• Fixed an issue that caused an error during Nintex eSign integration set-up when the Enter key was pressed to submit credentials in some scenarios.

• Fixed an issue where the Preview DocGen component (RunDocGen.cmp) caused an error when navigating away in some scenarios.

• Fixed an issue that prevented AssureSign Envelopes from populating lookup fields to their starting record in some scenarios.

New features

• Added support for optionally merging data into ad hoc documents that are added at runtime.

  • This update includes a Merge Data into Ad Hoc Files checkbox to the Documents tab in the Lightning Designer.

  • New DocGen Packages will no longer merge data into ad hoc documents by default.

• Added support for the new standard objects up to Salesforce Metadata API 54.0.

Performance improvements and resolved issues

• Resolved an issue where the Lightning Designer would time out when users attempted to load DocGen Packages with many Relationships.

• Resolved an issue where completed AssureSign Envelope were not attaching to the signed documents to the starting record.

New features

• Add support for new standard objects up to Salesforce Metadata API 54.0.

Performance improvements and resolved issues

• Resolved an issue with third-party integrations where a user was asked to allow access after access was already granted.

• Update Salesforce API version from v50 to v54.

New features

• Updated Nintex Drawloop DocGen to no longer require Nintex AssureSign Lightning to view Envelope status and details.

  • Added a pre-defined set of webhooks for AssureSign Envelope status updates to be used instead of using webhooks that were configured in the AssureSign Templates.

  • Added functionality to create related AssureSign Envelope records to conveniently view the AssureSign Envelope status and details when using the Nintex eSign Delivery Option.

  • Added functionality to return the signed document to the AssureSign Envelope record once the document has a status of "Complete".

Performance improvements and resolved issues

• Fixed an issue where Mass via Report would not run with predefined parameters in the URLs for DocGen Package versions 17.9 and 18.0.

• Updated the Button Wizard so that when you create a JavaScript button, the code that is generated references the latest AJAX toolkit version.

Performance improvements and resolved issues

• Fixed a Daylight Saving Time issue for Brasilia Standard Time.

• Fixed an issue with AssureSign Sub Account location.

• Improved timeout issues for those experiencing latency.

• Resolved an issue so that mass DocGen Packages can be run again.

• Fixed an issue where Grouped Relationships now work as expected.

• Resolved issues for the following delivery options:

  • SignNow

  • OneSpan Sign

  • SMTP Delivery Option

  • DocuSign

  • Post PDF and Originals (autosend)

• Resolved an issue with row replication so that links are now correct.

• Resolved CSV errors with Job endpoints. More details are found in the CSV documents.

• Improved Pause to Edit functionality.

• Updated Scratch org licenses to be set to True in order to have a Sandbox property.

• Improved performance of PowerPoint templates that contain images.

• Fixed multiple issues with Ad Hoc files.

• Fixed Visualforce template errors.

• Fixed an infinite query loop error.

• Fixed an error for Office 365 documents.

• Fixed an issue with unrelated data relationships.

• Fixed an issue with OBM requests.

• Fixed an issue with incomplete jobs.

• Fixed an issue with Document Template with Separate PDFs in preview mode.

• Fixed AssureSign Envelope issues.

• Added Job Queue improvements.

• Improved App Insight logging.

• Improved 404 logic.

• Fixed an authorization issue with Scratch orgs.

• AssureSign integration improvements.

• Added support for pre-defined values in adhoc webhooks.

New features

• Added select lists for URLs instead of text input fields in the AssureSign integration setup.

• Updated the AssureSign integration username with App name and Org ID

• Updated the AssureSign JotBlock Field Tags so that they are organized by Signer when you configure a Nintex AssureSign Delivery Method.

• Added a Refresh Inputs button to the Nintex AssureSign Delivery Method that refreshes a template to display the latest changes in Nintex DocGen if the template was changed in AssureSign.

• Added a View Template in AssureSign link to the Nintex AssureSign Delivery Method so that the DocGen Admin can quickly navigate to the template in AssureSign.

Performance improvements and resolved issues

• Fix an issue that prevented you to select Contact for the email delivery options.

• Updated the Nintex AssureSign Delivery Method to use Single PDF for an output.

• Updated the Nintex AssureSign Delivery Method to warn users when unsupported Addendum Sender Inputs exist on an AssureSign Template.

Other Updates

• Update Salesforce REST API Version in preparation for Salesforce Summer '22 release.

Resolved issue:

• Resolved an error that occurred when using Field Tags for Name & Email field with the Nintex AssureSign Delivery Method, an error no longer occurs.

New features

• New Nintex eSign delivery option. For more information on adding Nintex eSign to your integrations, see Third Party Integrations.

• Adobe Sign has changed to Adobe Sign.

Performance improvements and resolved issues

• Several issues and updates have been deployed to improve quality.

New features

• Added support for the Nintex AssureSign Delivery Option.

Lightning Experience DocGen Package Designer (LEDD)

New feature

• Add support for query string parameters in Reports in LEDD.

Performance improvements and resolved issues

• When viewing the Classic runtime experience in Lightning, using an Email Delivery Option will show Contacts email addresses.

• Resolved an issue so that duplicate Group By fields can no longer be configured on Relationships.

• Added a search field that allows you to search for Reports in Connected Data.

• Added Delivery Option Help Text in the Classic runtime when viewed in the Lightning Experience.

• Updated Form Field Help Text to be available in the Classic runtime when viewed in the Lightning Experience.

• Enabled the loopMessage class to be used in LEDD.

• Added scrolling to email templates with a sufficient height in the Lightning Experience runtime.

• Resolved an issue so that an error no longer occurs when Enabling Enhanced Notes is used with the attachments=all parameter.

• Resolved an issue where E-sign Recipients with legacy configuration no longer causes a Lightning Experience runtime error.

• Improved Template loading performance in LEDD.

• Resolved an issue so that when a user rapidly navigates between the LEDD tabs, an error no longer occurs.

Other Updates

• Enhanced the look and feel of menus and picklists in the LEDD user interface.

• Added the following message in the Classic DocGen Package management user interface: "Template management is no longer supported in Salesforce Classic. To manage your template, please use Lightning."

• Updated Nintex Sign Delivery Methods so that it can to no longer be configured before the integration is configured.

• Using a Recipient Report no longer blocks running when validity is indeterminate.

• Remove deprecated code.

• Updated the DocGen Admin navigation.

  • Updated the name of the Job Queue Status page to Automated DocGen Instances.

New features and updates

• Optimized processes to acquire licensing data.

• Updated messaging to enable better error handling.

• Deprecated Cipher Cloud & Perspecsys support.

Performance improvements and resolved issues

• Several issues and security updates have been deployed to improve security and quality.

Performance improvements and resolved issues

• Resolved an error rendering email templates with URL Stabilization enabled.

• Resolved an error using the processDDP and Preview DocGen components with Salesforce Communities under a Custom Domain.

Other updates

• Enhanced the user interface for Comboboxes in the Lightning Experience DocGen Package Designer.

Performance improvements and resolved issues

Lightning Experience DocGen Package Designer (LEDD)

• Resolved a performance issue in the DocGen Packages that contain multiple relationships.

• Resolved a performance issue with loading, sorting, and deleting templates.

• Added error handling for relationships that do not match the Starting Object.

• Enhanced scrolling to new relationships in Safari.

Other Updates

• Resolved an error that prevented changes to storage location in the Classic Experience.

• Add support for Topaz Signature Pads with DocuSign Delivery Options.

• Updated the DocGen Flow Component to support Communities with site paths.

Updates

• Removed the following change that was introduced in v17.6, as this prevented some customers from successfully delivering generated documents:

  • Using the Flow preview component or our processDdp Visualforce component in a Salesforce Lightning Community with a custom domain will no longer result in an error when attempting to generate documents.

Lightning Experience DocGen Package Designer (LEDD)

• Your browser will auto-scroll to the newly created relationships. Previously, the form for that relationship appeared out of view below the current position on the page.

• Improved visual issues in the File Selection component when a new template is added to a DocGen Package.

• Resolved an issue that caused selected checklist options that have been cleared checklist options to still display as selected in a few LEDD configuration options.

Other Updates

• Using the Flow preview component or our processDdp Visualforce component in a Salesforce Lightning Community with a custom domain will no longer result in an error when attempting to generate documents.

• The DocGen Package Search feature in the Lightning Component has been disabled if no DocGen Packages are available to run for the Salesforce Record you are viewing.

Performance improvements and resolved issues

Lightning Experience DocGen Package Designer (LEDD)

• The Remove Template confirmation dialog modal has been updated to account for templates with long names. Those names will no longer be cut off at the end of the modal.

• The Relationship Alias validation introduced in v16.4 has been scoped down to the DocGen Package. This improves the loading time of Relationships, and reduces/prevents timeout errors that would prevent you from managing your DocGen Package.

• Templates with incomplete or incorrect metadata will no longer cause errors in LEDD. The incomplete or incorrect metadata could have surfaced when using Dataloader to move templates between orgs instead of using our Migration Tool. These cases are rare, and we've added handling for them so the management of DocGen Packages is not impacted.

• New Templates added in LEDD will no longer contain their file extension by default.

• With LEDD enabled, the Create New DocGen Package button at the end of the Drawloop Setup Wizard for new installs will now correctly direct you to the LEDD DocGen Package creation screen instead of the Classic creation flow.

Other Updates

• In the Drawloop Lightning Component, the Authorization Required information banner that appears for users who have not yet gone through the OAuth flow for Nintex Drawloop has been update to match current Salesforce Lightning Design Styles.

New features

Lightning Experience DocGen Package Designer (LEDD)

• Added further checks to capture improperly configured relationships. These relationships will be shown in the Invalid Relationships section for you to review. You can then reconfigure the relationships as you need.

• Loading the Classic DocGen Package management user interface in Lightning will no longer display errors in rare cases.

• Cloned or Migrated DocGen Packages will no longer show duplicate relationships.

• Updated styling in the LEDD interface to match changes introduced in Spring '21.

• Resolved an issue where Connected Data configurations stored in a really old format caused errors when loading a DocGen Package.

• Resolved an issue that prevented DocGen Packages from saving due to long template names.

• Invalid Relationships will now always be shown at the end of the Relationships section.

• The following fields can no longer be saved with no value or with whitespaces as this causes issues with loading or running the DocGen Package:

  • Data Tab:

    • Data > DocGen Package Name

    • DDP Type > Other > Text field

  • Documents Tab:

    • Template > Name

    • Template > Include Template > Conditionally > Conditional Fields (first field)

    • Template > PDF Bookmark

  • Delivery:

    • Output Filename

    • Delivery Option Name

Performance improvements and resolved issues

• Updated the application to now use Salesforce API version 50. This allows access to more objects and fields when creating DocGen Packages or relationships.

• The viewable size for embedded eSign experiences, such as embedded signing or Signing Preview and Edit, has been increased to proportionally match the size of your browser window.

• Resolved an issue that prevent users, namely Community Users, from generating documents that contained a Visualforce page as a template.

• Security Fixes.

New features

Lightning Experience DocGen Package Designer (LEDD)Package 17.3

• Added a new info section at the top of the Delivery tab, calling out that not all features may be currently supported in the new Lightning Designer, and with a link to the DocGen Package details in Salesforce Classic in a new tab/window. The link will not change the Salesforce User’s context (whether they are in Salesforce Lightning or Classic), so Designers can make edits in the new tab/window, and then close to remain in Lightning to manage their DocGen Package.

• The appropriate User’s profile picture will now be displayed for the Created By and Modified By details in the Metadata Panel.

• Resolved an issue that prevented some Connected Excel file configurations (fka Excel as Middleware) from correctly displaying in LEDD.

• DocGen Packages with SOQL Relationships that contain a nested query will no longer error when navigating to the record for that package.

• The menu button for Relationship cards is no longer aligned to the middle vertically, it is once again in the top right where it belongs.

• You should no longer get errors when creating new DocGen Packages in LEDD after enabling the new Lightning Designer.

• Prevented saving Nintex Sign / Adobe Sign delivery options with no Sign Configuration defined, which would cause errors when generating and sending documents for esignature.

Performance improvements and resolved issues

• SMTP Third Party Configurations and Delivery Options can now use non-email based SMTP username credentials.

• Custom Console components enabled on Standard Object layouts will no longer prevent the DocGen Admin > Basic Buttons page from loading.

• Added access to the VisualforceSessionId Visualforce page in our managed package to the DocGen Admin and DocGen User permission sets.

• Resolved an issue that prevented DocGen Users from generating documents when using our Lightning Component in orgs with the following setup:

  • “Remove Instance Names From URLs for Visualforce, Experience Builder, Site.com Studio, and Content Files” Release Update enabled

  • OAuth setting enabled, and had previously not authorized the Drawloop DocGen app

• Resolved an issue that caused errors when attempting to change the storage location for delivery options that stored generated documents to Content.

• Removed the Nintex Drawloop Customization Guide Document file included in our managed package, as this file was a URL reference to a long outdated and now unavailable Drawloop support site.

• Nintex Sign / Adobe Sign delivery options that are not configured to Autosend will no longer appear in the Drawloop DocGen Lightning Component added to Lightning Page layouts

• The DocuSign User label when configuring a DocuSign Third Party Integration is now properly visible, no longer trying to hide from view.

Updates, performance improvements, and resolved issues

• Updated the DocGen Engine to now connect to the Salesforce API V50, to allow access to more Objects and Fields.

• Updated Dynamic Image replacement that use record IDs in fields to no longer require the file extension appended to the record ID. The file extension is still required when using reference record IDs in button/URL parameters.

• Resolved an issue where DocGen Packages that contained templates saved in .doc, .xls, or .ppt formats caused slightly longer runtimes. We highly recommend that files in this format be saved in the modern .docx, .xlsx, and .pptx formats.

• Added a new error message that displays when two or more Form Fields are using the same tag; "Form field tags must be unique per field across the entire form, even on multiple steps."

New features

• SMTP Third Party Configurations and Delivery Options can now use non-email based SMTP username credentials.

New features

Lightning Experience DocGen Package Designer (LEDD)

• DocGen Package template files with invalid page ranges will no longer cause errors in LEDD, or prevent all templates for not loading. We've also introduced validation to prevent saving templates with and End Range equal to 0, when the Start Range is 1 or larger.

• Implemented further updates to how Unsupported relationships are handled when parents are deleted. In this update, if you have a Broken Relation (no parent or link to a valid object), deleting it will not cause any of its dependent relationships to be deleted as well.

• The new Lightning Designer is now enabled by default on the DocGen Admin tab when upgrading to the latest version. The Lightning Designer can still be disabled if needed on the DocGen Admin, bit of a warning, this is a global change and will impact all DocGen Designers managing your DocGen Package Templates.

• The appropriate data replication start tag will now when configuring Connected Data.

• Resolved an issue that caused errors to appear when navigating between multiple DocGen Packages in the new Lightning Designer, or when navigating to a the record page for another Object from a DocGen Package.

• A warning will now display if the source or permission to a Connected Data file or Report is removed.

• DocGen Package templates that had their source file deleted or permission removed will no longer cause errors in LEDD.

Performance improvements and resolved issues

• Added the MetadataProviderController Apex class to the DocGen Admin permission set to address Salesforce security changes. The additional class is related to updates we made in v16.7.

• Security Fixes

Performance improvements and resolved issues

• Image replacement using a Salesforce Files record id saved in a custom Object field is now supported. I apologize, we don’t have proper documentation for this yet, but if you used this feature in the past hopefully you’re really excited by this news as it was previously limited to only Document and Attachment record id’s, or external URLs.

• Resolved an issue that caused the wrong value to be displayed when using the Pause to Edit feature to view Word documents with Merge fields.

• Added a new error message in the case of after three (3) we can’t complete the process of combining PDFs to a Single PDF.

New features

Lightning Experience DocGen Package Designer (LEDD)

With this release, you can now manage all of your DocGen Package templates within the Lightning Designer, which does not require the use of Adobe Flash.

• Connecting Salesforce Reports, Excel Templates (aka Excel as Middleware), and Runtime CSV or Excel files to your DocGen Package template is now supported.

• Template management is available for Scheduled DocGen Packages, however to manage timing and activation, and your desired delivery settings you will need to continue using the Classic UI. To make it a little easier for you, Scheduled DocGen Packages now have a button that will open the Classic UI in another tab/window without requiring you to switch to Salesforce Classic or disable the Lightning Designer.

• Invalid Relationships will now be shown in a new section in the Relationship Forest on the Data tab. These relationships will be shown in a grid without displaying Parent-Child or Lookup connections. Invalid relationships are are typically a Lookup off a Lookup, or a child relationship that is four (4) or more levels deep.

  • Note: Invalid relationships are those that are not explicitly supported by Nintex DocGen. These relationships may work for you now, and will continue to work even after upgrading, we are making no immediate changes to cause data from "working" invalid relationships to stop filling data. However, you will want to review these relationships as we may make changes in the future that could cause these invalid relationships to stop working.

  • Previously when you delete a relationship with children, all child relationships were also deleted. As we do not show the parent-child or lookup connections for Invalid relationships, deleting parent relationships will not delete its children. We made this update so you can can continue to review your invalid relationships before making appropriate changes to replace them with supported relationships.

• When removing a template from your DocGen Package, we've updated the messaging where appropriate to warn that your template may be referenced by another template, applies mainly to Excel template used as middleware and connected to a Word or Powerpoint template.

• Added better error handling in case of any issues loading Relationships. This will address cases for Orgs with loads of Objects and relationships that may have caused ugly component errors to surface.

• Relationship filters will now show all the same fields you would find in the Classic UI, such as "Name" fields that were lookups to others Object records.

New features

Lightning Experience DocGen Package Designer (LEDD)

• In DocGen Admin, the "New" has been removed from next to the control to enable the Lightning Designer, and we have stripped any "Beta" messaging from the Help text. The Lightning Designer is now officially out of Beta.

• New Installations for Nintex DocGen for Salesforce have the Lightning Designer enabled for them. DocGen Admins still have the option to disable the Designer on the DocGen Admin Tab > Home page.

Performance improvements and resolved issues

• In Salesforce Classic, DocGen Packages will once again load for orgs that have a large number of applications installed. The root cause was an attempt to check the version of Drawloop DocGen that is currently installed, and then provide a helpful notice to upgrade when a new version exists. Instead, if we can not determine the version installed the notice will no longer appear. DocGen Admins will want to check the Nintex Drawloop DocGen for Salesforce AppExchange listing every so often to see if a newer version is available.

• To address Salesforce permission updates, we've updated the included DocGen Admin and DocGen User permission sets and profiles to provide access to additional packaged Apex classes. If you currently use your own custom Permission Sets for managing access to objects and fields included in Nintex DocGen, you will want to make updates according to the lists found on our knowledge article for Required Apex Classes.

• Security Fixes

Performance improvements and resolved issues

• Having Salesforce Document and Salesforce Reports folders with the same name will no longer cause errors when using the DocGen Package Migration tool.

New features

• The message field is now supported for OneSpan Sign delivery options. The field only allows plains text, supports field tags, and will be sent to all recipient/signers of the OneSpan Sign Package.

• PDF's generated from Word or Powerpoint files will now have their document title set to match the title configured in their respective source template file.

New Features

• Improved how we retrieve images from Rich Text Fields for Dynamic image replacement.

Performance improvements and resolved issues

• Resolved an issue where sometimes the Mass DocGen Status emails wouldn't be sent. This scenario differs from the one fixed by v16.7.9

• Fullname, Title, Datesign, and other secure fields for OneSpan Sign delivery options will once again be assigned to the proper recipient.

• Sertifi delivery options should no longer result in a timeout error.

Performance improvements and resolved issues

• Resolved an issue that caused some Mass DocGen status emails to not be delivered.

New features

Lightning Experience DocGen Package Designer (LEDD)

• Viewing, Editing, Deleting, and Adding New DocGen Package templates from Sharepoint Online (labeled as Office 365) is now available.

Performance improvements and resolved issues

• Resolved an issue that caused some the document generation process using the processDdp component to sometimes unexpected stop, or result in an Invalid Session Id error.

New features

• When using the Classic run experience, SMTP delivery options with the Preview Step enabled, allowing you to download the generate documents before clicking the button to send the email, will once again redirect Users back to the Salesforce Record they initiated to docgen process from.

• Security Fixes

New Features

Lightning Experience DocGen Package Designer (LEDD)

• You can now upload new template files directly from the Documents tab. You will have the option to select which Salesforce Files Library (recommended) or Salesforce Documents Folder you wish to store them.

Relationship Validation Updates

• Relationship Alias names will now be validated against all Standard and Custom Object API names. This means for a Custom Object with an API Name of "ACME__c", we will now validate and prevent using the alias of "ACME". This also applied to Objects from any managed package.

• In cases where a DocGen Package contains a relationship with an existing Alias that matches a newly enabled Salesforce Object, Designers will see now a validation warning navigating to that DocGen Package, prompting them to update their Alias.

General Updates

• We've updated how the Relationship Container and Relationship Object Cards are sorted and displayed in both the Relationships section of the a DocGen Package, and the Metadata Panel.

  • Relationship Object cards, those that display the Object Name (and Alias), and Repeat by type, will be shown in order of most recently created at the top, to oldest created at the bottom.

  • Relationship Container cards, larger cards that contain all the Relationship Object Card cards (label as "Relationships from Starting Object, or "Relationships from Objects") will now be shown chronologically with the oldest created towards the top, and more recently created at the bottom.

• DocGen Packages with more than 100 document templates will no longer error when navigating to the Documents tab.

• Aliased fields in SOQL Relationships will no longer have the wrong tag in the Field Tagger.

• The Restrict Reflective Access to Non-Global Controller Constructors in Packages critical update when enabled will no longer cause an error when saving Delivery Options.

Performance improvements and resolved issues

• Added a loading spinner when editing Component Group Filters, this will prevent issues in case where it takes some time for the page load before allowing you to properly save any changes.

• Users without permissions to Delivery Options will now an informative error message in Flows utilizing the Preview Component. This typically surfaces with users without the included DocGen User or DocGen Admin permission set (assigned when granting the user a Drawloop DocGen License), or when using a custom permission set that may have missed this object.

• The email preview screen in Lightning will no longer show the body field in a shrunken state, you can once again view more than 1 line at a time.

• Email attachments stored temporarily in a user's "My Personal Documents" folders will once be properly deleted, no longer taking up storage space long after the emails have been sent.

• Salesforce Users assigned the the included DocGen Admin permission set will no longer encounter errors when navigating to the DocGen Admin tab.

• Security Fixes

Performance improvements and resolved issues

• The Status Reports for Mass DocGen runs will now include the following information when applicable: Starting Object, DocGen Package Id, Delivery Option Id, Contact ID

• Clicking the options to open and view template files stored in Office 365 should now open new windows to the correct URL. This applies to any templates files added to DocGen Packages following the June 2020 release. Previously added templates files unfortunately will not have their reference URLs updated, if you wish to have the links take you to the proper URL you'll need to remove and re-add them.

• Security Fixes

Performance improvements and resolved issues

• Resolved an issue that caused docgen runs to error if they utilized a Visualforce page as document template.

• Using both Forms and including Attachments should no cause docgen runs to error when run from Case records.

New features

Lightning Experience DocGen Package Designer (LEDD)

• New Validations Rules for Relationships Aliases.

• We have implemented validation rules and visual indicators when creating relationships that can be aliased, these rules will help prevent issues in the docgen process that can occur with tags and data fill conflicts. The following are now enforced when working with Relationships:

  • An Alias is required when two Relationships refer to the same object

  • Aliases can only contain underscores and alphanumeric characters. Aliases must be unique, begin with a letter, not start or end with an underscore, and not contain consecutive underscores.

  • Aliases can not match Object API Names, which mostly applies to Salesforce Standard Objects. Examples of Salesforce Standard Objects are, but not limited to, the following: Account, ActionPlan, Address, Case, Contact, Contract, Leads, Opportunity, User.

  • Aliases must be unique, you cannot use the same alias for multiple relationships within a DocGen Package.

• The DocGen Package Metadata Panel now displays Created and Modified info for Relationships and Templates.

• Removed the record Created By, Modified By, and Owner information in the header, this data can found in the new Metadata Panel.

• Objects with no label, such as ChannelProgramMemberFeed will now display their API instead for all appropriate picklist's, such as when creating Relationships.

• Apex Data Relationships will now display as errored if their associated Apex is class has been removed/deleted, or if the Object configured in the relationship is no longer available.

• Starting Objects will no longer appear in picklists when creating new Relationships from Other Objects.

• Added informational popover messages when creating Relationships from Other Objects for cases when they have previously added an Object for the one they are selecting, or the desired Object has been used in another type of relationship (SOQL, Apex, Stand Alone).

• Editing a DocGen Package template from Optional to Advanced Optional in Classic will no longer result in that template always showing as optional when generating documents, they will now correctly be evaluated according to the Advanced Optional logic and displayed at the appropriate times.

• Creating DocGen Packages in LEDD with Availability that has Profiles and Roles configured, the Security Type is not correct set to "Match Profile OR Role", previously this was set to an "AND" which meant an End User had to have both the Profile AND Role to view the DocGen Package. Remediation steps in case a customer comes across this: Edit the docgen package in Classic and set to "Match Profile OR Role."

Performance improvements and resolved issues

• In the Salesforce Mobile app, when generating documents using a button or action, the download link no longer results in a blank page and no downloaded file.

• Removed unnecessary text artifacts that showed up when using the Drawloop DocGen Lightning Component in Salesforce Mobile.

• Resolved an issue that caused errors running docgen packages that included a form when the User's language was changed to a non-English language.

• Security Fixes

Performance improvements and resolved issues

• Resolved that caused the content of one component group to places in the middle of another that contained a list if their tags were placed immediately next to each other in a template file.

Performance improvements and resolved issues

• Generated documents sent to SignNow should no longer error.

• Security Fixes

New features

Lightning Experience DocGen Package Designer (LEDD)

• For DocGen Packages with two (2) or more document templates, you now have access to a Sort Mode for easier re-arranging the order of your templates.

• Introducing a new DocGen Metadata slide in panel, with access to the Record Ids, and Created, and Modified information for your DocGen Package and Delivery options. This will greatly assist DocGen Designers and Salesforce Admins when configuring Process Builder or Flow workflows that make use of our Run DocGen Apex Action.

Performance improvements and resolved issues

• Following the Salesforce Spring '20 release, there was an issue when creating new relationships due to the selection for Repeat By not actually being set correctly. We fixed that issue, you're all good to create your relationships again.

Other Updates

• Customers utilizing the RunDocGen Package Apex Action in their Salesforce Flows will now have access to a new Record IDs field. The Record IDs is available for submitting a batch of records id to generate documents, and accepts a Text Collection Variable.

• The convertAndMerge method in our DocumentServices Apex class is now supported for cases when DocGen runs are initiated in Salesforce Lightning.

• Removed an unnecessary permission for Visualforce page templates that would cause docgen runs to fail.

• Resolved an issue where some DocGen Users who did not have access to a handful objects and fields in our application caused an error to surface when attempting to generate document with our Lightning Components. The appropriate access to those objects and fields are now part of our bundled permission sets.