Macromedia live cycle 7.2 Manual
Adobe LiveCycle
Developing Forms for LiveCycle
Installing and Configuring LiveCycle for JBoss
Using dynamic forms with LiveCycle products 114
Using dynamic forms with LiveCycle products
Dynamic forms can expand or shrink to accommodate the amount of incoming data. Dynamic forms
typically include buttons that request form data from LiveCycle Forms. LiveCycle Forms renders the form
with the data and returns it to the client. The client’s browser is refreshed with the form, which has been
expanded or contracted, depending on the amount of new data.
typically include buttons that request form data from LiveCycle Forms. LiveCycle Forms renders the form
with the data and returns it to the client. The client’s browser is refreshed with the form, which has been
expanded or contracted, depending on the amount of new data.
For example, some forms enable users to query a database by specifying search criteria. The returned data
appears on the same form (a subform) in a table. The returned data determines the number of rows in the
table. To submit the query, the user clicks a button, which sends the request to LiveCycle Forms.
appears on the same form (a subform) in a table. The returned data determines the number of rows in the
table. To submit the query, the user clicks a button, which sends the request to LiveCycle Forms.
LiveCycle products support the use of the following types of buttons for dynamic forms:
●
One that updates the data on a dynamic form
●
One that returns a PDF document to a client, who can then can save a local copy of the document or
print the document
print the document
LiveCycle products use specific button names to recognize these buttons. Dynamic forms must use these
button names. You can use the default names, or you can go to the Administrator pages and configure
LiveCycle products to use different names.
button names. You can use the default names, or you can go to the Administrator pages and configure
LiveCycle products to use different names.
Embedding fonts in PDF/A-compliant forms
When creating a form design that is intended for the creation of a PDF/A Level 1B-compliant form when
rendered by LiveCycle Forms, all of the fonts used must be embedded in the form design. If the fonts are
not embedded, the rendered form is not PDF/A Level 1B-compliant, although it is a valid PDF form.
rendered by LiveCycle Forms, all of the fonts used must be embedded in the form design. If the fonts are
not embedded, the rendered form is not PDF/A Level 1B-compliant, although it is a valid PDF form.
Only fonts licensed for a minimum of View and Print usage can be embedded in the form design. The fonts
included in the Font Manager Module meet this criteria.
included in the Font Manager Module meet this criteria.
Property
Default
Description and options
Re-render
Button name
Button name
RENDERAGAIN
The button name that indicates to LiveCycle products that this
button sends a request to LiveCycle Forms to render the current
form again with updated data.
button sends a request to LiveCycle Forms to render the current
form again with updated data.
Print
Button Name
Button Name
PRINTFORM
The button name that indicates to LiveCycle products that this
button creates a PDF document from the current form and returns
it to the end user.
button creates a PDF document from the current form and returns
it to the end user.