| Section | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
Clicking on the edit form/flow View and Generated Forms View icons on the toolbar toggles between the two views.
| Note |
|---|
You will not see the |
Click the icon to display the PDF forms view for your form/flow. Existing PDFs (if any) to be generated for the form/flow will be listed. For example, the Employee On Boarding form shown below will generate a pixel perfect PDF for the federal W4 and the I-9 Employment Eligibility Verification form when the Employee On Boarding form is submitted or the Form Viewer control is clicked.
A status of existing pdfs (if any) will be reported using three icons.
...
The uploaded template will be added to the list of the PDFs to be generated.
Click the 
icon to edit the template name. If you do not select a file and you try to submit this screen, you will see the message "Form Template file is Required".
...
Click the Map Fields icon to begin:
In the forms designer only, the following message will display when you click on the Map Fields link:
...
The PDF view screen is divided into three areas: the form/flow properties pane, the Mapping Form Outline and the PDF forms editor canvas.
Notice the orange color when you are dragging a control from the Mapping Form Outline over a mappable area on the pdf. Drop the control onto the pdf when you see color change to orange.
...
Non-mappable control types can be dragged, but you will not be able to drop it on any PDF field. The image shows the Allowance fields from the Live Form/Flow mapped to the corresponding fields on the W - 4 pdf.
Repeat for all mappable controls on all the pages of the template.
...
Map each option to the pdf using the drag and drop or mapper dialogue. Notice the options are listed using the Control Name.OptionName format:
Sometime, you may wish to map to the entire control instead of the individual options. For example, the dropdown control in the image is mapped to the whole control in the pdf. Any choice selected by the user will be mapped.
...
A simple work-around is to put a control by the same name into the second form and uncheck the visible property. Then add the same rule to the second form to populate it. Workflows designed using Linked Activities, should not exhibit this behavior. Linked steps in flow are like a single form broken into pieces. Flows using this design pattern have a single schema which includes fields from all its steps. So when fields from a flow are mapped to a PDF, there is nothing like future fields from the PDF point of view. It is mapped to the controls in a single schema or document.
Adobe Reader Issue with Grouped Check Boxes
...