This example fires the execValidate() on the preSave event. If required fields are null, then a warning is displayed. Note that for this example we have not used some of the new features, such as validationState event or the cancelAction method. Therefore it should work satisfactorily in earlier versions of Acrobat/Reader.
While we have listed a number of blogs over on the righthand sidebar, we thought we would spend some time providing more information on why we think these are such an important resource to you. First, we will look at key influencing blogs and then we will outline other online resources. Blogs John Brinkman’s blog FormFeed [...]
A previous post shows how events fire and their sequence as a user interacted with your form. If you explore the form you will see how some events fire quite often, in particular the calculate event, validate event and the form:ready event. The intention of the example is to show that some events fire many [...]
First off – thanks to everyone who came to my session on “What’s new in Adobe Digital Enterprise Platform Document Services Designer 10″ and for engaging in the conversation. Second – thanks to Adobe for delivering such a great conference. It was an honour to present at the conference. I promised that I would share [...]
I will be speaking at Adobe Max in Los Angeles in October. The session will cover the new features in the next version of LiveCycle Designer and how to harness these to generate dynamic solutions. There will be over twenty LiveCycle sessions and labs, which will explore all areas of the platform. Learn how [...]
The Scripting Object Model (SOM) is one of the backbones of the XFA Specification. The SOM provides a structure for referencing objects and properties in our forms. A SOM expression is simply the reference in a script to another object. If the objects are in the same container, then the SOM expression can be as [...]
John Brinkman's FormFeed
LoveCycle Blog
Stefan Cameron on Forms
Technoracle