Relius Documents ASP Doc Editor

Transcription

1 Relius Documents ASP Doc Editor Overview The Doc Editor is included with your license for Relius Documents ASP. This feature allows you to customize document outputs via a specialized version of Microsoft Word and save each of your modifications within the system so they are retained with subsequent rebuilds of the same document. In addition, the Doc Editor allows you to save the modifications for one project to a library so they may be applied to other projects within your system. To summarize, the Doc Editor feature will allow you to perform the following actions: Customize any document that is output from the Relius Documents system with images, formatting changes, and modified or deleted language and save the edits so they appear in the document each time it is regenerated through the application. Save your edits to a library so they may be applied to multiple projects at one time. View a listing of all modifications made across all the projects in your system and remove any number of selected edits en masse. Compare your customized plan language to the default language provided by FIS. Important Information Before You Begin. Please note that use of the Doc Editor requires the installation of certain prerequisites and confirmations of certain settings on each workstation from which you intend to use this feature. It is recommended that you contact your system administrator to perform installations any necessary components before attempting to use the functionality outlined in this document. Items that will require attention are as follows: Microsoft.NET Framework 4: This version of.net Framework is required in order to use the Doc Editor add-in for Microsoft Word. A free download of the installation package is available from the Microsoft Download Center website: Visual Studio 2010 Tools for Office Runtime: This is required for Doc Editor to install properly. A free download of the redistributable is available from the Microsoft Download Center website: Microsoft Word: You must have your own licensed installation of Word (version 2010, 2013 or 2016) in order to use the functions of the Doc Editor. Previous versions of Word are NOT compatible with FIS s Doc Editor plug-in. Word Paragraph Setting: To ensure proper outputs within edited documents, your Paragraph settings within Word during Doc Editor sessions MUST be set for Single line, 0 pt. spacing. To verify this setting, from within the Word toolbar go to Page Layout/Paragraph. On the Indents and Spacing tab of the Paragraph dialog box, be sure the Line Spacing option is set to Single and the Before and After options are set to 0 pt. 1

2 For Internet Explorer Users: If Internet Explorer is your preferred browser, you will need to make sure you have the proper security zone settings in place in order to install and use the Doc Editor feature. These settings are accessed via Internet Options under the Tools menu found within the Internet Explorer toolbar (see examples below). Internet Explorer 8 Internet Explorer 9 or 10 or 11 From the Internet Options dialog box, go to the Security tab. Select the Trusted Sites zone and then click the Sites button. Be sure that doc.corbel.com or *.corbel.com is on the list of your trusted sites. Upon returning to the Internet Options dialog box, be sure the security level for the Trusted sites zone is set to Medium-low or Low. This will ensure that the Doc Editor feature can be installed when initiated from Relius Documents ASP. If you fail to comply with these settings the Doc Editor will not launch when invoked from Checklist Entry. For Firefox Users: If Firefox is your preferred browser you will need to install the.net Framework assistant add-on for Firefox in order to use the Doc Editor feature. A free download of the installation package is available at: Framework-Assistant.shtml 2

3 For Google Chrome Users: If Chrome is your preferred browser you will need to install the ClickOnce extension for Chrome in order to use the Doc Editor feature. A free download of the installation package is available from the Google Chrome web store: Glossary of Terms Doc Edit Doc Edit Library Doc Edit Summary Language Type Locked Paragraph Paragraph Number Any document modifications or deletions created and saved within the Doc Editor feature. Doc Edits for a single project can be named and saved to this area of the system so the same modifications can be applied to any number of other projects residing under your account. Users will need to be given rights to save Doc Edits to the library and/or apply library edits to other projects of the same language type. A summary of all modified and deleted paragraphs for a particular project or library entry. Each product in the Relius Documents system is classified by a language type. This is best described as a set of plan language that is shared amongst the different types of products with which it is associated. For example, all EGTRRA Corbel products (Prototype 401(k), Prototype Profit Sharing, etc.) are classified under the EGTRRA Corbel language type. A paragraph that has been locked by the developer to prevent edits to the text contained therein. Each block of text within every document generated by the Relius Documents system is assigned a unique paragraph number. All modifications performed within the Doc Editor are done so on a paragraph number level. 3

