| Section | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
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
For example, your 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 You have mapped an English PDF and a Spanish PDF. Create the precondition in the Precondition property for the English PDF. Type the JavaScript into the field
...
With this precondition in place, the English verison version of the PDF is generated when the user selects the English option for a Radio control named Language.
...
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
...