Flowed Form Strategy Form Services uses Adobe LiveCycle in conjunction with Adobe form fragments to create forms. However, to successfully maximize the capabilities of these technologies, forms must be able to flow dynamically when fragments are revised. To accomplish this, Form Services has developed this Flowed Form Strategy. Please note, this document will be updated as business needs and Form Services standards evolve. It is important to note that the following rules must be used alongside the existing Form Design Standards and Guidelines and Design Standards & Guidelines: Field definitions. Here are the links to those documents: Standards and Guidelines: https://eforms.metlife.com/wcm8/OIDAction.do?OID=51813 Field Definitions: https://eforms.metlife.com/wcm8/OIDAction.do?OID=52978 LiveCycle Set-up Rules These rules are specific in their settings and numbers and form designers should adhere to them in all cases. 1. Master pages a. Main content area i. Are you creating a completely new form or modernizing a form in LiveCycle? 1. Same size for all pages 2. Margins should be 0.875" left/0.75” top & right/1” bottom 3. Rename the master pages in the hierarchy to include the form’s form number. If the form number contains spaces, special characters, or dashes, convert these to an underscore (“_”). a. If the form number begins with a number, add “F_” to it as a prefix when renaming the master pages, as LiveCycle will not allow hierarchy names to start with numbers. When you open the template, they are generically named as “FormNumber_Master,” “FormNumber_M_A,” and “FormNumber_M_B.” For example, on the DEBITAUTH- 05 form, you would rename the master pages to “DEBITAUTH_05_Master,” “DEBITAUTH_05_M_A,” and “DEBITAUTH_05_M_B.” ii. Are you converting an existing LiveCycle form to the flowed format? 1. Same size for all pages 2. Margins should remain as is on the existing LiveCycle form. Please note, if you still choose to use one of the LiveCycle Flowed Templates, you MUST adjust the form margins to match the existing form. 3. Rename the master pages in the hierarchy to include the form’s form number. If the form number contains spaces, special characters, or dashes, convert these to an underscore (“_”). a. If the form number begins with a number, add “F_” to it as a prefix when renaming the master pages, as LiveCycle will not allow hierarchy names to start with numbers. When you open the template, they are generically named as “FormNumber_Master,” “FormNumber_M_A,” and “FormNumber_M_B.” For example, on the DEBITAUTH- 05 form, you would rename the master pages to “DEBITAUTH_05_Master,” “DEBITAUTH_05_M_A,” and “DEBITAUTH_05_M_B.” b. Footer i. Are you creating a completely new form or modernizing a form in LiveCycle? 1. Actual footer information (e.g., form number) placed on every master page 2. Sizing and placement – follow FS Design Standards 3. Add “/f” directly after “Fs” insignia a. MetLife form – “Fs/f” b. NewCo form – “Fs-B/f” c. If the form does not contain “Fs” in the footer, it must be added. Place it on the same baseline as the form number, and flush against the right margin. If there is a form number and/or date in the bottom right footer, the “Fs” is placed after that. Ex: FORM-NUMBER (XX/XX) . FORM-NUMBER2 (XX/XX) Fs/f d. If the form contains an older version of the Form Services insignia (“FF” or “eF”), simply change it to “Fs” and add the “/f” after it. Ex: eF becomes Fs/f ii. Are you converting an existing LiveCycle form to the flowed format? 1. Actual footer information (e.g., form number) placed on every master page 2. Sizing and placement – follow the existing form 3. Add “/f” directly after “Fs” insignia a. MetLife form – “Fs/f” b. NewCo form – “Fs-B/f” c. If the form does not contain “Fs” in the footer, it must be added. Place it on the same baseline as the form number, and flush against the right margin. If there is a form number and/or date in the bottom right footer, the “Fs” is placed after that. Ex: FORM-NUMBER (XX/XX) . FORM-NUMBER2 (XX/XX) Fs/f d. If the form contains an older version of the Form Services insignia (“FF” or “eF”), simply change it to “Fs” and add the “/f” after it. Ex: eF becomes Fs/f c. Logo i. Are you creating a completely new form or modernizing a form in LiveCycle? 1. Follow design guide standards for size and placement 2. Use existing logo fragments whenever possible st 3. Always placed on the 1 master page ii. Are you converting an existing LiveCycle form to the flowed format? 1. Follow the existing form’s layout for logo size and placement. 2. Use existing logo fragments whenever possible st 3. Always placed on the 1 master page d. Forms without barcodes i. Two master pages ii. First master page 1. Applied only to the first page of the form (contains the form header with the logo) 2. Contains the logo in the header of the first master page 3. Overflow - Go to page-level subform for the first page – under pagination, pick content area in the second master page iii. Second master – for all other pages e. Forms with barcodes i. One master page for each page containing a barcode 1. Naming convention for master pages: eApp >> FormNumber_Master >> FormNumber_M_A FormNumber_M_A, FormNumber_M_B, FormNumber_M_C, etc. a. “FormNumber” = the form’s actual form number (e.g., ENB-7-07) b. “M_A” is incremented according to the alphabet for the 2nd letter 2. Naming convention for content areas on master pages: 3. A_1, A_2, A_3, etc. a. Number is incremented along with the letter in the master pages i. A_1 belongs on master page FormNumber_M_A ii. A_2 belongs on master page FormNumber_M_B iii. Etc. ii. First master page 1. Applied only to the first page of the form (contains the form header with the logo) 2. Contains the logo in the header of the first master page 3. Overflow - Go to page-level subform for the first page – under pagination, in After, pick “Continue filling parent” iii. For each Master page, on the Object palette, on the Master Page tab, make sure “Restrict Page Occurrence” and “Max:” are both checked, and “Max:” contains “1” in the field. iv. NO separate content area on master pages for barcodes 4. Each master page contains the actual barcodes 5. Barcodes are centered in the footer area with other footer information (i.e., form number, pagination) 6. Barcode size – 4.45” width and 0.42” height 7. When importing in LiveCycle, check “Use Original Size” when placing 2. Subforms a. Page level subforms i. Change the name to the form number of form. Convert any spaces, special characters, or dashes, to an underscore (“_”). 1. If the form number begins with a number, add “F_” to it as a prefix when renaming the page level subform, as LiveCycle will not allow hierarchy names to start with numbers. When you open the template, it is generically named as “FormNumber.” “DEBITAUTH-05” becomes “DEBITAUTH_05.” ii. Must be set to Flowed – Top to Bottom iii. Place: Top of Content Area – “A_1” iv. After: Continue Filling Parent v. Do not change any other page-level subform settings except for the ones listed above. This includes margins. Do NOT set margins on page-level subforms. Use the margin settings on the subforms within the form to adjust spacing as needed. b. Check for JavaScript placed directly on page-level subforms. For each page-level subform: i. Click “Show: Events with Scripts” and “Show Events for Child Objects” ii. If any scripts are found that are not referencing the Variables objects, alert lead design. c. First subform on a form (form header area with form title, Things to know, etc.) should be set to Fixed position. d. All subforms after the form header – must be set to: i. Flowed ii. Western-text iii. Allow Page Breaks. e. Subform width i. If there is one subform in one row, its width must equal the width of the content area. ii. If there are multiple subforms in one row, the total of their combined widths must match the width of the content area. f. Subform height – must be set to Expand-to-fit/Auto-fit g. Subform margins i. Top and bottom margins should follow design guide standards (e.g., spacing above a section header). Please note, as much as possible, you should set the margins on all subforms using the Layout Bottom margin option. This will help avoid extra space at the tops of pages. ii. If using multiple elements on a single line, to help with element placement within a subform, the total width of all elements in that subform should be less than or equal to the page width (e.g., 6.875") h. Form sections (e.g., SECTION 1: Client information) should be wrapped in a subform, then other elements or groups of elements within that subform can further be wrapped in their own subforms as needed. i. Each single row of content must be wrapped in its own subform. A “row” is a group of consecutive content of similar height occupying the space between the left and right margins. The simplest example of this is a row of name fields like First, Middle, Last. i. Set to Flowed – Western Text ii. Set to not break – uncheck “Allow Page Breaks.” Please note, this is important because the software sometimes shows the top half of the fields on one page and the bottom half on the next page. iii.