| Section |
|---|
| Column |
|---|
| Checking the Save PDF option for a form/flow saves a a PDF image of the form/flow in the ' submission repository. This generated snapshot is a basic PDF rendering of the form/flow. You can generate additional PDFs' as part of your form/flow, if required. For Example, new employees hired by a company are typically asked to fill out federal forms such as a W-4 or an I-9. ' Pixel Perfect PDF generation feature allows you to design a form/flow with fields that capture the information needed and integrate the data from the e-form controls to an acroform PDF. adds all generated PDF forms to the document set of a completed form/flow. See Submissions for more details. 
|
|
...
Click the 
icon to remove the template. You will be asked to confirm the deletion as the template and all field mappings will be removed.
You can set up logic for the PDF via a precondition that will control when the PDF will be generated or it can be used to skip the PDF entirely. For Example, currently the only way to disable a template is to use a precondition that always evaluates to false and it will be skipped.
Let's say you have an English version and a Spanish version of a pdf. Preconditions, in conjunction with Business Rules can be used to determine which pdf is used in the form/flow at runtime.
...
| Info |
|---|
- Skipped activities do not affect PDF's generated by Live Forms. For example, controls in form/flow activities containing default values, that have been mapped in the pdf mapper, will show up in the PDF even if the activity is skipped due to a precondition. Use a form.load rule to set the "initial state" data dynamically instead.
- will not allow the use of an owner or user password protected PDF acroform to be used as a template. It is the the form/flow designer's responsibility to provide an unprotected PDF acroform. There are programs such as PDFescape available to "remove" an owner password from a protected PDF. Simply upload the password protected PDF to PDFescape, then save and download it. The password will be "removed" from the PDF and you will be able to use it as a template.
- A form with mapped pdfs that has been published as a template then is used to create a new form may result in a pdf that is in an error state (red icon). Upload the pdf acroform again to resolve the issue.
- If you are storing submissions on Box.com, be sure to include the file extension in the name of any acroforms uploaded to for mapping Pixel Perfect PDFs.Box will not open any files that do not have a file extension.
|
Preconditions for PDF
You can set up logic for the PDF via a precondition that will control when the PDF will be generated or it can be used to skip the PDF entirely. For Example, let's say you have a form/flow where you want to generate an English version and a Spanish version of a PDF. Preconditions, in conjunction with Business Rules can be used to determine which pdf is used in the form/flow at runtime. The form/flow contains a Radio control named Language that has two options: English and Spanish.
The precondition can be created in two ways. You can type the JavaScript into the field
Image Added
or click the Image Added icon to launch the Precondition Editor to create it. Click this link for the full details about how the Precondition Editor works.
Image Added
When the precondition is built with the Precondition Editor, the expression displays as shown in the image.
Image Added
The Precondition Editor checks the expression for valid JavaScript and displays appropriate error messages when necessary. Preconditions are re-validated when you click the Image Added save and test icon and you click on the Image AddedGenerated Forms icon. If there is an error, the designer is notified and given an option to re-edit.
With this precondition in place, the English verison of the PDF is generated when the user selects the English option for a Radio control named Language.
Step 4 - Map the Live Form fields to the acroform fields
...
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
...