Performing Service Operations Using APIs > Rendering Forms > Rendering Forms as HTML > Digitally signing HTML forms

Digitally signing HTML forms
You cannot sign an HTML form that contains a digital signature field if the form is rendered as one of the following HTML transformations:
For information about digitally signing a document, see Digitally Signing and Certifying Documents.
Rendering an accessibility guidelines-compliant XHTML form
You can render a full HTML form that is compliant with accessibility guidelines. That is, the form is rendered within full HTML tags as opposed to the HTML form being rendered within body tags (not a complete HTML page).
Validating form data
It is recommended that you limit your use of validation rules for form fields when rendering the form as an HTML form. Some validation rules may not be supported for HTML forms. For example, when a validation pattern of MM-DD-YYYY is applied to a Date/Time field that is located in a form design that is rendered as an HTML form , it does not work properly, even if the date is typed in properly. However, this validation pattern works properly for forms rendered as PDF.
Note: For more information about the Forms service, see LiveCycle ES Services.
Summary of steps
To render an HTML form, perform the following steps:
1.
2.
Create a Forms Client API object.
3.
4.
5.
 
Include project files
Include necessary files into your development project. If you are creating a client application using Java, include the necessary JAR files. If you are using web services, ensure that you include the proxy files.
Create a Forms Client API object
Before you can programmatically import data into a PDF formClient API, you must create a Form Data Integration service client. When creating a service client, you define connection settings that are required to invoke a service.
Set HTML run-time options
You set HTML run-time options when rendering an HTML form. For example, you can add a toolbar to an HTML form to enable users to select file attachments located on the client computer or to retrieve file attachments that are rendered with the HTML form. By default, an HTML toolbar is disabled. To add a toolbar to an HTML form, you must programmatically set run-time options. By default, an HTML toolbar consists of the following buttons:
Home: Provides a link to the application’s web root.
Upload: Provides a user interface to select files to attach to the current form.
Download: Provides a user interface to display the attached files.
When a HTML toolbar appears on a HTML form, a user can select a maximum of ten files to submit along with form data. Once the files are submitted, the Forms service can retrieve the files.
HTTP URLs to where form data is posted may be specified by setting the target URL using the Forms Service Client API or may be specified in the Submit button contained in the XDP form design. Setting the target URL using the Forms Service Client API resets the specified target URL in the form design to the one specified using the API. If you wish to submit the HTML form to the target URL specified in the form design, then programmatically set the target URL to an empty string.
Note: Rendering an HTML form with a toolbar is optional.
Note: If you render an AHTML form, it is recommended that you do not add a toolbar to the form.
Render an HTML form
To render an HTML form, you must specify a form design created in Designer ES and saved as an XDP file. You must also select an HTML transformation type. For example, you can specify the HTML transformation type that renders a dynamic HTML for Internet Explorer 5.0 or later.
Rendering an HTML form also requires values, such as URI values that are required to render other form types.
Write the form data stream to the client web browser
When the Forms service renders an HTML form, it returns a form data stream that you must write to the client web browser. When written to the client web browser, the HTML form is visible to the user.
 

Performing Service Operations Using APIs > Rendering Forms > Rendering Forms as HTML > Digitally signing HTML forms

Programming with LiveCycle ES (LiveDocs)
Adobe LiveCycle ES Update 1

 

Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/help/000336.html