Please upgrade the use of static Ids on the formula fields and provide a way to effectively deploy them to rest of the environments. While using a lot of packages, it takes up a lot of manual effort and chances of error missing the ids are more.

allow user to filter available/required 'ad hoc' object types (i.e., files vs feed item).

As it is, the checkbox list of available attachments that DocGen provides includes unhandleable object types that cause errors when selected.

E.g.:
"No Unknown record found matching id: 0D51T00006w0****** (MetadataInvalid)
Include this Error Id if you contact support: b1cd6aff-f788-43e0-8e7f-328112ed3e9d"

The user has to engage in a process of trial and error in order to avoid the attachment options that will produce errors. this becomes unworkable when dealing with large numbers of attachments

Currently you only support sending Classic-view Dashboards to the output file. Please add support for the newer, significantly nicer Lightning components.

There should be an option box i.e. "Stop sending email when no records are found" in the Nintex DocGen package configuration for scheduled report type, and, when it is enabled, the Nintex DocGen should stop sending email to the users. In other words, the Nintex DocGen should initiate mail communication only when the baseline report contains some data.

It would be great if we could use Excel as Middleware to output to another Excel or .csv file. Currently the only options are Word and PowerPoint. My deliverables are .csv

Email 'To' has no filter criteria for lookup - no way to identify the contact for selection based on criteria as there is in Classic. We are told this is standard functionality of this page, but it is having a huge impact on the ability to select the correct contact for email.

We are using person accounts and we need to generate documents and send the emails to person account's email address. But I dont see any contact get populated on the screen because its a Person Account.

Working with parameters is easy at the DDP level but if an end user wishes to pass through parameters as part of their "query" to create a document, their experience isn't as seamless as what it could be.

A common method is to create a Salesforce form but this form is presented in the classic interface.

This request is either to pass parameters directly via the DocGen widget or to work with custom forms using the Lightning interface.

Currently The access is only available for Profiles, Role, Permission Set and Group.
We would like to request you to add access to the Permission Set Group as well.

Allowing OCR to serve as the starting object would allow a user to pull from both the Opportunity and Contact objects for a given OCR. Currently you need to use SOQL to do this.

In Lightning Experience, when selecting an email template to use with the DocGen package, only classic email templates are supported currently. I'd like to switch my org over to using lightning email templates, but can't yet because we rely on them being compatible with DocGen.

In the Docgen template, we have Field codes to dynamically render the text in the Document. we have scenarios where we might wanna download the doc in a word format, rather than a PDF. To ensure that a user can update the doc, we convert the field codes to text. what this does is, it would also remove the hyperlinks, table of contents etc.. it would be nice to have a flag over the field tagger, that could decide whether a respective Field code has to be retained / converted to text...

Allowing for specification of a contact and cell phone number for SMS authentication would greatly enhance the integration with OneSpan.

It would be very beneficial to be able to set some metadata for example, Document Status = Draft when a new document is generated. This is on the ContentDelivery object.

So when the object sets the Status to Approved, and generates a new file, then the metadata should be updated to reflect the Document Status as Approved.

My DocGen Package has an Insert-Update that creates a Task. I'd like that Task's Description field to list data from multiple records related to the main object. Can row replication work for populating Fields, instead of just for templates? Thanks!

On the Salesforce rich text field, if you create text and format using the indent function (either on classic or lightning), when merged into Word the indent of text is not applied in Word.

Have it so all formatting in the Salesforce rich text field equally gets applied in Word like it does for bold, center, etc.

When merging images into a Word document there is no way to control the size of the image when the merged image is of an unknown size. The merged image is resized to be the same dimensions as the placeholder image which means that more often than not you end up with an image with the wrong aspect ratio.

It would be useful if, when merging an image, you can nominate a height or width. DocGen could then resize the image to fit the height/width and preserves the aspect ratio by setting the relevant width/height.