4 Quick Reference Guide The following has been provided for quick reference for accessing the most commonly used functions of the Doc Editor feature. Consult the Detailed Reference Guide section of this document for more elaborate information regarding each of the Doc Editor functions. If you want to. Setup users with access to the Doc Editor functionality Create Doc Edits for a single project Follow these steps: 1. Go to Administration/User Group Setup/Modify. 2. Select the Doc Editor checkbox on the Services tab. 3. On the Doc Editor tab, select the Users in this group can save to the Doc Edit library checkbox to allow users in the group to save Doc Edits for a single project to the library (for use with other projects) 1. Go to Project/Existing and select the project you want to modify. 2. Select Open Checklist from the left-hand menu. 3. Click the Doc Edit toolbar button once the project is opened in Checklist Entry. 4. Select the specific document you want to modify. 5. If this is the first time you are attempting to use the Doc Editor on the current workstation, the system will prompt for installations of the necessary add-in components. Click Run / Yes / Install to all prompts. 6. The Document you want to modify will open in an instance of Word that includes Doc Editor options. 7. To modify a paragraph block: a. Modify text within the paragraph. b. Click on the UNMODIFIED marker next to the current paragraph number. A drop-down will appear that will allow you to FLAG MODIFICATION for the current paragraph block. 8. To delete a paragraph block: a. Click on the UNMODIFIED marker next to the current paragraph number. A drop-down will appear that will allow you to DELETE PARAGRAPH. 9. To undo a modification or deletion: a. Click on the MODIFIED or DELETED marker next to the current paragraph number. A dropdown will appear that will allow you to UNDO MODIFICATION or UNDO DELETION. 10. Click Save and Continue at any time to 4

5 Save Doc Edits for a project to the Doc Edit Library Apply a Doc Edit library file to one or more projects View a listing of all modified and deleted paragraphs across all projects and/or remove edits across multiple documents save your edits and continue working. 11. Click View Edit Summary to view a summary of all the modifications/deletions that have been made to the current document. 12. Click Exit Editing Session to close the document and return to Checklist Entry. 13. Click the Submit toolbar button from within Checklist Entry to receive a final built document that features your edits. 1. Go to Project/Existing and select the project that contains the Edits you want to save to the Library. 2. Click Save Doc Edit As from the lefthand menu. 3. Enter a name and description for the library entry and click OK. 1. Go to Doc Editor/Doc Edit Library 2. Select the desired Library file. 3. Click the Apply to Projects button. 4. Select the Project(s) to which you want the Edits applied and click OK. NOTE: You must resubmit each project to which the edits have been applied in order for the changes to appear within the respective built documents. 1. Go to Doc Editor/Doc Edit Maintenance. 2. You can filter/sort the list by Project Name or Paragraph number. 3. Select any number of paragraphs and click Undo Edit to remove the modification/deletion from the applicable project(s). Detailed Reference Guide 1. User Permissions In order to utilize the functionality provided with the Doc Editor, users must first be given access to the service by someone with Project Administrator rights. Permissions may be granted to one or more users via user group settings. As a subscriber to Relius Documents ASP, your account will be automatically licensed for the Doc Editor service. If you are a project administrator for your Relius Documents system, you can grant users access to this feature by going to the Administration/Project Admin/User Group Setup menu. Select the user group that you would like to grant access to the Doc Editor feature and select the Doc Editor checkbox under the User Group Services list. Every user that is assigned to this user group will now have the ability to modify documents via the Doc Editor assuming their workstation is equipped with a supported installation of Word. Doc Editor Options Once the Doc Editor check box option has been selected under the Services tab for a particular user group, a separate Doc Editor tab will appear (fig. 1). From here you can set certain Doc Editor options for the user group as they relate to saving edits to your account s Doc Edit library. 5

6 Figure 1 Users in this group can save to the Doc Edit Library Check this box to grant the users belonging to the selected User Group with rights to save the Doc Edits for a single project to the Doc Edit Library of the current account. If this box is left unchecked, users in the group will be limited to creating and saving Doc Edits for single projects. Users in this group can apply Doc Edit Library files to one or more projects Check this box to grant users belonging to the selected User Group with rights to apply Doc Edits to one or more projects under your account. If this box is left unchecked, users in the group will not be able to apply library modifications to other projects. 2. Creating Doc Edits To create a Doc Edit you must first open the checklist for the project you wish to modify. To do so, go to Project/Existing and select the project you intend to open from the Project Listing page (fig. 2). Figure 2. Select the project you wish to modify and then click Open Checklist from the left-hand Project menu. 6

