Accomplish common Acrobat commands in Designer

Acrobat-based PDF files are generated with Distiller 7 and are PostScript-based. They can include various elements, but are designed to maintain the layout of the original document. PDF files created through Distiller originate from a source application and are typically more focused on maintaining the original layout of the document than gathering data.

Designer-based PDF files are XML-based. They can include various elements but are designed to interact with a data gathering workflow. Although they can maintain the look and feel of a source document, most PDF files are initiated in Designer. Since these PDF files are focused on data collection, they are not image intensive and are laid out to acquire data effiiciently.

AcroForm.api is the plug-in Acrobat uses to create form fields. Designer has it own XFA toolset that is built into the application.

Adobe Technical Support can demonstrate the predefined functionality of fields within Designer. Support is able to explain the predefined functionality and define where additional functionality would be accessed. Support is also able to refer you to additional resources and tools found within the Help guide.

Many of the instructions in this document assume that the Standard tab is available on the Library palette. If you do not have the Standard tab available, then re-create it.

To assist you in converting Adobe JavaScripting to Designer JavaScripting, see Converting Acrobat JavaScript for use in LiveCycle Designer Forms on the Adobe website at http://partners.adobe.com/public/developer/en/acrobat/sdk/AcroJS_DesignerJS.pdf . This guide assists you in determining whether an Acrobat JavaScript can be converted to a Designer JavaScript.

Acrobat and Designer contain methods to link text from one field to other fields on the form. When you maintain a text field name when you create text fields within AcroForm.api, you duplicate information between fields. Designer can bind data to fields allowing fields with the same name to exist with different data. To have the information populate to all fields, bind the data to the entire form (globally).

Note: When you exit the field, the information populates to all other fields with this name and global setting.

Designer has simplified the process of placing images within a PDF file. In Acrobat, you can insert the image as a page of the PDF file. Then, you can use the TouchUp Object Tool to move it to the desired location, and delete the extra page. Another method, within Acrobat, is to use a customer stamp or button to place the image within a form. Designer allows for the placement of images in a much more simplistic manner.

Designer has an image object designed for placing images within PDF files. Before you place images in a Designer form, consider whether the image will be repeated. Designer contains master pages, which allow dynamic placement of common elements. Elements on the master page can appear on every associated body page. Furthermore, creating image links is drastically simplified in Designer. You can link an image field to a file that is not embedded within the PDF. To ensure that the image is viewable from other machines, link to image files posted to a web server. Or, use an image with a relative path.

Tip: If you leave the URL field blank, then users can click the field and select an image to embed within the PDF file. This feature is not supported in Acrobat 6.

Acrobat and Designer support hyperlinks within a PDF file. Acrobat contains a Link tool, which simplifies the process of generating a hyperlink. Designer contains buttons which give you greater control over the function of the hyperlink.

Note: You can use a number of fields to create hyperlinks in Designer.

Note: The , false is case sensitive and causes the website to launch in a new window. Also the semi-colon (;) is required and must be put in to mark the end of the operation.

If you need the website to launch in the same window as the PDF file (when working in a browser), use app.launchURL("http://www.adobe.com");

Acrobat can create links to specific pages, views, or locations within PDF files using the Link tool. Acrobat-based PDF files are not designed to flow dynamically according to the information they contain. Designer-based PDF files can expand or contract according to the information they contain. Since the position of information within a document can change, linking within Designer is different from Acrobat. Designer uses a method known as SetFocus to move the interface to a new location. SetFocus only works with certain types of fields since it was designed to move between form fields.

• To navigate to the previous page, type xfa.host.pageUp();
• To navigate to the next page, type xfa.host.pageDown();

Note: PageNumber refers to the desired current page. Page numbering begins at 0 within Designer. To navigate to page 3 you would need to enter 2 for PageNumber. If a reflowing feature is enabled, then the page number are no longer fixed. Consider using the steps in the To link to a specific location section of this document.

When working with dynamic forms, this method is the most reliable to ensure that the user is viewing the desired information. Furthermore, text fields can be contained within subforms which can be used to help control the flow of elements within the PDF.

Note: Skip steps 2-5 when an interactive field exists in the link destination.

Note: Maintain the naming conventions that Designer uses. The field doesn't allow you to enter characters that violate the naming conventions.

Note: The FormName, PageName, and FieldName can all be acquired from the Hierarchy window. The top of the tree is the FormName. The PageName associated with the page icon the field is located on. The FieldName is highlighted in the hierarchy if the field is selected on the form. Enter the name of the Text Field create in steps 2-5 or the link destination field. Some fields cannot be used as a destination. Furthermore, a master page field can be selected as well by using the master page name from the hierarchy window rather than the page name.

• E-mail Submit button
• HTTP Submit button
• Print button
• Reset button
• Standard button

Acrobat contains a Button tool that allows you to create a button to perform an action, such as submitting a form. Designer comes with a series of predefined buttons. You can automatically add the Print and E-mail submit buttons to a form when you create a form in Designer using the wizard. Additionally, you can add the E-mail Submit, HTTP Submit, Print, and Reset buttons from the Standard tab of the Library palette. You can re-create all of these functions from the standard button although they can require scripting. The predefined buttons were designed to perform a specific function. They do not display code in the Script Editor Field. The XML Source does contain the script used by these buttons. Additional information about these buttons can be found in the help file and in Create Submission forms in Adobe LiveCycle Designer (7.x on Windows) (332289).

