Making content accessible by screen reader software.
Select
one of these values:
False:
Do not render a tagged
PDF form.
True:
(Default) Render a tagged PDF form.
Linearized
PDF:
Sets whether to render a linearized PDF form. A linearized
PDF form is organized so that it supports incremental access in
a network environment. For example, a linearized PDF can be displayed
in a web browser before the entire PDF document is downloaded. Select
one of these values:
False:
(Default) Do not render
a linearized PDF form. It is best to use this option for non-web
applications.
True:
Render a linearized PDF form.
It is best to use this option for optimized web applications.
Seed
PDF:
Sets an initial PDF form that is used in a PDF transformation
to optimize delivery. The seed PDF form specifies a customized PDF
form containing only fonts that is appended with a form design and
data. This property is used when the form is opened using Acrobat
7.0 or later. No default value is provided.
Render At Client:
Sets
whether to enable the delivery of PDF content by using the client-side rendering
capability of Acrobat 7.0 or Adobe Reader 7.0 and later. Client-side rendering
improves the performance of the Forms service. This property applies
only to PDF, PDFForm, or PDFMerge transformations. Select one of these
values:
Use Server Default:
(Default) Use the Render
At setting version on the server to open PDF forms rendered by the
Forms service. The Render At setting is configured in Administration
Console. (See Forms Administration Help.)
Use
Form Template Default:
The Forms service determines the form
rendition based on the setting in the form design.
Yes:
A
dynamic PDF form is generated and rendering occurs in Acrobat. Rendering of
a dynamic form occurs only on Acrobat 7.0 or later. No rendering
occurs for earlier version of Acrobat.
No:
A static
PDF form is generated. Rendering does not occur on the client.
Stand
Alone Rendition:
Sets whether the form can be rendered without
state information. State information is used for rendering interactive
forms that require user interaction with the server for submissions.
Select one of these values:
False:
(Default) The form
is rendered without state information and without embedded JavaScript
that runs on the client web browser. The Forms service renders the
form after server-side calculations are performed and the results are
displayed in the rendered form. The results of the calculation are
displayed in the rendered form. Because of the required interaction
with the Forms service, the form cannot be used offline.
True:
The
form is rendered with state information and embedded JavaScript.
The JavaScript code runs on the client with no interaction with
the server. In addition, the form can be used offline.
Form
Model:
Sets the location where scripts that are embedded into
the form are executed. Select one of these values:
Use Form
Template Default:
(Default) The Forms service checks the
form design to determine whether to render the form on the client
or on the server.
Client Side:
The form is rendered
on the client. Server-side scripts should not be used. Scripts in
a form that are run on the server when this option is selected generate
a warning on the LiveCycle Server.
Server Side:
The
form is rendered on the server.
Both Server and Client side:
The
form is rendered on both the server and the client.
XCI URI:
Sets
the URI location of the XCI file to use for rendering. If the root
is not specified, the file is assumed to reside in the location
where the LiveCycle EAR files are deployed.
Client Cache:
Sets
whether the rendered PDF form is cached on the client web browser.
Only forms that are rendered as interactive PDF forms can be stored
in the client web browser cache.
When client caching is used,
the timestamps of the cached PDF form is compared with the timestamp
of the PDF form generated on the server. If the timestamps are the
same, the PDF form is retrieved from the client cache. When the
compared timestamps are different, the server redelivers the PDF form.
Using the cache on the client results in reduced bandwidth usage
and improves performance. Performance improves because the Forms
service does not have to redeliver the PDF form to the client application.
Select one of these values:
False:
(Default) Do not
cache the form on the client.
True:
Cache the form
on the client.
Generate Server Appearance:
Sets whether
the appearance for the PDF form is generated on the server. Appearances
include the layout of fields and graphical elements in the PDF form.
When you generate the appearance on the server, the form is rendered on
the server and merged with data. Generate the appearance when you
want to use the rendered PDF form in a subsequent operation. For
example, if you need to apply a digital signature to the rendered
PDF form on the server, generate the appearance on the server before
applying the digital signature. If the appearance is not generated
on the server, it is generated in Acrobat or Adobe Reader when the
PDF form is rendered on the client, which invalidates the digital
signature that was applied.
False:
(Default) Do not
generate the appearance on the server.
True:
Generate
the appearance of the rendered PDF form on the server.
opens
the Select Asset dialog box. (See 