7 Figure 3 Make elections to complete the opened checklist. When you are ready to edit a document, click the Doc Edit toolbar button. A list of all the documents that can possibly be generated from the current checklist will be displayed (fig. 4). Figure 4 The application will check for an instance of Microsoft Word 2010 or 2013 or 2016 on the current workstation. If one of these supported versions of Word is not found, you will not be able to proceed. Otherwise, the application will then check for the necessary Doc Editor add-in components. If you are attempting to use the Doc Editor for the first time on the current workstation, you will be presented with a series of prompts relating to the install of the necessary programs on your workstation. Click Yes or Install to all prompts to install the required Doc Editor components. Once workstation setup has been completed, the application will generate the requested document based off the selections within the current checklist and display the output within Word. If you are not presented with the document, check your Windows system tray for an opened instance of Word and click it to display the generated document (fig. 5). 7

8 Figure 5 Modifying Existing Document Language When you have a document open in the Doc Editor, you will notice that virtually each block of text is preceded by a unique system-assigned identifier or number (denoted by hidden text). These paragraph identifiers are common to the same block of text within the current language type. For example, paragraph CS0015 will appear in the Summary Plan Description for every project created using the EGTRRA Corbel language type. While attempting to modify a document, one of the most important rules to keep in mind is that every change you make is stored to the Relius Documents system on a paragraph number level. As such, you will notice that to the right of every paragraph number in the document there is an indicator that denotes the current status of the current block number. To the right of the status indicator there is an additional status field that, when clicked, serves as a drop-down field to change the status of the paragraph (fig. 6). In order to save your edits to the system, each paragraph you intend to modify or delete must be flagged with the applicable status as part of your editing session. Note that for Modified paragraphs, if you make changes within the paragraph block and neglect to flag the modification, the system will automatically flag the paragraph when you save your document prior to exiting the Doc Editor. Figure 6 To make a change to existing language, simply type and/or edit text within the desired paragraph language just as you would with any normal Word editing session. Note that you have all the standard formatting tools of Word at your disposal, including the ability to insert pictures, charts, etc. anywhere within the document. 8

