Nintex DocGen for Salesforce - FedRAMP

Nintex performs two types of updates: back-end updates to our DocGen Engine and front-end package updates to the Nintex Drawloop DocGen for Salesforce managed package.

DocGen Engine updates are typically released once a quarter. Package updates are typically released at the end of every month, however new versions may released at any time to address urgent issues.

If you have been testing a recent version of the Drawloop Package in your sandbox or UAT environments, to then discover a newer version is available for install on the AppExchange, you do have the option to reach out to our Support team, we can assist helping to install the version you have verified.

The following release notes will identify enhancements to the DocGen Engine for FedRAMP customers.

Announcements and Release Notes for updated package versions can be found on the Nintex Drawloop DocGen for Salesforce Release Notes page.

For more information, see Install the app. To get the latest version of the app, see Nintex DocGen for Salesforce on the AppExchange.

Note: Any unreleased services or features referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make the purchase decisions based upon features that are currently available.

DocGen Engine release 17.27: 13 June 2024

Performance 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

  • 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

Previous releases

Performance improvements and resolved issues

  • General improvements and minor 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.

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

Performance improvements and resolved issues

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

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

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

  • General improvements and bug fixes.

Updates, 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 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.

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

  • 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 Nintex eSign 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.

  • 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.

  • 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.

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

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

New Features

  • Added support for the Nintex AssureSign Delivery Option.

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

  • 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.

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

  • Optimized processes to acquire licensing data.

  • Updated messaging to enable better error handling.

  • Deprecated Cipher Cloud & Perspecsys support.

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

Updates, performance improvements, and resolved issues

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

  • 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.

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

  • 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.

  • 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."

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

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

  • 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.

  • 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

  • Resolved an issue that caused an error to appear on the Select DocGen Package, but did not prevent initiating the DocGen process.

  • Automated DocGen Package runs using Outbound Messages with SMTP delivery options will now have the appropriate emails sent to DocGen Admins in the event there was an error with that run.

  • 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.

  • 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 NEW templates files added to DocGen Packages following the June 2020 release, previous templates files unfortunately will not have their reference URLs updated.

  • 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.

  • Resolved an issue where sometimes the Mass DocGen Status emails wouldn’t be sent.

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

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

  • 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

  • Automated DocGen Runs that involved Outbound Messaging that may error for some reason will no longer result in XML gibberish when viewing the Outbound Message monitoring request in Salesforce

  • Upgraded to using Salesforce API version 47. This upgrade grants us access to more objects and fields within in Salesforce, allowing for their data to be used in DocGen Packages.

  • Adobe Sign / Nintex Sign delivery options using Adobe Sign Agreement Templates are now supported with the latest version of the Adobe Sign for Salesforce application.

  • Insert-Updates configured using the attachIds tag will now successfully provide the correct ID's, previously updates were missing the ID's completely.

  • Visualforce Page parameters set for DocGen Package Templates using Visualforce pages are working again.

  • Proper error messages will now be provided in cases where Automated DocGen Runs fail due to timeout issues. Timeout issues typically occur due to a handful of reasons, typically with large amounts of data. If you encounter this error please reach out to support for assistance.

  • Errors will now be provided for those rare cases they previously were not in some automatic docgen runs.

  • Updated the error message for URL based template files if the file type can not be determined or is missing.

  • Text labels for "eSignLive" have been updated to "OneSpan Sign" to reflect updated branding by OneSpan (formerly Vasco, eSignlive).

  • Resolved an issue where data suffixes ("3rd", "4th") might be output incorrectly for some locales, there is no such thing as Dec 3th!

  • Resolved an issue that prevented some long running docgen processes to error when they shouldn't have.

  • DocGen Package email delivery options configured to use a Word template as the email body will now successfully have those templates correctly set after migration.

  • Resolved an issue that prevented some LOOP Storage customers from being able to download files.

  • Security Fixes

New features

  • Visualforce page templates can now be retrieved and used as Word .doc files in the document generation process.

Performance improvements and resolved issues

  • DocGen Packages that utilize Word documents for email body templates which include Components Groups that contain bullets with hyperlinks will no longer cause the document generation process to error.

  • Resolved an issue that caused some Right to Left text to be merged incorrectly into documents. Specifically in this fix parentheses "( )" should be placed correctly into documents as intended.

  • Resolved an issue that caused some docgen runs to error when using the Nintex DocGen loopMessage class for DocGen Packages that included Salesforce Reports as document template.

  • Resolved an issue that prevented some generated documents from being saved to Box if the associated Box account a large number of folders with names that are similar or the same.

  • DocGen packages should no longer error for scenarios using our processDdpComponent when you are logged in as another user. Scenarios such as these would surface in cases when you may be testing your docgen packages and need to log in as a community or portal user.

  • Transparent backgrounds are now support for Rich Text Content. This particular update helps in cases when content that contains a transparent background color is copied from another source to a rich text field in Salesforce. Previously the background color would case the document generation process to fail, now your documents will successfully generated with the transparent background.

  • Resolved an issue that prevent some long running docgen processes to error when they shouldn't have.

  • Security updates

Performance improvements and resolved issues

  • The user experience for scenarios involving iPads and Salesforce Lightning Console should be more seamless when running a DocGen Package using a DocuSign delivery option that has "Signing Preview & Edit", or "Embedded Signing" enabled.

  • Added support for userId and sandbox parameters for Drawloop_Next fields used with Outbound Messages, resolving a change in Salesforce Summer '19 that caused some Automated DocGen Packages to fail that included reports or images from rich text fields.

  • Resolved an issue that prevented some Automated DocGen Package runs, initiated through either an Outbound Message or using out Apex classes, to result in an error.

Performance improvements and resolved issues

  • Unordered lists will no longer display a ? or ⃞ symbol for each list item in web-based or modern desktop email clients when using our Email Merge feature. Note: ? or other icons may appear still appear in older desktop based clients due to lack of support for the appropriate unordered list symbols.

  • Removed support for Salesforce Files sync with Pause to Edit. Any DocGen settings currently configured to use Files Sync on the DocGen Admin > Settings page will now default to the Upload option. File Sync support was removed following Salesforce retiring Files Sync on May 25, 2018.

  • Fixed an issue with dynamic hyperlinks for certain rare hyperlinks in Word.

  • Corrected an issue that sometimes prevented strikethrough content in Rich Text fields from accurately shown as strikethrough in generated documents.

  • Added a new error message in case where a template file could not be retrieved during the docgen process.