Right now you can specify an Addendum Doc Id Field on the DocGen Package. If you then have a child relationship that contains multiple records that each specify a different salesforce document id, these all get merged onto the end of the rendered PDF

Request is to implement the ability to specify where the document(s) get merged into the final PDF in the case where you do not want to have it go at the end.

The most flexible way would be to have the ability to specify an addendum doc id field on an entry of a doc gen package template. This would let you enter in more than 1 entry and control the positioning of the addendum documents relative to the other documents on the doc gen package.

An example would be a salesforce data situation like:

Account
    Product(s)  
    Office location(s)   

-each product references a salesforce document representing a datasheet for the product
-each location references a salesforce document representing US State specific warranty/regulatory verbage

To represent an order fulfillement document, you could setup a doc gen package that would have DDP files set to be something like:

Cover letter

Product data sheets (would use addendum feature to print product data sheets for each product record under the account)

Invoice

Warranty/regulatory (would use addenum feature to print warranty/regulatory documents for each location under the account)

How to contact us

I was trying to use a table in a document for a client and was saddened to find out that it is impossible to use a SOQL query within the table even when referencing the row object's ID. This feature would be a GAME CHANGER. i.e. My client wanted to show the name of a bundle of products (a custom object model) as a row in a table with all of the other bundles - this part was achieved - but then they wanted to add the subtotal of the individual bundles. To do this, I needed to sum up the total cost of all of the sub-products in the bundle via SOQL, but we were not able to bring this into the table because SOQL queries within table rows are not supported!

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.

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)