Note: You can modify the text displayed on any button by editing the caption and the appearance from the Appearance field.

The E-mail Submit button is designed to create an XML data file attached to e-mail. Once the data reaches that location, you can manually manipulate the data or populate it into a database. You can also set up a script to interpret the data and redistribute it as needed. You typically use a HTTP submit button if you intended to automate the process.

The FormCalc based script used by the E-mail Submit Button is:

<submit textEncoding="UTF-8" audience="mailto:"/>

Note: If a yellow exclamation point appears on the button, then a problem has been detected with the e-mail address. Verify that the e-mail address is entered correctly.

The HTTP Submit button posts the XML data to a HTTP service as a data stream. Use a Standard Button to post data using other protocols such as HTTPS.

The FormCalc based script used by the HTTP Submit Button is:

<submit textEncoding="UTF-8"/>

Note: If a yellow exclamation point appears on the button in the form, then a problem has been detected. Verify that the URL is entered correctly.

The Print button triggers the print command, which will up the print dialog box.

The FormCalc based script used by the Print Button:

<script contentType="application/x-javascript">xfa.host.print(1, "0", (xfa.host.numPages -1).toString(), 0, 1, 0, 0, 0);</script>

The Reset button resets the data in all form fields. To customize which fields the reset button controls, use a standard button and modify it for your intend purpose.

The FormCalc based script used by the Reset Submit Button is:

<script contentType="application/x-javascript">xfa.host.resetData();</script>

The Button is the standard button that is available in Designer. It can be modified to perform various commands, including all of the predefined buttons or any script that require a button to trigger the action.

• Regular: A standard button that typically has a script associated with it for an action. Such as a calculation that is performed when clicking the button.
• Submit: A button designed to submit data. This button is similar to the E-mail and HTTP submit buttons although this option gives you more options.
• Execute: Typically connects to a database for transferring data into and from the form.

• Submit type displays the Submit tab.
• Execute displays the Execute tab.

Note: HTTPS server addressescan be used when the submit type is chosen. Grouping Text Fields with a Submit button within a Subform allows you to control what fields are submitted with that button. Furthermore, you can use scripting to specify the fields that are submitted with the button.

The easiest method for creating basic calculation scripts is to use FormCalc. FormCalc simplifies calculation scripts. In Acrobat, JavaScripting was required to perform simple scripts. Acrobat also contained a Sum function where a series of fields where selected and sum together for a total. Designer offers greater versatility. Below is a series of calculation scripts for Acrobat based PDFs and the related Designer-based PDF calculation using FormCalc.

• Addition, Multiplication, Average, Minimum, and Maximum:

• Simplified field notation:

Note: Simplified field notation requires that all fields be number or percentage formats.

• Other Calculations:

• Basic Subtraction:

Note: Text1 is the name of the first text field. Text2 is the name of the second text field.

• Basic Division:

Note: Text1 is the name of the first text field. Text2 is the name of the second text field.

FormCalc was designed to function with Designer and greatly simplifies scripting math applications within the PDF. Text or numeric fields can be used when doing calculations. People typically find it useful to use numeric fields for the data being entered and the results because it limits unexpected user entries. You would not want to use a numeric field if you intend to use number formatting. Formatting characters such as , and $ are not considered numeric and generate error messages. JavaScripting can also be used within Designer. See the Acrobat Scripting guide available at http://partners.adobe.com for additional information.

Note: Maintain Designers naming conventions. The field does't allow you to enter characters that violate the naming conventions.

• Addition:TextField1 + TextField 2 + TextField3
• Sum: Sum(Field1 + Field2 + Field3)

Note: Designer allows for fields to have the same name but give each instance a different occurrence number. This number appears to the right of the Field Name on the Binding tab of the Object Palette. This unique feature allows you to sum all occurrences of a field with the same name. Type Field1[*]in the script editor. [*] tells designer to sum all occurrences of Field1.

• Average: Avg(Field1, Field2, Field3) or Avg(Field1[*])
• Minimum: Min(Field1, Field2, Field3) or Min(Field1[*])
• Maximum: Max(Field1, Field2, Field3) or Max(Field1[*])
• Subtraction: TextField1 - TextField2
• Division: TextField1 / TextField2

Adding a digital signature field within a Designer PDF file allows a form to be certified. You can create a hidden digital signature field so that it is more transparent to the users. However, it must be signed before the PDF file become certified. When exporting XML data from a designer form the data must be certified first. This change occurred with the 7.0.5 update to Acrobat and Reader.

• Auto-sizing fonts
• Horizontal and vertical font adjustment

Designer has the same functionality for auto-sizing text within a field as Acrobat.

Designer allows for a much greater amount of control over the font alignment and adjustments within a PDF file than Acrobat allows. PDF files generated by Designer are focused more around data collect rather than preserving the exact look of the original file. You can edit the caption and the value of fields separately by selecting the value to edit from the pop-up menu on the palette. PDF files generated by Acrobat offer limited control over any of the settings specified below.

