cancel
Showing results for 
Search instead for 
Did you mean: 

Nintex Drawloop DocGen for Salesforce - FedRAMP Release Notes

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

Releases

February 14, 2020 - DocGen Engine 16.2

Effective Feb. 14, 2020 at 7a Pacific

 

Updates, Bug and Other Fixes

  • 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

 

November 13, 2019 - DocGen Engine 15.10

Effective Nov. 12, 2019 at 7a Pacific

 

New Features

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

Updates, Bugs, & Other Fixes

  • 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

 

July 11, 2019 - DocGen Engine 15.6

Effective Jul. 11, 2019 at 7a Pacific

 

Updates, Bugs, & Other Fixes

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

 

March 21, 2019 - DocGen Engine 15.2

Effective Mar. 21, 2019 at 7a Pacific

 

Updates, Bugs, & Other Fixes

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

 

Version history
Revision #:
9 of 9
Last update:
‎02-19-2020 03:26 PM
Updated by:
 
Contributors