Events with Sripts

[#1]

Hi,

I want to ask whether anyone can let me know when should I should the following events with scripts and for what purpose?

1. calculate

2. validate

3. preOpen

4. full

5. preSave

6. postSave

7. prePrint

8. postPrint

9. preSubmit

10. docReady

11. docClose

12. form:ready

13. layout:ready

Thanks!

[Former Member]

Hi Shreya,

Process events

Process events initiate automatically as the result of an internal process or action related to a form or objects on a form. These events initiate immediately following significant form changes; for example, after a form design is merged with data or after the form pagination process finishes. Process events also initiate immediately after interactive events initiate. For example, immediately after any interactive event initiates, the calculate event initiates followed by the validate event.

The following list contains the process events, which are available from the Show list in the Script Editor:

u2022 calculate

u2022 form:ready

u2022 indexChange

u2022 initialize

u2022 layout:ready

u2022 validate

Process events can initiate many times as a result of dependencies; that is, actions associated with a single event that ultimately initiates one or more additional events. Using an example of a form filler clicking a button to reveal a previously hidden portion of the form, after the form filler clicks the button, not only does a series of interactive and processing events initiate for the button itself, but a number of process events for the new subform initiates as well.

Interactive events

Interactive events initiate as a direct result of form filler actions, which makes these events useful for a variety of calculation and scripting tasks. For example, you can add a script to the mouseEnter event for a text field that changes the border color of the field to blue and a script to the mouseExit event that changes the border color back to the original color. This action creates a highlighting effect when form fillers move the pointer over the field to visually assist them while filling the form. Interactive events are also useful for changing form data in response to a form filler selection. For example, you can add a script to the change event for a drop-down list that updates the data values in multiple fields in response to the value the form filler selects in the drop-down list.

The following list contains the interactive events, which are available from the Show list in the Script Editor:

u2022 change

u2022 click

u2022 enter

u2022 exit

u2022 mouseDown

u2022 mouseEnter

u2022 mouseExit

u2022 mouseUp

u2022 preOpen

Application events

Application events initiate as a result of the actions that either a client application or a server application performs, either in response to a form filler action or as a result of an automated process. For example, if a form filler saves the form in Acrobat or Adobe Reader, the preSave event initiates immediately before the save operation, followed by the calculate, validate, and layout:ready events, in order, for all objects on the form. The same event sequence initiates if the form contains a script that programmatically saves the form.

The following list contains the processing events, which are available from the Show list in the Script Editor:

u2022 docClose

u2022 docReady

u2022 postPrint

u2022 postSave

u2022 prePrint

u2022 preSave

u2022 preSubmit

Application events do not exist as part of a general flow of events. They are single events corresponding to actions that the client or server application performs.

Hope this helps.