When to use fragments

Create fragments when you identify form content or a script that you intend to use in multiple forms. Fragments allow you to quickly create or change common elements that you want to share with multiple form authors. A company logo is a good example of content that you use in multiple forms. Changes to the logo are simplified because you make a single change in one place, which is the fragment file.

A script fragment is also useful where a function defines a standard way of formatting or doing some type of calculation.

Content reuse

You can use fragments to reuse content in multiple form designs. When you must use some of the same content in multiple forms, using a fragment is faster and simpler than copying or re-creating the content. Using fragments also ensures that the frequently used parts of a form design have consistent content and appearance in all the referencing forms.

Global updates

You can use fragments to make global changes to multiple forms only once, in one file. You can change the content, script objects, data bindings, layout, or styles in a fragment, and all XDP forms that reference the fragment reflect the changes. To update a fragment in a PDF form, resave the form in Designer.

For example, a common element across many forms can be an address block that includes a drop-down list object for the country. If you update the values for the drop-down list object, you must open many forms to make the changes. If you include the address block in a fragment, you open only one fragment file to make the changes.

Shared form creation

You can use fragments to share the creation of forms among several resources. Form developers with expertise in scripting or other advanced features of Designer can develop and share fragments that take advantage of scripting and dynamic properties. Form designers can use those fragments to lay out form designs and to ensure that all parts of a form have a consistent appearance and functionality across multiple forms designed by multiple people.


If you have Designer and Workbench, you can use the LiveCycle repository to limit access to a fragment and to store and share fragments.

// Ethnio survey code removed