Custom Forms Configuration

You can create custom forms to allow users to capture data for policy lines that do not have a default application detail. This area allows you to enter basic information about a custom form, such as its name and type, and select Common Screens to include with it. Once you have added a custom form, you can use the screen generator to add controls to it and further customize it to capture the information your business needs. To enable users to select a custom form and use it during policy servicing workflows, you must install it and define a policy type for it.

If you have previously used custom forms for benefits policies and would like to begin using data capture forms instead, you can convert a custom form to a data capture form, then migrate existing policies to the data capture form. Existing attachment, summary of insurance, and proposal templates associated to the custom form are updated automatically as part of the conversion. If a custom form contains multiple plans in a single schedule, the system converts policies that use that form to package policies, with each plan as a line of business within the package. You cannot convert a custom form containing multiple schedules to a single plan data capture form.

Data capture forms and related functionality are only available in Applied Epic Browser, and only available if your agency does not have Active Directory Authentication enabled in Login Configuration.

If you access Applied Epic through a web browser, you must install all components from Help > Connection Suite (including the Applied Epic Custom Form Editor item in the Optional Connections section) to configure custom forms. Otherwise, you can only use the Screen Generator with Applied Epic installed locally on your computer.

Note: This article contains printing instructions that are only applicable if Applied Epic is installed locally on your computer. If you access Epic through a web browser such as Google Chrome, Mozilla Firefox, or Microsoft Edge, you cannot print directly from within the system. See Printing for more information about the printing capabilities available from Epic Browser. All other steps in this article are applicable to both methods of accessing Epic unless stated otherwise.

  1. From the Home screen, do one of the following:

From any other area of the program, do one of the following:

  1. Click Policy on the navigation panel or Areas > Policy on the menubar.

  2. Click Custom Forms on the navigation panel.

  3. You can do the following from here:
     

Convert Custom Forms to Data Capture Forms

Converting custom forms to data capture forms is a two-step process. In the first step, you map the custom form’s fields to their counterparts on the data capture form. Depending on your agency’s needs, you can either use one of the six default data capture forms or customize a form in Policy/Plan Detail Builder. Because the conversion is permanent, complete any modifications to the forms you intend to use before you begin the mapping process.

In the second step, you convert all existing policies that use that custom form to use the data capture form instead. Before you run the conversion, review the mappings one last time to confirm that you have mapped all fields that you want to convert. All data in unmapped fields on the custom form will be lost when the conversion runs.

Create Conversion Mapping

Before beginning the mapping process, confirm that every field you want to migrate from the custom form has a counterpart on the data capture form, especially if you have modified either form.

Make sure you can identify each field on the custom form by its prompt text, as only the prompt text displays when you select Source fields for the mapping. Access the screen generator for the custom form to view this information. If multiple fields share the same prompt text, you may also want to update them with unique, descriptive prompt text to make them easier to identify. Fields without prompt text display their field names in the Source field when you perform the mapping.

  1. Select a benefits custom form in the Custom Forms list.

  2. Select Actions > Create Conversion Mapping on the options bar or menubar.

  3. Select a benefits data capture form to map to, either a default form or one that your agency has customized using the Policy/Plan Detail Builder. You cannot map the same custom form to a different data capture form once mapping is complete.

  4. The mapping panel displays, with a preview of the data capture form. If you selected the wrong data capture form, click the Change Form Target button to choose a different one.

    The system automatically maps fields with a one-to-one match (for example, Project Name). You must map other fields manually. You can expand each area of the form and click the fields you want to map. Mapped fields display in blue on the form and unmapped fields display in pink.

  5. Map all fields on the custom form to their counterparts on the data capture form. For details on the default data capture form field corresponding to each mapped custom form field, refer to these articles:

Select a field on the data capture form from the Target Field dropdown menu, then select its custom form equivalent from the Source Field dropdown menu. Repeat this step until you have mapped all necessary fields. To change a mapping selection, select the Target field and/or Source field, then press [Backspace] to clear the selection.

If you have mapped multiple fields incorrectly and want to start over, click the Discard changes button to remove all mappings (including the default mappings).

If you need to make updates to a customized data capture form in the Policy/Plan Detail Editor, select Edit from the Mode dropdown menu. You cannot edit Applied-managed forms.

Click Publish to save and publish your edits to the form. If you need to continue mapping fields, select Custom Form Mapping from the Mode dropdown menu.

  1. Double check that you have selected a Target field and a Source field for all fields you want to map. Select Preview from the Mode dropdown menu to view the form. Note that the preview only displays the sections of the data capture form, not the data that will be converted.

  2. Click the Publish button to save your mappings and prepare the form for conversion.

Publishing only makes the custom form available for conversion; it does not convert existing custom form data or enable new policies to be created using the data capture form. To take these additional steps, you must run the conversion, as explained in the next section.

Run Custom Form Conversion

Although you can create a conversion mapping at any time, Applied recommends running the conversion (to migrate policies) outside of peak business hours, as it may take several hours to complete and users will be unable to work on the plans you are converting while it is running.

  1. When you are ready to migrate existing custom form benefits policies to a data capture form, select a form that you have mapped in the Custom Forms list, then select Actions > Run Custom Form Conversion on the options bar or menubar.

  2. The Process Conversion window displays. In the Scheduling Options section, choose to run the conversion Now or Schedule to run it later. If you choose Schedule, enter a date and time for the conversion to run.

  3. Click OK to begin the conversion or create a job to run it at the date and time you specified (depending on your selection in the previous step).

    When the conversion completes, a job notification displays and a Microsoft Excel document listing the policies updated during the conversion saves to your browser’s Downloads folder. If the conversion is scheduled, the file displays in your Downloads the next time you log into Epic.

  4. Repeat the steps above to convert additional custom forms.

Running the conversion inactivates the custom form to prevent you and other users from making additional changes to it or associating it to policy types. If you missed a mapping during the conversion process and need to rerun it, perform the Inactivate/Reactivate action to activate the custom form before redoing the mapping and rerunning the conversion.