9 Working with Codes Variable Codes Another important rule to keep in mind when performing modifications within the Doc Editor is the existence of system codes that are embedded within most of the paragraph blocks found in each document. These codes are used by the Relius Documents application to pull variable values into the applicable areas of the document based on data entered or elected in the project s checklist. Each code is denoted by hidden text opening (<00Co>) and closing tags (</00Co>) which surround the value that will be pulled into the checklist when the document is generated by the system. Note that if the value or election associated with a code is not present in the current project s checklist, the hidden text code tags will still be displayed without an encompassed value (fig. 7). For assistance in determining how codes correlate to checklist elections, download the language manual for the applicable type of plan from the Current Language section of the Relius Documents support site ( Figure 7 Topics of note as they relate to working with variable codes: You will notice that the same code is used for the same variable value across products of the same language type. This is what makes it possible to save the edits of a single project to your Library so they can be used across multiple projects of the same type. Be sure that any codes associated with a value that you intend to keep are part of a paragraph block that will appear in the final built document are NOT deleted as part of your Doc Editor session. If you wish to delete a code so the associated checklist value does not appear within the paragraph block in the final built document, both the opening and closing tags for the code need to be deleted as part of your modification. Codes may be reused throughout the document as you desire. For example, if you wish to reuse the code associated with the Employer Name value as entered in the project s checklist, you may copy and paste the opening and closing tags into other areas of the document. This will ensure that the Employer Name as entered in the project s checklist at the time of build appears wherever the code has been placed. Numbering Tags Many of the documents generated by the Relius Documents system contain articles or lists that are sequenced with alpha or numeric characters. You have the ability to edit the items in these lists and maintain sequence with the use of numbering tags. Numbering tags are hidden text codes within documents that are denoted by <N0#></N0#> throughout document paragraphs. When a numbering tag is present within a paragraph, the Relius Documents build program will automatically maintain the proper sequence for each of the items in the list. As an example, if you wish to add an item to the middle of a list or group of articles in your document without having to worry about re-ordering the sequence, the easiest way to add your item is to copy an existing item in the list and include its numbering tag as part of the copy. Paste the copied text, including the closing and opening numbering tags, into the desired area of the document. The illustration below depicts a scenario where item number (2) in the existing document has been copied to create a new item in the middle of a list and sequence is maintained through the use of numbering tags. 9

10 As modified in the Doc Editor: <N01>(1)</N01> your surviving spouse <N01>(2)</N01> your children, including adopted children in equal shares <N01>(2)</N01> your custom language <N01>(3)</N01> your surviving parents, in equal shares As resolved in the final document: (1) your surviving spouse (2) your children, including adopted children in equal shares (3) your custom language (4) your surviving parents, in equal shares Reset Codes You can reset a sequence of list items or start a new sequence by inserting a reset code at any place after the last numbering tag in the preceding list. Reset codes are hidden text codes with documents that are denoted by <R0#> throughout document paragraphs. When a reset code is present within a paragraph, the Relius Documents build program will automatically reset sequence at the next instance of a numbering tag. The illustration below depicts a scenario where a sequence is restarted in the middle of an existing list. As modified in the Doc Editor: <N01>(1)</N01> your surviving spouse <N01>(2)</N01> your children, including adopted children in equal shares <R01> Your custom language <N01>(3)</N01> your custom list item <N01>(4)</N01> your surviving parents, in equal shares As resolved in the final document: (1) your surviving spouse (2) your children, including adopted children in equal shares Your custom language (1) your custom list item (2) your surviving parents, in equal shares Deleting Entire Paragraphs You have the ability to flag an entire block of text for deletion to ensure that all of the language contained within the block does not appear in the final document. To do so, click the status selection drop-down to the right of the number for the paragraph you want to delete and select the Delete Paragraph option (fig. 8). 10

11 The next time you generate the document through the Relius Documents system, the entire contents of the paragraph will be omitted from the final build. To remove the Deleted status from a paragraph, open the applicable document in the Doc Editor and choose the Undo Deletion option. The next time you generate the document through the Relius Documents system, the contents of the paragraph will be included in the final build (assuming the checklist logic associated with the paragraph has resolved as true). Figure 8 Doc Editor Task Pane On the right-hand side of the screen you will see an Editor Task Pane that is specific to the Doc Editor tool. Functions of the buttons within this task pane are as follows: Button/Field Purpose How to Use Add a hidden text comment to a modified or deleted paragraph. View the latest default language for a modified paragraph. Save all your current edits and continue working. View a summary of all edits for the current project in a single document. Regenerate the originally requested document. The Comment functionality is only available for paragraphs with a Modified or Deleted status. If you are modifying an Individually Designed or Prototype-formatted Volume Submitter plan, the Comments you enter will appear in the Nature & Effect statement that the system automatically generates to summarize your changes. Comments will not appear in any built documents outside of Nature & Effect statements. If a new version of default language is available for a paragraph that you have modified or deleted, an icon will be displayed next to the applicable paragraph number. Place your cursor anywhere within the paragraph and click the View Default Language button to view the latest default language within the Doc Editor. When you click this button, the system will determine any paragraphs that have been modified as part of the current editing session and automatically flag each of the applicable paragraphs so they can be saved to the Relius Documents application. You will briefly see each modified paragraph appear on the screen as the system makes these determinations. Once the save is complete you will be returned to the document editing session to continue working. You can view all the paragraph modifications or deletions you have made across all the documents for a project in a single Edit Summary document. Clicking the View Edit Summary button will generate this document in Word for display in the Doc Editor. Modifications you make directly within the Summary will be applied to the same paragraphs within their applicable document(s). This option will regenerate the document you originally chose to modify. This allows you to confirm the appearance of your edits as they will appear in the final built document. 11

12 Exit the Doc Editor and return to Checklist Entry. Using this button is the only way to properly exit the Doc Editor. Exiting in any other fashion will cause the Doc Editor Task Pane to be present the next time you begin a normal Word session. Helpful Hint: Performing a Document Preview upon returning to Checklist Entry is a good way to confirm how your edits will appear in the final document. To do so, click the Doc Preview toolbar button and choose the document containing your edits. Nature and Effect Statements When you use Relius Documents ASP to generate Individually Designed (IDP) or Prototype-formatted Volume Submitter plan documents and you modify or delete the pre-approved language within either of these types of products, you must notify the IRS of the effect of these changes in the form of a nature and effect statement. If the Doc Editor feature is used to perform these types of modifications, a nature and effect statement will be automatically generated as part of your document package. To ensure, you must add a nature and effect comment for each modified or deleted block. The Add Comment button was added to the word processor toolbar to allow you to add nature and effect comments. (The system will not prompt you to add comments.) Any comments you add are inserted in the document as hidden text. The nature and effect statement generates during the build. Note you may not modify the contents of a nature and effect statement from within the Doc Editor. If you open a built document that includes a nature and effect statement, the nature and effect statement is deleted. When you save and close the document, the nature and effect statement is regenerated. If you need to modify a nature and effect comment, you may modify the project's special language to get to the comment. (Refer to the help topic, Modifying a project's special language.) 12

