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. Use the margins on the subform to space each row properly. (e.g., if a row of fields sits below it, the bottom margin spacing would be 0.075”) iv. Make sure to avoid overlapping boxes on elements in a row. The software has issues with tabbing and other functionality if boxes overlap too much. You should build the row piece by piece so each element ends where the next element begins. For example, instructions, caption, percent field, percent sign, and additional helper text should all occupy their own horizontal space as they are placed on the row in proper order. j. When you must arrange elements within a subform such that flowed western text does not work, you can set that particular subform (NOT the page level subform) to fixed position, then you can arrange the elements inside the subform as you need. Please be aware, you should only do this when you cannot create the layout you need with the particular subform set to flowed. Setting a subform to fixed position will necessitate more manual control of its elements when any changes are needed. k. When you must Keep content together and not allow page breaks – group it all in a subform and make sure "Allow Page Breaks" is unchecked. l. When content must be kept on its own page within the flow of a form (e.g., a page of fraud warnings that should not “flow”), adjust the first element of content that begins the new page: i. Wrap it in its own subform. ii. Pagination – Place: Top of Next Page

3. Barcodes a. Place in the barcode footer area on each master page. i. Bring in as a new Image Object (NOT an Image Field) on every page ii. Bring in at original size b. Correct size: i. 4.45” width ii. 0.42” height c. For barcode creation, use the “Barcode Conversion_052416.pdf” document. It is located at: Designer Writeable\_Masters\Barcodes d. When you need a barcode: i. Check the barcode folder located at: Designer Writeable\Final Logos\LAR Barcodes If you find what you need in this folder, you may proceed. ii. If you cannot find the barcodes in the above folder, then you must create the barcodes using the “Barcode Conversion_052416.pdf” document and the business supplied doctype number. Please note, if you do not have a doctype number, then the requestor must first reach out to Ray Redlinger and the Service Solutions & Technology Delivery group to acquire one, then we can search as described above and, if necessary, create the barcodes.

4. Tables a. Do NOT wrap tables in subforms. A table in LiveCycle is already a parent subform containing all the rows in that table. b. Header rows i. Must be uniquely named. 1. If you create a fragment from the table, or the table is already part of a fragment, use the fragment name (following the Fragment SOP instructions) in the naming convention. As an example, the table header on a fragment named “individualAnnuities_Funds- g_012_a” would be named: TH_individualAnnuities_Funds-g_012_a 2. If the table is not part of a fragment, use the form number and number (count) of the table on a form in the naming convention. As an example, the table header on the 4th table in form ABC-FORM would be named: TH_ABC-FORM_4 ii. Set header rows as table leaders so they always appear at the top of a page when the table breaks across pages. 1. Ensure the correct row is set as the header row on the Object >> Row palette. 2. Highlight the header row and on the Object >> Pagination palette, check both “Include” options: a. Include Header Row in Initial Page b. Include Header Row in Subsequent Pages c. Special Cases – If you must build a table from a group of separate subforms and/or fragments (e.g., 10 fragments each containing several rows of the table): i. Wrap all the fragments in a parent subform. ii. Name the new parent subform in the hierarchy. iii. Click the subform or fragment that represents the header row on the table. 1. On the Object >> Subform palette, set “Content:” to the “Positioned” option. 2. On the Object >> Binding palette, check “Repeat Subform for Each Data Item” and then Check “Min Count:” and ensure it is set to “1” in the field. iv. Click the parent subform. On the Object >> Pagination palette, under “If Dataset Must Be Paginated” in the “Overflow Leader:” drop-down, choose the subform or fragment that represents the header row. Please note, the dental forms represent an example of such a special case. Each one contains numerous fragments, which together comprise one long table that spans multiple pages. d. Page Breaks i. Down-Only Tables – require a user to read downward through each row: Table subform – check “Allow Page Breaks” to allow the table to break across pages. Please note, when a table is set to break across pages, and the form containing it is changed in any way, you MUST include a check on the table as part of your QC process, as increasing or decreasing content may result in the table header row sitting by itself at the bottom of a page. Example of a Down-Only Table ii. Down-Up Tables – require a user to read downward through one set of rows, then back up to the right again to read downward through another set of rows. This process can contain 2 or more sets of rows that require the user to read back up to the top: Table Subform – Uncheck “Allow Page Breaks” to stop the table from breaking. Example of a Down-Up Table

