Fragments tips

When working with fragments, keep in mind the following points:

  • Because fragments are used for content reuse, keep them generic enough so that they do not quickly become unusable in some forms when changes are made to it.

  • When changing a fragment, verify whether you must also change the following items:

    • Digital signatures that sign a collection that includes the fragment file.

    • Update the schema for the fragment or host form to accommodate the changes.

    • The form design layout of the host form to ensure that the changes did not cause errors. More work may be required to complete the change to the host forms. If you are not using the LiveCycle server to generate the PDF files on demand, manually open each form design and resave it as a PDF file in order for the fragment changes to appear. If the PDF files are generated by using the LiveCycle server, the fragment references in the host form design are resolved before the form is rendered so that no additional effort is required.

  • When placing fragments on a master page, leave consistent space between the page border and the fragments to maintain consistent margins.

  • When creating the fragments, such as the body of a letter, consider the spacing you want between each paragraph. Then make the spacing part of the static text object that contains the paragraph or part of the fragment subform itself (where the fragment subform has a greater height than the static object it contains). When the paragraph fragments are flowed into the body pages, they are consistently spaced. The easiest way to add spacing is to use the Paragraph palette and define the spacing on the static text object.

  • When creating paragraph fragments that contain floating fields, always ensure that they are wide enough to allow for arbitrary data width. For example, make the salutation of a letter as wide as the page so that it can accommodate long names.

// Ethnio survey code removed