How to build a button that creates a new page in Acrobat Pro DC?

Not likely.

No. You have to create a separate template for each page.

And no, you can spawn as many copies as you want to all the templates in your file. They don't interfere with one another.

Awesome! So far no problems but of course someone always throws a wrench in the works:

Lets say I have a form that on the second page has an area for comments from (for example) an architect. In past we've used word which everyone has been familiar with and people like the fact that the form field and borders carry over to the next page without them having to do anything. I'm guessing that is not possible with acrobat?

As we are moving towards removing word documents and using pdf's there's pushback because we're trying to reduce the verbosity for easier processing.

-After the reviewer inputs their comments the consultant has an area to include their response, which in word could carry over for  multiple pages as well.

-I wanted to create 2 buttons on the review page. One to add a page for reviewer comments and one for the consultant to add additional comments should they run out of room.

Question: if the consultant wants to add a comments to a document that has already grown to 7 pages (thanks to the reviewer), is it possible to have their comments page be inserted after each page they're commenting on or will all the additional pages be added to the end of the document?

JR_Boulay I have read the tutorial. Maybe I'm losing something from the french to english translation? but it seemed like I followed it. Understanding a lot of it I'm not quite sure. This is not a comfort area for me (obviously). Trying to learn as I go. Actually I used the button and script from the tutorial. Copied it over so there were no discrepancies. but still ended up with the example that I posted above a few comments ago.

gkaiseril  Feb 6, 2017 2:36 PM (in response to Richard DiMaio)

You are creating the blank form and then making that into a template which can be hidden and used to create a new form page.

1. Create the form.

2. Make form into template.

3. Spawn new page from template with form fields renamed.

4 Rename form fields on the generated form to be prefixed "P0.".

5. Hide template page.

So to clarify  The form is 2 different pages. One that involves the scope of the work and the second (and possible additional pages) would be the recommendations from the various architects, engineers, etc..

The second page would have an "add page" button for the reviewers to add additional comments.

So here's a question: If my additional pages are a duplicate of the second page can the second page be the template and NOT be hidden? Every time I add the duplicate to be used for additional pages I get this prompt. I have no idea how the portfolio function works with a fillable form.

here is the script that I am using:

this.getTemplate("page1").spawn({nPage:this.numPages, bRename:true, bOverlay: false});

I read the tutorial and set the bRename to "true", but it still comes through as above.

"BRename: If true, it renames all form fields contained in the model page by adding the prefix P #. Model-name. In the new generated page, where # is the sequence number. So the identical fields do not have the same name on the new pages generated, which allows them to have different contents. Otherwise (false) the identical fields are not renamed in the new generated pages and they share the same content. Of course, this parameter is useful only if the document contains form fields, which is not always the case."

Yes! I got it to work on a clean file! Thank you!

Now I noticed that the button only exists on the first page. How do I get it so that the button appears on each additional page. The form I'm creating will have reviews from construction sites from people from different principles. Some are more wordy than others  so if they need to keep adding pages for their reviews is it possible to have the button appear on each page?

Thank you so much! I copied what was in the files and tried again but each time I put the file in preview and hit the button I get the wheel and then a crash. I'm going to try an unrelated file. Maybe what I've been using has gone corrupt? So frustrating because those sample files work so smoothly and without an issue.

Is there anything out there that gives a tutorial in the latest version of the software? This is interesting but I'm not well versed in javascript and I'm already getting lost in the explanations.

Thanks, I'm going to spend some time with it today and document if it goes wrong and where. I'm sure it's all user error. Unfortunately our IT upgraded us to 2017 without warning or documentation and trying to figure things out with all of my other responsibilities tends to be a bit much. My schedule is clear today to dedicate some time to it!

I've been going through it and I must be doing something wrong because it's not working for me.