13 3. Using the Doc Edit Library The Doc Edit Library serves as a mechanism for saving and applying the edits for a single project to other projects under your account. In order to name and save Doc Edits to your account s library, your project administrator must first grant you rights to do so through Administration/User Group Setup. Saving Doc Edits to the Library Assuming you have been granted rights to save edits to your account s Doc Edit Library, go to Project/Existing and select the project containing the Doc Edits you want to save to the Library from the Project Listing page. Click the Save Doc Edit As item from the left-hand menu (fig. 9). Note that projects containing Doc Edits are denoted by an icon in the Project Listing grid. You can click this icon at any time to view a summary of all the Doc Edits associated with the project. Figure 9 The Save to Doc Edit Library dialog box is displayed (fig. 10). Figure 10 Save to Doc Edit Library dialog box Fields and Functions Library Name: You are required to enter a name for the Doc Edit you are attempting to save to the Library. Description: Entering a description is optional. Use this field to enter an explanation of the edits you are attempting to save. Available To: All users on this account : Select this option if you want all the users with access to your account s Doc Edit library to see the library entry you are creating. 13

14 Myself only : Select this option if you want to be the only user with access to the library entry you are creating. Click the OK button to save the Library entry. The Doc Edit Library page will be displayed (fig. 11). Performing Actions from the Doc Edit Library Page Assuming you have been granted rights to the Doc Editor service, you can access the Doc Edit Library page by going to the Doc Editor menu and selecting Doc Edit Library. Figure 11 Fields and Functions of the Doc Edit Library Page Doc Edit Name: Displays the name assigned to the Doc Edit when it was saved to the Library. Description: Displays the description entered for the Doc Edit when it was saved to the Library. : If at least one paragraph within the Doc Edit has a new version of default language available, this icon will be displayed in the record. Click on the icon to see the latest default version of the paragraph language as a pdf in a separate browser window. User Name: The name of the user that last saved the Doc Edit to the Library. Modified: The date and time the Doc Edit was last saved to the Library. Language Type: The language type for which the Doc Edit is intended. 14

15 Button/Field Purpose How to Use View a summary of the edits that make up the selected library entry Make changes to the selected library entry Delete the Doc Edit library entry Copy a Doc Edit library entry to create a new library entry Apply the edits of the selected library entry to any number of other projects Select a single library entry and click this button to view a summary of all the edits for the selected library entry as a pdf in a separate browser window. Select the library entry you want to modify and click this button to open a summary of edits in the Doc Editor. When you save your changes the library entry will be updated. NOTE: Modifying a Doc Edit library entry will NOT automatically update the edits for each of the projects with which the library entry was previously associated. If you have projects with Doc Edits that were applied by a previous edition of the library entry and your intent is to incorporate changes made to a newer edition of the library entry across these projects, you will need to re-apply the library edits to the projects via the Apply to Projects button. Clicking this button will delete the selected Doc Edit library entry so it is no longer available in the system. NOTE: Deleting a library entry will NOT automatically remove the same edits across all the projects to which the library was previously applied. Paragraph edits for within individual projects may only be undone through Doc Edit Maintenance or through a Doc Editor session for the respective projects. Select the library entry you want to copy and click this button to open the Save Doc Edit As dialog box. All the edits of the selected library entry will be copied to create another library entry with the name and description of your choosing. Click this button to display a list of all the projects to which you have access that are of the same language type as the selected Doc Edit library entry. Select any number of projects and click OK to apply the edits to each selected project. IMPORTANT ITEMS OF NOTE: 1. If you have recently migrated a set of library files from the Relius Documents PC system, you will need to assign a Language Type to your library entries before attempting to assign the edits to projects. You will be prompted to do so the first time you click the Apply to Projects button with the library entry selected. It is critical when doing this that you select the language type for which the edits were originally created to ensure accuracy within your documents. 2. After you have applied Doc Edits to any number 15

