We use the mass document feature to send multiple certificates of completion. We would like to ensure that the document looks correct before sending (i.e. that a long name hasn't forced text to overflow to a new page).

Currently, using Reports as a data source only allows you to pull in a tabular column of data (further calculation requires using Excel as middleware). I would like to see the summary row at the bottom of a tabular report be made available as a series of merge fields as well. For example, the current syntax for a report column is <<AnyRangecol1>>; the sum for that column could be <<AnyRangecolsum>>.

We have a custom object which is linked to another custom object, which is then either linked to a contact or an account. When I use the field tagger search function to find an instance of the custom object that is attached to a contact then the field tagger displays the values of the fields for that contact. When I use an object that is attached to an account it doesn't display those fields. I was told that this isn't a bug, but I should submit a suggestion, so here it is!

Where a formula text field has internal carriage returns, i.e. the user has entered
line 1
line 2
line 3
a DDP currently renders that at line 1 line 2 line 3

Salesforce respects the internal breaks and it would be better if a DDP did the same.

This has become an issue for us where the formula field contains an address with multiple lines. Having all the lines flow into one means that we cannot produce a properly formatted address on a letter.

When adding Insert Updates, you are able to select whether the update should take place for all or only specific delivery options.
Similarly, I'd like to be able to specify Form Steps so that they are used for only specific delivery options.
For example, if I'm prompting the user for information that is necessary for sending via email, I don;t need to capture that when sending the document directly to storage

We use DocGen (Drawloop) on Opportunities. The DocGen can create multiple tables great, but there is not way to create a sub-total on each total.
For instance a Quote with Table 1 for Products and Table 2 for Services. We have the ability to make the tables, but we cannot create sub-totals of each table.

Currently, ddp's can only be migrated in an automated fashion once. After that any changes made in the word templates in a ddp have to be made manually in all orgs. This should be automated. The word templates should migrate to qa, staging and to prod (rather than making the changes manually in each template in each org).

It would be great idea to have more options than Now, Today and Tomorrow for date field tags. For example a Today + 14 days field tag would enable the document to not always have to be updated with a future date at every instance of ddp generation

It would be nice to see who clicks on the "Test" button or who last "Activates" a Report DDP. At some random times, my Report DDP will send out when it is not activated, which means someone is clicking the "Test" button on it. It would be nice to track who is doing this.

The update removed flash from salesforce lightning only. My company has not migrated to lightning yet and it would be beneficial if flash was removed from the classic version of salesforce as well.

As is, the lookup relationship type doesn't have much value. It only works in a single record scenario. Please consider enhancing lookup relationships so that if they're part of a table or row the lookup relationship automatically replicates. This would allow us to tag records to reference the correct lookup record.

Today, if a lookup relationship is part of a table or row, all tables/rows only reference the first lookup record making them have very little value.

I have a case where I need to:
1. Compile a document
2. Create a case object
3. Compile a final document with a link to the case that was created.

This is not possible today because the system automatically compiles both documents first and then creates the case. So the final document that should link to the case that was created instead links to the last case that was created on an account. Please update Drawloop to allow us to set the order that items are compiled.

The DDP allows to select document(s) Inclusion Type as Optional, which a user can then select to be included in the document to be merged. However we would like to have also the ability of having these documents marked as optional to "print in a list" in the merged document.
For example we have 2 endorsements marked as Optional:
Endorsement 1
Endorsement 2
when checked we would like them to be listed on the merged document as i.e.

INCLUDED ENDORSEMENTS

Endorsement 1
Endorsement 2

My DDP has 10 template documents. I want to include an attachment from the record but it should appear in between the template documents rather than at the end of the generate document.

Hello,

We are currently sending out a scheduled report with accounts and missing the possibility to use the field update on the package to update a field on all the records in the report.

It is configurable but not working and Nintex Support already confirmed that this is not inteded to work.

Currently the 'Days till Signing Expires' field on the Adobe Sign Delivery option accepts only numerical values which are constants. It should be possible to use the field tagger to reference any field as a value for the same which will allow the users to have dynamic Expiry dates defined for the echosign agreements.

I need the ability to filter to a subset of Files linked to a particular record based off custom fields on the Files

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.

When creating a DDP, we need files across multiple objects to be combined and rendered as distinct pages in a consolidated document. This has been confirmed as a known issue.