Livecycle

Events that you can reference in a script or calculation  

Server-side scripts

Acrobat and Adobe Reader recognize all the events that LiveCycle Designer ES supports. The client application sends user-initiated events to LiveCycle Forms ES for server-side processing. No other types of events trigger server-side processing. LiveCycle Forms ES performs server-side processing whenever it is rendering a form, executing server events initiated from the client, or processing submitted data.

When you specify that a script or calculation should be run on the server, the following user-initiated events cause Acrobat or Adobe Reader to send the event to LiveCycle Forms ES for processing:

•

exit

•	mouseEnter

•

mouseExit

•

change

•

mouseUp

•

mouseDown

•

click

During event processing, LiveCycle Forms ES runs all the scripts /calculations that are designated to run on the server and remerges the results into the form before returning it to the client application.

If any of these events are referenced in a server-side script/calculation, Acrobat or Adobe Reader ignores them:

•	initialize

•

calculate

•

validate

•

docReady

•

docClose

The following table identifies the events that you can reference in server-side scripts/calculations only. These events are not recognized by HTML client applications.

 

Event	For more information, see
form:ready	form:ready event
layout:ready	layout:ready event

When a script has been designated to run on the server, the click event (of a regular button) is the only event that causes an HTML client to initiate server-side processing. During processing, LiveCycle Forms ES remerges the results into the HTML form before returning it to the client application. All other events are ignored by the HTML client and are executed only when LiveCycle Forms ES performs server-side processing.

Client-side scripts

For client-side scripting and calculations, Acrobat and Adobe Reader support the full list of events that you can define in LiveCycle Designer ES.

However, not all of these events are recognized by HTML clients. If you will be using a single form design to create both PDF forms and HTML forms, your client-side scripts should reference only a subset of the supported events.

If a client-side script references an event that the HTML client does not recognize, the script will stop executing at the point where the unrecognized event is referenced.

You can use the following events to run client-side scripts from HTML forms.

]

Event	For more information, see
initialize	initialize event
enter	enter event
exit	exit event
calculate	calculate event Note: In HTML forms only, activities triggered by calculate events are run when the cursor exits a field. Processing does not start when a user changes a field value, but you can invoke processing explicitly at this time, if required, by using the execCalculate() method.
validate	validate event
change	change event Note: In PDF and HTML forms, this event is supported for drop-down lists and list boxes only.
mouseUp	mouseUp event
mouseDown	mouseDown event
click	click event Note: The click event cannot be used for Submit buttons in PDF or HTML forms. Use the preSubmit event instead.
preSubmit	preSubmit event Note: In PDF and HTML forms, this event is supported for Submit buttons only. When you use the preSubmit event to run a client-side script, processing is done before the data is submitted. If the event runs a script on the server, processing is done while the data is being submitted.

See also 

Where calculations and scripts are run

About scripting in LiveCycle Designer ES

About the Object Scripting Reference

Events that you can reference in a script or calculation