16 of projects, they will be visible within your documents the next time the respective project is submitted for build. 3. If you have chosen to apply Doc Edits to a project that already contains modified or deleted paragraphs: a. The latest edits will be appended to the existing edits. b. If you are applying an edit for a paragraph number that is already part of a project s edits, a confirmation dialog box will be displayed. From here you can choose if you want to proceed with an overwrite of the existing paragraph edit. 16

17 4. Performing Doc Edit Maintenance The Doc Editor feature is equipped with a tool that will allow you to efficiently analyze and maintain all the edits applied across all your projects. This is particularly useful for confirming edits or making determinations about when certain modifications should be removed from any number of projects at one time. If your system administrator has granted you rights to the Doc Editor service, you can access the Doc Edit Maintenance page by going to the Doc Editor menu and selecting Doc Edit Maintenance. The Doc Edit Maintenance page will be displayed (fig. 12). Figure 12 When the Doc Edit Maintenance page is loaded, it will display each paragraph that has been modified or deleted across each project to which you have access. Fields and Functions of the Doc Edit Maintenance grid Project Name: This column will display the name of the project containing the modified or deleted paragraph in the record. If a project features multiple paragraph edits, you will see multiple instances of the project name in the grid. Click the column heading label to sort or you can filter the contents of the grid by specific Project Name value(s) by entering a string of text in the column heading text box and clicking the filter button (fig. 13). Figure 13 17

18 Paragraph Number: This column will display the number of each modified or deleted paragraph across every project to which you have access. If the same paragraph has been modified across multiple projects, multiple instances of the paragraph number will be displayed. You can sort by clicking the column heading label or filter the grid contents by a single paragraph number value using the drop-down box in the column heading (fig. 14). Figure 14 Version: Each paragraph number in the system is assigned a version number. When FIS releases new language for a particular paragraph number, the version for the paragraph will change. In the Doc Edit maintenance grid, the Version column displays the version number at which your paragraphs have been modified or deleted. You can sort by clicking the column heading label or filter the grid contents by a single paragraph version number by using the drop-down box in the column heading. : If FIS has released a new version of a paragraph you have modified, this icon will be displayed in each row for the applicable paragraph number/version. Click on the icon to see the latest default version of the paragraph language as a pdf in a separate browser window. Applied by Library: If a paragraph modification or deletion was applied to a project via a library, this column will display the name of the library edit that was used to apply the change. If the edit was made directly to the project, a library value will not be displayed in the row. You can sort by clicking on the column heading label or filter the grid contents by a single Library name value by using the drop-down box in the column heading. Last Modified: This column displays the date and time the paragraph edit was last updated and saved to the system. You can sort by clicking on the column label or filter the grid contents by a particular date using the calendar control and filter button in the column heading (fig. 15). Figure 15 User Name: This column will display the name of the system user that last saved the paragraph modification. You can sort by clicking on the column label or filter the grid contents by a particular User Name value using the drop-down box in the column heading. Product: This column will display the product associated with the project in the current record. You can sort by clicking on the column label or filter the grid contents by a particular product value using the drop-down box in the column heading. 18

19 Button/Field Purpose How to Use View the edited version of the selected paragraph. Undo the edited paragraph(s) within each selected project. Export to Excel Refresh the grid Click the View Edit button to see the modified version of the selected paragraph in a separate browser window. If you no longer want to omit a deleted paragraph or include a modified version of a paragraph in a project s documents each time they are generated you must undo the applicable edit(s). You can do this by selecting any number of projects/paragraphs in the maintenance grid and clicking the Undo Edit button. The next time you resubmit any of the selected projects, the generated documents will feature the default version of the paragraph. Use the Export to Excel option to offload the entire contents of the maintenance grid to an Excel spreadsheet. Use the Refresh button to refresh the maintenance grid and remove any filters that may have been applied to the contents FIS Trademark Information: FIS and the FIS logo are trademarks or registered trademarks of FIS or its subsidiaries in the U.S. and other countries. All other trade names are trademarks or registered trademarks of their respective holders. 19