Add User-Defined Fields and Pages to Sagitta

This function should only be performed by the System Administrator in your agency.

Use this procedure when you want to add fields or pages defined by your agency to Sagitta. Fields can be added to client and policy level pages, but not to Accounting or Other pages with the exception of Insurer, Staff, Payee and Chart of Accounts pages. New fields & pages can be reported on and/or used with MS Word. Client and policy level data can be sent to the remarks sections of ACORD forms in SagittaeForms.

When new pages or user-defined fields are added to the client or policy level and that client and/or policy is archived, the new fields and pages can be viewed when the archived client or policy is accessed.

Data on new pages or user-defined fields on existing pages follow to the next policy when it is renewed, rewritten or copy/merge is used.

  • If a change is made to a field(s) on an agency created page of the previous term of a policy that is renewed, rewritten or re-marketed the change follows to the next term.

  • If a policy with a new page, or an existing page with user-defined fields, is copy/merged into another policy, that page, with its data, is copied to the subsequent policy.

  • If an existing policy-level page with user-defined fields has been renewed, rewritten or re-marketed, and a change is made to the page in the original term, and the copy to next term prompt is answered yes, any changes made to the User-Defined fields will follow to the next term.

History is available to review any changed data in any field on agency specific pages and new fields on existing pages.

Do not use these fields to capture, hold, or report Protected Health Information (PHI). There are strict Federal privacy regulations for auditing access to PHI. Sagitta is not designed to contain nor audit Protected Health Information.

Restrictions

There is no pre-fill on the data entered in these fields to:

  • Sagitta forms

  • Schedules exported to Excel

  • Sagitta Schedules sent to Adobe

Error Messages

When you make an invalid entry the field will not pink as the error message does for current system field(s). The error message appears in red to the right of the field(s) with the exception of the Date Off field, which displays to the left of the field.

Pages that accept user-defined fields

This is an alphabetical list of pages where user-defined fields can be added.

File Name

Page

AC.COVERAGES

Accounts Receivable/Valuable Papers Coverage

AC.UNDERWRITING

Accounts Receivable/Valuable Papers Underwriting

ADDITIONAL.INTERESTS (Policy Level)

Additional/Other Interests (see Note)

APP.SUBMISSIONS

Submission Activity

BA.COVERAGES

Business Auto Coverage

BA.UNDERWRITING

Business Auto Underwriting

BD.COVERAGES

Surety Bond Coverage

BR.COVERAGES

Installation/Builder’s Risk Coverage

BR.UNDERWRITING

Builders Risk/Installation Underwriting

CHART.OF.ACCOUNTS.MASTER

General Ledger Account Codes

CLI.ADDITIONAL INTERESTS

Client Additional/Other Interests

CLI.DRIVERS

Client Drivers

CLI.EQ.COVERAGES

Client Equipment Floater

CLI.LOCATIONS

Client Locatons

CLI.SCHEDULES

Client Schedules

CLI.SUPPLEMENTAL.NAMES

Client Supplemental Names

CLI.VEHICLES

Client Vehicles

CLIENTS

Basic Client

CONTACTS

Contacts

CP.BLANKETS

Commercial Property Blanket

CP.COVERAGES

Commercial Property Coverages

CP.POLICY.COVERAGES

Commercial Property Policy Level Coverages

CP.POLICY.UNDERWRITING

Commercial Property Policy Level Underwriting

CP.UNDERWRITING

Commercial Property Underwriting

DN.COVERAGES

Dental Benefits

DRIVERS

Drivers

EQ.COVERAGES

Equipment Floater Coverage

EQ.UNDERWRITING

Equipment Floater Underwriting

GD.COVERAGES

Garage and Dealers Coverage

GD.UNDERWRITING

Garage and Dealers Underwriting

GL.COVERAGES

General Liability Coverages

GL.UNDERWRITING

General Liability Underwriting

GS.COVERAGES

Glass & Sign Coverage

GS.UNDERWRITING

Glass & Sign Underwriting

HO.COVERAGES

Homeowners Coverage

HO.UNDERWRITING

Homeowners Underwriting

INSURORS

Insurer Codes Maintenance

LF.COVERAGES

Life Insurance/AD&D

LOCATIONS

Locations

LOSSES

Basic Loss Information

LT.COVERAGES

Long-Term Disability

MARKETING

Marketing

MD.COVERAGES

Medical Benefits

MEMOS

Activity Log

MH.UNDERWRITING

Mobile Home Underwriting

MS.COVERAGES

Miscellaneous Benefits

OL.COVERAGES

Miscellaneous Coverage

PA.COVERAGES

Personal Auto Coverage

PA.UNDERWRITING

Personal Auto Underwriting

PAYEES

Payee Codes Maintenance

POLICIES

Policy Info

PRIOR.HISTORY

Prior History & Other Insurance

PU.COVERAGES

Personal Umbrella Coverage

PU.UNDERWRITING

Personal Umbrella Underwriting

REMARKS

Remarks & Attachments

RX.COVERAGES

Prescription Drugs

SCHEDULES

Scheduled Property

SI.COVERAGES

Self Insured Benefits

SN.UNDERWRITING

Snowmobile Underwriting

SP.UNDERWRITING

Supplemental Property Underwriting

STAFF

Staff Codes Maintenance

SUPPLEMENTAL.NAMES

Supplemental Name Information

TD.COVERAGES

TDB/DBL Benefits

UM.COVERAGES

Commercial Umbrella Coverages

UM.UNDERWRITING

Commercial Umbrella Underwriting

VEHICLES

Vehicles

VL.COVERAGES

Voluntary Benefits

VS.COVERAGES

Vision Benefits

WC.COVERAGES

Workers’ Compensation Coverages

