Settings and activity
267 results found
-
3 votes
Anonymous supported this idea ·
-
6 votes
Anonymous supported this idea ·
-
42 votes
Anonymous supported this idea ·
-
5 votes
Anonymous supported this idea ·
-
2 votes
Anonymous supported this idea ·
-
38 votes
Anonymous supported this idea ·
-
3 votes
An error occurred while saving the comment Anonymous supported this idea ·
-
29 votes
An error occurred while saving the comment Anonymous commented
I have a feature suggestion that would significantly enhance our workflow and efficiency. It would be immensely beneficial if PandaDoc could create a functionality where we can merge input fields from one template to all other selected templates. Specifically, if a merge field name is updated in one template, it should automatically be added to all the templates that we have selected for the update. This update should only occur in the sections specified within each template.
For instance, if I update a text field in a specific section of one contract, I would like the same update to be reflected in the corresponding sections of all selected templates. This feature would streamline our document management process and ensure consistency across our numerous templates.
I believe this addition would be a valuable enhancement to the PandaDoc platform, not just for our startup but for many other users who manage multiple templates.
Anonymous supported this idea ·
-
16 votes
Anonymous supported this idea ·
-
19 votes
Anonymous supported this idea ·
-
58 votes
Hi. We aren’t planning on building this into our feature set at this point in time since it doesn’t fit into our current product roadmap. Please keep upvoting this idea so we can keep considering it every time we work on our roadmap.
Should you come across any other ideas that suit your business needs, don’t hesitate to give them an upvote!
Anonymous supported this idea ·
-
4 votes
Anonymous supported this idea ·
-
3 votes
An error occurred while saving the comment Anonymous commented
Just wanted to recommend that the API return a 404 status code when requesting the details for a document that cannot be found. The currently observed behavior is that it returns a 403.
When I get webhook requests for documents, sometimes a user has already deleted the document by the time a request comes in, in which case I'd like to ignore 404 errors. Since it returns 403, it's not as ideal because there could actually be an issue with our API credentials that would also cause that error (which is something we've experienced in the past).
Anonymous shared this idea ·
-
3 votes
Anonymous supported this idea ·
-
12 votes
Anonymous supported this idea ·
-
4 votes
Anonymous supported this idea ·
-
17 votes
An error occurred while saving the comment Anonymous commented
We work with pdfs with multiple fields, we'd appreciate if it could be possible to make all the placed fields required in bulk
-
3 votes
Anonymous supported this idea ·
Anonymous shared this idea ·
-
5 votes
Anonymous supported this idea ·
-
33 votes
Anonymous supported this idea ·
I want to pull a report of names of who has been sent, viewed, and completed the document