5. Checkboxes a. First checkbox option (or row of checkbox options) and their instructions (e.g., Check only one) must be kept together: Wrap the instructions and the first checkbox option (or row of checkbox options) in a subform and make sure “Allow Page Breaks” is unchecked. b. 4 rows or less of checkbox options – wrap all rows in a subform and do not allow page breaks. c. 5 rows or more i. Wrap all rows in a subform and allow page breaks. ii. Wrap the last two rows in a subform within the main checkbox subform and do not allow to break on those two options. Please note, if the last two options combined have more than 4 lines of text, do not wrap the last two options in a separate subform. Instead, allow page breaks on all checkbox options in the group.

6. Paragraphs/Questions (text only) a. Use a text box and on the Layout palette, set Height: Expand to fit. b. 4 lines or less – do not allow page breaks on text box. c. 5 lines or more – allow page breaks on text box. Ensure LiveCycle “Window and Orphan Control” is checked (2 places) i. File >> Form Properties >> Formatting >> Pagination ii. Tools >> Options >> Formatting >> Pagination Settings for New Forms

7. Large blocks of text a. Do not use 2 columns. All large, uninterrupted blocks of text should be set in a single column. i. If you are creating a new form, simply set the text in a single column. ii. If you are converting an existing LiveCycle form to flowed format, be sure to convert any blocks of 2 column text to a single column, to ensure the text will flow correctly across pages. b. The only exception to this is if the 2 columns of text reside on a page of content that is set to always start at the top of its own page, and the 2 columns of text fit completely on that page. See section 2.l. on page 3 for how to set a page like this.

8. Asterisk statements a. Place directly under the main piece of content which contains the initial asterisk that references the statement. i. If not already in one, wrap the statement in its own subform ii. Place the statement subform inside the subform of the main piece of content, which may be either a table, fragment, or basic subform. Please note, if the main piece of content is not already in a subform, you must wrap it in one so you may place the asterisk statement subform inside it. Important – Before changing a fragment, please consult with Lead Design. b. On the subform of the main piece of content, on the Object >> Palette, choose the asterisk statement subform as the Overflow Trailer. c. On the asterisk statement subform, on the Object >> Binding palette, check “Repeat Subform for Each Data Item” and “Min Count:” and ensure there is a “1” in the “Min Count:” field. Main content area selected below, named “asteriskSection” (initial asterisk statement in the Section VI header)

Asterisk statement subform selected below, named “asterisk” (at the bottom of the main subform, repeated)

9. Overall formatting of content a. The same content in the same order should appear on each page after conversion to the flowed format as on the original form before conversion. b. All content on a form converted to flowed format should be very close to its original position on the form before conversion. Please note, content will shift very slightly when converting to flowed format, but as stated above, the placement of all content should be very close to its position on the original form. Flowed Form Strategy

Content Breaking Rules The rules in this section target specific types of content that may be encountered on MetLife forms, and are intended as a supplement to the more technical LiveCycle rules in the previous section.

There are two basic types of breaking rules – Should Break and Cannot Break. 1. “Should Break” content represents form elements that will be allowed to break across pages when they do not fit on the current page. 2. “Cannot Break” content represents form elements that will move completely to the next page when they do not fit on the current page.

Content Types and Their Breaking Rules

1. Sections

a. Sections – Should Break

b. Section Header and first object/element/row of content in the section – Cannot Break

Please note, while a section generally may break across pages as space dictates, the section header and first row of content in that section will not break, moving as one unit of content from page to page.

2. Tables

a. Down-Only Tables - Table rows – Should Break

b. Down-Only Tables – Table header and 1st row of fields/content in the table – Cannot Break

Please note, when a table breaks across pages, the table header should be repeated so it appears with the row or rows of the table that begin on the new page.

c. Down-Up Tables – Entire table – Cannot Break

3. Paragraphs (text only) a. Paragraphs that are 4 Lines or less – Cannot Break

b. Paragraphs that are 5 lines or more – Should Break However, there should never be less than two lines on the next page.

4. Questions

a. Questions that are 4 Lines or less – Cannot Break

b. Questions that are 5 lines or more – Should Break However, there should never be less than two lines on the next page.

c. Questions and their answer fields/checkboxes – Cannot Break

5. Signature boxes – Cannot Break

6. Any text that references content directly below it and the actual referenced content – Cannot Break

7. Any elements or content that take up only a single row of space – Cannot Break

8. Checkbox groups

a. First checkbox option or row of options and the checkbox instructions – Cannot Break

b. Checkbox groups that are 4 lines (rows) or less – Cannot Break

c. Checkbox groups that are 5 lines (rows) or more – Should Break However, there should never be less than two lines on the next page.

9. Multiple elements affected by more than one rule - Cannot Break The preceding rules may cause multiple, continuous pieces of content on a form to fall into the “Cannot Break” category as a large whole. For example, a section header followed by checkbox instructions followed by checkbox options all become one large group of elements that cannot break.