WC.UNDERWRITING

Workers’ Compensation Underwriting

WT.COVERAGES

Watercraft Coverage

WT.UNDERWRITING

Watercraft Underwriting

 

The ADDITIONAL.INTERESTS file holds the data entered on both the Additional/Other Interest page on the policy level and the Certificate Holder page on the client level. When selecting this file in the Sagitta File ID field, added fields display on the Additional/Other Interest page.

Where Information Displays for Existing pages

When you access the page that you added fields to, the Additional Information (Agency Defined) section appears after the Quick Entry section. If there are no Quick Entry fields, it appears under the first section of the page.

For Newly Created Pages Only

The Quick Entry feature cannot be used on agency specific pages.

Client level pages are automatically added to the Additional Options section of the Client Nav bar (those items listed when hovering the mouse over the >>) and the location of these can be changed.

To access newly created policy level pages, the pages must be added to PI.Control for the specific coverage code.

How to add user-defined fields & new pages

  1. Access the User-Defined Data Setup page. Access to this page varies depending on how your agency set this up in Toolbar Maintenance or Role Based Security Maintenance.

  1. Do one of the following:

If Then

You are adding new fields or editing new fields to a  Sagitta page

Complete the Sagitta File ID field or select it from the lookup.

The page expands showing the following fields:

  • Page Level

  • File Description

  • ACORD LOB Flag

  • Data to the ACORD 125?

  • ACORD Line of Business

  • Disable Page/Section View

You are creating a new page or editing fields on an agency specific page

Complete the Agency File ID field or select it from the lookup.

After you enter the Agency ID and tab from the field a prefix of ACD. is added.

When accessing this ID in the future, you can enter the file name without the prefix and it will pre-fill.

The page expands showing the following fields:

  • Page Level

  • File Description

  • Page Description

  • Single/Multi Pages

  • ACORD LOB Flag

  • Data to the ACORD 125?

  • ACORD Line of Business

  • Disable Page/Section View

  1. Go to the Database Fields section and click Add to begin adding user-defined fields to the selected page or to a new page.

Role Based Security for User-Defined Client and Policy Level pages

If your agency is using Role Based Security, the following steps must be taken to add client and policy level pages.

Client Level Pages

When you add a client level page, the page is automatically added to CI.CONTROL; however, it is NOT added to the Client section of the Role Based Security Maintenance page. If a role(s) should NOT have access to this page nothing has to be done.

To give a role access to this new page, one of two things can be done. It can be added manually or select Full on the Client Level title bar and any pages (including those you may not want to give this role access to) that have been added to CI.CONTROL will be added with ‘Full Access’. You can expand/collapse the Search Client Records section by clicking the  icon next to the section name and click Add to manually add a page. If you select Full, the new pages are added at the end.

If you are manually adding, in the Program field lookup search for ‘CP.400’ or a description (the page description from the User-Defined Data Setup page) or select all and look for the Program IDs that begin with CP.400. Select the desired page and in the Access field select ‘Full Access’, ‘Display Only’ or ‘No Access’. Save the line item and save the page and the staff members assigned to that role will have access to these pages the next time a client is accessed unless, the page is set to ‘No Access.’

If you added the page by selecting Full, each page can be changed as needed to ‘Display Only’ or ‘No Access’. Highlight the line item that needs to be changed and click Edit on the grid or double click the line item and change from ‘Full Access’ to ‘Display Only’ or ‘No Access’. Save the line item and save the page and the staff members assigned to that role will have access to these pages the next time a client is accessed unless the page is set to ‘No Access.’

Policy Level Pages

When you create policy level pages and add them to PI Control, they are automatically available to any role that has ‘Full Access’ or ‘Display Only’ for PI.101. If the page was added to the Coverage Information or Underwriting & Rating Information section of PI Control, the access to these pages cannot be changed. Whatever the access is for PI.101 will be the access for any Coverage or Underwriting page.

If you add a new page to the User-Defined Pages section in PI Control, and it therefore has a tab on the policy, it can be changed to ‘Display Only’ or ‘No Access’. If the role has ‘Full Access’ for PI.101, the access to the agency specific page can be changed to ‘Display Only’ or ‘No Access’.  If PI.101 is ‘Display Only’ the agency specific page can only be changed to ‘No Access’ (if PI.101 is Display only, any policy level page can NOT have ‘Full Access’).

You can make changes to the access for an agency specific page, by clicking the  icon next to the section name and click Add. In the Program field lookup, search for an ID or description (the page description from the User-Defined Data Setup page) or select all and look for the same ProgrSagitta ID as entered in PI Control. These always start with PI.400 for single pages and PI.800 for multi pages. Select the desired page and in the Access field select ‘Full Access’, ‘Display Only’ or ‘No Access’. Save the line item and save the page. The staff members assigned to that role will not see this change until the next time they sign on to the system unless the page is set to ‘No Access.’

For more information, see Role Based Security Maintenance Page.

Locking Down Data Format(s)

Once you add data to a new page or a new field on an existing page and that page is saved data exists in the file. Changes made to any previously created field on this page that has data via the User-Defined Data Setup page could affect your database.

To prevent this situation, limitations are set as to what formats can be changed and what it can be changed to.

For more information on Locking Down Data Formats, see User-Defined Data Setup Page.

User-Defined Data to Sagitta Word

Data from agency specific fields added to existing pages will not be included in the table for the existing file. These fields will be in a separate table and will need to be selected when creating the form letter or proposal.

User-Defined Data for Reporting

When dictionaries are created for the fields created for a User-Defined page or a User-Defined field on an existing page, if there is a space in the field label, it will be replaced with an underscore. When using report builder if a field was called ‘Coverage Limit’ the dictionary item would be ‘Coverage_Limit.’