| Section | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
When mapping selection controls, you will see the name of the control and the options for that control in the mapping choices. The option values will be listed as ControlName.OptionName?. As an example, let's take a look at the Eligibility field on the I-9 Employment Eligibility federal form. A radio control to collect the eligibility status from the new employee in the Employee On Boarding form/flow is shown in the image:
The option/label values for the radio control in the e-form are:
...
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
...