How to exclude objects on a master page from the tabbing order sequence

When customizing the tabbing order sequence between objects on a form, you may sometimes want to exclude certain objects on the master page from the sequence, but without using the Protected option on the Value tab to do so.

You can do this by applying a setFocus method on the objects you want to exclude. The script excludes an object by changing the focus to the next object in the sequence. That is, when you tab to an object on which the setFocus script is applied, the script automatically executes and moves the focus to the next object.

For example if you have a Button object on the master page that is not protected, you can apply the following JavaScript on the onEnter method.

xfa.host.setFocus(this.parent.nextButtonInTabSq);

Keep in mind that the setFocus method configures the object to always jump to the scripted target; the object will no longer be included in the tabbing order displayed on the Tab Order palette.

To learn more about Scripting, go to the LiveCycle Designer ES Help and search for Scripting.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

3 Responses to How to exclude objects on a master page from the tabbing order sequence

  1. E. Loralon says:

    I am a beginner with Adobe Livecycle designer 8.2 and I am trying to do two things with a flowed form that I have. I have the follwoing two questions.1) On a flowed form can I force to position a field in particular place at runtime?2) Is there a way to exclude an object placed on the master from being remerged or reset? I have a form with a data field on the master page, which gets reset every time the form reloads causing the said field to loose its data.

  2. Drew Brazil says:

    E. Loralon,Thank you for your questions. I’ll need to do some investigating before I can give you an informed response. I’ll get back to you as soon as I have the answers. Thank you for your patience.

  3. Drew Brazil says:

    E. Loralon,In response to your first question, you can place the field inside a suborm that is set to position content. However, the subform will move up or down in the form according to the amount of data that needs to be displayed. As a result, you’ll need to do some testing to determine where the field will end up. Also, when a subform is configured to position content, you must test your form design to make sure that any objects within the subform that you expect to expand in response to data merging do not interfere with other objects in the form design. Remember that any objects you configure to expand, such as text field objects, can possibly overlap other objects when the form is rendered. Alternatively, you can place the object on a master page.As for your second question, I’ll need to know more details about your form. Where is the data coming from? Is this a default data value or a user entered value? Do you want to preserve an initial default value?