Note: Designer allows you to control various functions. Horizontal and vertical alignment with the text field you have created. Indentations, the type of paragraph indentation and the amount of the indentation, line spacing including the amount of space above and below the line.

Note: You can apply underline, baseline shifts, and strikethrough effects through Font palette.

• Saving PDF files
• Importing Word forms
• Bookmarks
• Embedding fonts
• Editing Designer forms in Acrobat

Take careful consideration of the choices you make when saving a PDF file. The type of PDF file you choose can limit the options available when previewing the PDF. The type you choose also affects the PDF file size, and the level of functionality during the PDF preview.

• -Acrobat 6 Compatible (Static) PDF Form File (*.pdf): Saves forms as Acrobat 6 compatible. You save the form design using this format when users fill the form using Acrobat 6.0 or Adobe Reader 6 Users cannot open LiveCycle Designer forms saved in earlier versions of Acrobat or Adobe Reader. This option generates an Acrobat 6-compatible PDF file. These PDF files do not support dynamic generated material. They don't support expandable text fields, image fields, paper form barcodes, and any reflowing data through the use of subforms.
• -Acrobat 7.0 Compatible Static PDF Form File (*.pdf): Saves forms as Acrobat 7 compatible static. The form design can only contain static elements. For example, if your form has 10 available rows for data, and there is enough data to fill 25 rows, only 10 rows can be filled. The rest of the data isn't displayed. Similarly, if there is enough data for 2 rows, you still see 10 rows, 2 of which are filled with data, and 8 that are empty. This type of PDF also supports PDF417 paper forms barcodes.
• Acrobat 7.0 Compatible Dynamic PDF Form File (*.pdf): Saves forms as Acrobat 7.0 compatible dynamic. The form design can contain dynamic elements. For example, the form design can be a dynamic interactive form that allows users to add or remove item rows. This type of PDF also supports PDF417 paper forms barcodes.
• Acrobat 7.0.5 Static PDF Form File (*.pdf): Saves forms as Acrobat 7.0.5 static. The form design can only contain static elements. If your form design contains dynamic elements, they are unavailable in the form. The same limitations of a 7.0 compatible static PDF apply. This option is only available in Designer 7.1. Some improvements were made to the PDF specification which require Acrobat/Reader 7.0.5 or greater to view correctly. This type of PDF also supports QR Code or Data Matrix paper form barcode in your form.
• Acrobat 7.0.5 Dynamic PDF Form File (*.pdf): Saves forms as Acrobat 7.0.5 dynamic. The form design can contain dynamic elements. For example, if you have a form that contains a dynamic table, all the rows of data are shown in the PDF Preview tab. This type of PDF also supports QR Code or Data Matrix paper form barcode in your form.
• Adobe XML Form File (*.xdp): Saves forms in the native XML-based file format created by LiveCycle Designer. Use this option if you use LiveCycle Forms. The form design can contain dynamic elements. A 7.0.5 static PDF file is rendered when rendering this type of PDF in PDF Preview.
• Adobe LiveCycle Designer Template (*.tds): Saves the basic structure for a form as a template. It can contain components and settings, such as fonts, page layout, formatting, and scripts. Use it as a starting point for a new form.

Designer can import Word forms and retain various fields that have been created in Word. Text fields that are imported in this fashion are imported with the same field name. You sometimes have to supply unique names for the form fields before you can obtain full functionality of the form. Designer also interprets underlines with no text above them as response fields and creates separate Text Field for these items. You sometimes have to manually adjust these elements.

Creating bookmarks within a Designer form requires scripting. Bookmark functionality is available on Form Ready event. To enable bookmarks within Adobe Reader, save Designer PDF files for Commenting in Reader within the Professional edition of Acrobat. Saving the file this way removes form functionality and creates a static version of the PDF file. Designer does not contain the simplified functionality of Acrobat in creating bookmarks. Designer-based PDF files are intended to be rendered from supplied data and can expand/collapse according to the amount of data that is added. Bookmarks are designed to link to a specific page of a PDF file which remains fixed. Although, using scripting you can create a link to a form field which can dynamically flow within the PDF file. Bookmarks can be added to a PDF file within Acrobat but can function unexpectedly. Set up PDF navigation using the Creating Internal Links section.

An example JavaScript that you could use to create a bookmark is:

var myDoc1 = event.target

myDoc1.bookmarkRoot.createChild("LeveransAdress", "this.getField(\"form1[0].#subform[0].TextField1[4]\").setFocus()");

Embedding fonts within a dynamically generated PDF file can cause the file size to increase unexpectedly. Unchecking this option eliminates the problem when you save a Designer PDF file.

You cannot edit Designer forms in Acrobat. The acroform.api plug-in for Acrobat is unable to edit XFA forms created from Designer. Numerous options under the Advance Editing menu are dimmed in Acrobat 7 if the PDF file was created in Designer. The options are not dimmed in Acrobat 6, but corrupt the form if used to editing form fields. Do all editing of forms created in Designer within Designer.