We converted to Files in Salesforce from Notes and Attachments and would like the ability to have files show up first in the Attachments list for the DocGen Package run.

We have a lot of records existing with Note and Attachments, since we are attaching files under Files when you go to loop a DocGen package the files show at the bottom on the list of attachments instead of showing by newest to oldest. In addition, the file order does not order from newest to oldest when it appears

Could you please either create a related area under for Files to sort above attachments or sort by date order (newest to oldest)

Thanks,
Shawna

Salesforce Files (ConventVersion) out of the box supports the ability to upload multiple versions of the same document such that the end user in Salesforce only see the current version of the document.

It would be a useful feature if DocGen when generating the same document more than once would upload subsequent documents as additioinal versions of the initial document instead of creating a new document on each generation.

Our use case is that we use docGen for sending quotes to our customers. We typically go through multiple iterations of a quote with a customer. Each time we send a new quote to a customer we run a docGen package that saves the quote to the record. The issue we have is that we can't easily determine which iteration a quote is since each quote gets uploaded a new separate new document. Instead it would be more helpful if docGen would use Salesforce's versioning system so that each time we upload a new quote, it creates it as a new version related to the initial quote. That way when the Sales rep view the quote in Salesforce they just see one file which is the latest version, but still can also click through to the file to view any previous versions for each revision that was sent out to a customer.

Hi - it would be nice to have a feature that would allow us to populate secured pdfs. We are a financial services company so alot of our PDF forms come from our custodians (TD, Schwab, etc.) in a secured format. In order to populate the form we have to remove the security and form fields and save the file as a plain pdf. Then create a new pdf form and overlay the fields on the plain pdf. These pdfs are constantly updated by the custodians, so this creates a ton of work for our operations department to manage these forms. We'd like to request this be added as a feature to populate as secured pdf forms.

Here are a couple cases related to this issue.

Case 1

https://community.nintex.com/t5/Nintex-for-Salesforce/Populating-Secure-PDFs/m-p/101839#M1439

Case 2

Hi,

At this time there is no way to open secure documents during the Document Generation process. This is due to fact that we do not have anything in our code that allows us password protect documents once they have been filled in. Please let me know if you have any additional questions that I can assist with.

Regards,

Tracy
Nintex Drawloop Support

COMMENT HISTORY

09/20/2019 07:04:11 PM EDT [Tracy]

[Recipients: Nick]

Hi Nick,

At this time there is no way to open secure documents during the Document Generation process. This is due to fact that we do not have anything in our code that allows us password protect documents once they have been filled in. Please let me know if you have any additional questions that I can assist with.

Regards,

Tracy
Nintex Drawloop Support

If a package produces a single document the output filename will adhere to the 'Output Filename' field format.

If the package produces multiple documents in the output the default behaviour is to append the document filename to the end of the 'Output Filename' field format.

Problem arises where you get the output file format convention correct for a single file out but for multiple file it doesnt look right. Alternatively if you structure the output file name format correctly for multiple files it doesnt display the single file as you wish.

It would be great if you could;

• Force a package to structure the output filename to always append the document filename to the 'Output Filename' field format.
• Force a package to adhere to the 'Output Filename' field format for single or multiple output files (if needed)