Sagitta 2026 R1.3.0 Release Notes

Microsoft Windows Server 2025 is required for the Sagitta Web Application Server and must be updated before loading 26R1. See Sagitta Web Application Server 2025 Installation Instructions included in Sagitta 26R1 documentation.

Sagitta’s Vertafore Single Sign-On (VSSO) authentication has been migrated to an OAuth-based VSSO flow for Vertafore eForms and Reset Password. This 26R1 release includes the provisioning implementation, plus an updated login and reset-password experience.

With this new authentication, Classic eForms are no longer supported in 26R1. References to Classic eForms will be removed in 26R2.

CHANGES TO VERTAFORE SERVICE PERSONALIZATION PAGE TO SUPPORT NEW AUTHENTICATION

• Hosted Agency

  • Sagitta Instance Name field has been moved from the Registration section to the Vertafore Tenant Configuration section, while the existing value is retained

  • A note is added in Registration section that points the user to the new location of Sagitta Instance Name field

    

    

• On-Premise Agency

  • The Sagitta Instance Name field has been moved from the Registration section to the Vertafore Tenant Configuration section, while the existing value is retained

  • A note has been added in Registration section that points to the new location of this field

  • New fields are added below the existing fields:

    • Service User

    • Secret

    • Tenant ID

    • Entity ID

    • All four fields will be blank when the release is installed. To add these details, please contact Customer Support.

  

  

  

HOW TO REGISTER THE NEW AUTHENTICATION

1. On the Vertafore Services Personalization page, go to the Vertafore Tenant Configuration section.

   1. This new section is used to register the Sagitta instance and eForms, replacing the former Registration controls at the top of the page.

   2. Go to Step 2 to register if you are a hosted agency, or to Step 3 if you are an on-premise agency.

2. Register for hosted agencies

   1. In the Vertafore Tenant Configuration section, verify that the displayed values are populated.

   2. Click Register Sagitta.

   3. Once registration is completed, the Status value at the top of the Vertafore Tenant Configuration section will change to Registered.

   4. Go to Step 4 – Confirm Registration completed.

3. Register for on-premises agencies

   1. Contact Vertafore Customer Support to receive the required configuration values for the Vertafore Tenant Configuration section.

   2. Enter the values supplied by Customer Support into the Vertafore Tenant Configuration fields.

   3. Click Register Sagitta.

   4. Once registration is completed, the Status value at the top of the Vertafore Tenant Configuration section will change to Registered.

4. Confirm Registration completed

   1. Navigate away from the Vertafore Services Personalization page, and then access it again.

   2. Verify that the Registration section at the top of the page has changed:

      1. The Status indicator will no longer be present.

      2. The Register button (in the top Registration section) will be grayed out and inactive.

      3. Within the Vertafore Tenant Configuration section, the Status will show Registered

Watch the demo on New Authentication and How to Register.

The Sagitta Login and Reset Password pages have been updated to a modern interface through the use of Vertafore Authentication.

NEW SIGN-IN PAGE

The enhanced login page is only available for customers who have registered with the new Vertafore Authentication. If you have not provisioned it, you will instead continue to view the classic login pages.

PASSWORD RESET

The Reset Password window now contains password requirements that comply with your agency’s password rules.

Watch the demo on Modern Login and Password Reset Pages.

This update is delivered as part of Project Impact, an initiative focused on reducing inefficiencies s well as improving the user experience.

NEW CRIME COVERAGES

A Crime Coverages page has been introduced in Sagitta to capture crime coverage details. This page replaces crime information entered under Miscellaneous Coverages.

The Crime Coverages page supports either policy-level or location- / building-level coverage, but not both.

• When Policy Level = Yes, only a single Crime Coverages page is allowed, and coverage applies at the policy level.

• When Policy Level = No, multiple Crime Coverages pages may be added, each associated with a unique Location and/or Building combination.

• A policy cannot contain both a Policy Level = Yes page and Policy Level = No pages.

NEW CRIME UNDERWRITING

A Crime Underwriting page has been introduced in Sagitta to capture crime underwriting details. This page replaces crime information entered in Miscellaneous Underwriting.

The Crime Underwriting page supports either policy-level or location- / building-level underwriting, but not both.

• When Policy Level = Yes, only a single Crime Underwriting page is allowed, and coverage applies at the policy level.

• When Policy Level = No, multiple Crime Underwriting pages may be added, each associated with a unique Location and/or Building combination.

• A policy cannot contain both a Policy Level = Yes page and Policy Level = No pages.

COPY / NEXT BEHAVIOR FOR CRIME COVERAGES AND UNDERWRITING

Copy / Next now matches records at the Policy, Location, and Building levels. If any of these values change and a matching next-term record cannot be found, Copy / Next will create a new record rather than update an existing one. Please plan your renewal and copy workflows with this behavior in mind.

AUTOMATIC DATE-OFF BEHAVIOR FOR CRIME COVERAGES AND UNDERWRITING

When a Policy Level = Yes record exists and includes location-specific Additional Coverages, dating off an individual location will remove that location’s Additional Coverages from the grid. The policy-level record itself will remain active.

When Policy Level = No records exist at the location level, dating off a location will date off all records associated with that location.

CRIME: NEW PAGES MAPPED TO ACORD 141: CRIME SECTION (2016/03)

Crime Coverage and Underwriting data captured on the new Crime Coverage and Underwriting pages now map to the ACORD 141: Crime Section (2016/03).

This process updates Crime form output from the legacy flow - Miscellaneous Coverages/Underwriting → ACORD 141 Crime Section 2000 (2015/04) to the current ACORD 141 Crime Section (2016/03).

Changes to Crime Coverages do not update on the ACORD 175 – Change Request.

Printing The ACORD 141: Crime Section

Crime applications are printed in one of two ways:

• At the Policy Level

• By Location / Building, which may generate one or multiple applications, depending on your selections.

Output is determined by how Coverage Policy Level and Underwriting Policy Level are set:

Scenario 1: Coverage Policy Level = Yes and Underwriting Policy Level = Yes

• A single application is generated.

• Location # and Building # are blank on all pages.

Scenario 2: Coverage Policy Level = Yes and Underwriting Policy Level = No

• Multiple applications may be generated.

• First application:

  • Location # and Building # print on all pages.

  • All fields are populated.

• Subsequent applications:

  • Location # and Building # print on all pages.

  • Coverage, ERISA, and General Questions are blank.

Scenario 3: Coverage Policy Level = No and Underwriting Policy Level = Yes

• Multiple applications may be generated.

• First application:

  • Location # and Building # print on all pages.

  • All fields are populated.

• Subsequent applications:

  • Location # and Building # print on all pages.

  • Underwriting information is blank.

Scenario 4: Coverage Policy Level = No and Underwriting Policy Level = No

• Multiple applications are generated based on the number of Location / Building combinations.

• Coverage and Underwriting must align by Location / Building.

• Each unique Location / Building combination produces a separate application.

CONVERSION OF MISCELLANEOUS COVERAGES AND UNDERWRITING TO NEW PAGES

What the Conversion Does

• Miscellaneous Coverage and Miscellaneous Underwriting Crime records for active policies are converted to the new Crime pages once the 26R1 release is applied to Sagitta.

  • “Active” policies are defined as CNR flag = null, CNR flag = I and M

• Converted Miscellaneous pages are dated off with the latest transaction date.

• A change record is added that describes the conversion; successful conversions = C status, conversions with errors = P status.

• Policy Information Control is updated for insurer / coverage combinations on policies that contained CRIM Miscellaneous Coverage or Underwriting.

What to Expect After the Conversion

• Some fields do not map to the new pages and will be blank after conversion (for example, Basis for Coverage is mandatory on the new page but has no source on Miscellaneous — it will be blank and must be completed on first use).

• User-defined fields on Miscellaneous Crime pages are not converted. Identify affected policies with these report builder statements:

  • SORT OL.UNDERWRITING.ADDLINFO 6 7 8 9 10 11 12

  • SORT OL.COVERAGES.ADDLINFO 6 7 8 9 10 11 12

Conversion Exceptions

• If duplicate question codes are provided, only the last occurrence is mapped.

• Remarks that exceed 160 characters are truncated; any content beyond 160 characters is reported as an error.

• Only Miscellaneous pages configured for the CRIME line of business are converted. Question codes from other LOBs are reported as errors.

• Only Primary coverage codes are mapped to Basic Coverages: EDPFR, EMPGT, EMPTH, ERISA, FORGA, FTF, MOCPC, MSECP, MSOFF, MSOP, and ROBOT. All other coverage codes are mapped to the Additional Coverages section.

• Deductible amounts ending in .00 are converted without the decimal portion on the new page.

• If a Miscellaneous coverage code does not exist in the Crime look-up, the record is still converted, and an error is logged, so the code can be added through Generic Codes.

• Deductible percent amounts are not converted and are instead reported as an error.

• Multiple Primary coverage codes mapped to mismatched locations / buildings will not be converted and instead reported as the record being skipped.

• Codes added to the Discount / Surcharge section of the Miscellaneous Coverage page do not convert.

• The Miscellaneous Underwriting question for question code CRIM34 — “Is a complete physical inventory made?” (If yes, how often?) — only the following remarks for this question will be converted:

  • Semi-Annual

  • Semi Annual

  • Annual

  • Quarterly

• If a user-created coverage code is added to the Miscellaneous coverage codes for the CRIME lob, an entry will be logged to the error report that reads: “xxxx does not exist in ACORD.CR.COVCD.CODES. Add via Generic Codes Maintenance.”

Exceptions Report

• The conversion program writes conversion errors to a report titled Miscellaneous Data Conversion Mapping Failures.

• The Miscellaneous Data Conversion Mapping Failures report will appear in the Processed Reports section of the Dashboard for staff configured on the Overnight UTM Process Parameters page to receive UTM reports.

CODES ADDED IN SUPPORT OF CRIME

New files and codes are added in support of the new pages. Refer to the document, SAG26R1 New ACORD Form Codes in Support of Crime in Vertafore eForms for a comprehensive list.

Watch the demo on Crime Coverages and Underwriting Pages.

This update is delivered as part of Project Impact, an initiative focused on reducing inefficiencies and improving user experience.

Documents downloaded from Sagitta are now downloaded with enhanced file names that include relevant details such as customer code and date. Each file name also becomes the document description in ImageRight with the drag / drop of the file into the file tree.

File Names by document type:

• ACORD Forms – Client and Policy Level:

  • VFORM ClientCode Description Today’s Date (MMDDYYYY).pdf

• Auto ID Cards:

  • VFAUTO ClientCode AutoIDTemplateDescription Today’s Date (MMDDYYYY).pdf

• Loss Notices:

  • VLOSS ClientCode- Description Today’s Date (MMDDYYYY).pdf

• Certificates, ACORD 24 and 25:

  • ClientCode_TemplateDescription_MasterNumber_Today’sDate(MMDDYYYY)_Staff_PID.pdf

Spaces in file names are not supported by all our systems. We replace them with underscores so you can access your files without any problems.

Appropriate names for Units at Risk and EPIs will be released in a future release.

Watch the demo on Download Sagitta Documents with Enhanced File Names.

This update is delivered as part of Project Impact, an initiative focused on reducing inefficiencies and improving user experience.

The Client label prompt will no longer be displayed on the Client Details page when the following situations occur:

• A new client is created,

• The name of the client is edited and saved, and

• Any address fields are edited and saved.

Prompt removed from Client Details

Watch the demo on Client Label Prompt Removed.

This update is delivered as part of Project Impact, an initiative focused on reducing inefficiencies and improving user experience.

Policy Line Item Set data is now fully visible in View Mode. You are in View mode (also called Display) when you access a policy but do not choose a transaction type (Maintain, Endorse, etc.). Accessing a Policy page in View Mode will display new View and ViewAll options. When a single line is selected in the Line Item Set, and View is also selected, line item data is expanded in View Mode to show all the fields of that entry. ViewAll expands all the line items to view all the details of the Line Item Set at one time.

The single View option displays the line item and has the option to go Prev, Next, or Close.

The ViewAll option displays all the line items, per the amount to display set in Personalization. There is pagination to view additional pages of line items that are not displayed on the first page.

This new functionality is available on the following pages:

• Business Auto Coverage

• Business Auto Underwriting

• Commercial Property Blankets

• Commercial Property Location Specific Coverage

• Commercial Property Policy Coverages

• Commercial Umbrella Coverage

• Commercial Property Underwriting

• Commercial Umbrella Underwriting

• Crime Coverage

• Crime Underwriting

• Equipment Floater Coverage

• Flood Coverage

• Garage and Dealers Coverage

• General Liability Coverage

• General Liability Underwriting

• Homeowners Coverage

• Miscellaneous Coverage Information

• Miscellaneous Underwriting Information

• Personal Auto Coverage

• Personal Umbrella Coverage

• Workers’ Compensation Coverage

• Workers’ Compensation Underwriting

The remaining pages will be completed in a future release.

Watch the demo on Access Policy Line Item Set Detail in View Mode.

A new flag, Disable Invoicing, has been added to the Payee Codes page to block invoicing for a payee that has this flag set as Yes.

This new flag affects the following pages with a payee code that creates an invoice:

• Client Multi Information

• Policy Multi Information

• Invoice Wizard

  • Multi tab

  • Installments tab

  • Finance tab

  • Invoice tab

• Web Services

  • policyMulti

  • invoiceInsert

  • commissionStatementInsert

• REST API

  • Client Multi

• One Step Direct Bill Receipts/Disbursements

• Direct Bill Commission Statement Processing

When a Payee Code is entered or searched where Disable Invoicing is set to Yes, an error message is displayed that states invoicing is not allowed for that Payee.

Watch the demo on Disable Invoicing for a Payee.

A new flag, Prompt To Override Suspense On Batch, has been added to the Direct Bill Commission Statement Flags page to allow a different General Ledger Account to be selected when clicking Suspense on the Direct Bill Commission Statement Processing Unmatched page.

When the flag is set to blank or No and you click Suspense, the existing prompt to select a division is displayed. The General Ledger Account automatically assigns the C/B Commissions Suspense G/L# in INS.POST.

When the flag is set to Yes and you click Suspense, the existing prompt to select a division is displayed, followed by the new prompt, Enter Suspense Account.

To enter a different General Ledger Account, enter or search for an account and select Use Different GL Account Number. The General Ledger Account must match the Division chosen in the previous prompt.

To retain the prefilled account from INS.POST, select Use Current GL Account Number without making changes.

Watch the demo on Select a Different General Ledger Account for Direct Bill Suspense.

Date Off and Date Off Remarks fields are now available on the Chart of Accounts page. The new Date Off field allows a General Ledger Account to be dated off, making it unavailable for selection in other programs. General Ledger Accounts may be dated off without requiring a zero balance.

If a General Ledger Account has a date in the Date Off field, the GL Account is not shown within Search. These programs are in error if the General Ledger Account is entered:

• AR Adjustments

• Budget Entry

• Cash Receipts

• Client Cash Receipts/Vendor Checks

• Inter-divisional Journal Adjustments

• Journal Adjustments

• Pay Insurance Invoice

• Vendor Payable Invoice

• Web Services:

  • cashReceiptInsert

  • journalEntryInsert

  • vendorPayableInsert

  • vendorPayableUpdate

Watch the demo on Date Off in Chart of Accounts.

A new CloseAll button is now available on the Period Control page, which allows users to simultaneously close month-end periods for multiple divisions.

1. Navigate to Other > Maintenance > Accounting > Period Control.

2. Select CloseAll at the top of the page.

3. In the prompt, enter the Period End Date and click OK.

   

4. A confirmation message is displayed at the top of the page that reads, All divisions are closed.

Watch the demo on CloseAll Option in Period Control.

The following enhancements have been made to the Policy Number, Invoice Number, and Check Number fields on the Clients Receivable Ledger / Display page.

• Policy Number

  • Characters entered in lowercase letters are automatically converted to uppercase letters when you tab out of the field.

  • Partial searches are now supported using [ ].

• Invoice Number

  • Characters entered in lowercase letters are automatically converted to uppercase letters when you tab out of the field.

  • The field length has been expanded to 12 characters.

• Check Number

  • Characters entered in lowercase letters are automatically converted to uppercase letters when you tab out of the field.

  • The field length has been expanded to 15 characters.

Watch the demo on Client Receivable Ledger Field Enhancements.

When a vendor code is automatically created by adding a payee or staff code, the Vendor Status behavior can now be controlled through a new flag.

A new flag, Default INS and PRD Vendor Status to Held, has been added to the Accounting Flags page. Available values are blank, Yes, or No.

• Blank or No: Vendor Status continues to default to Released when a payee or staff code is created.

• Yes: Vendor Status defaults to Held when a payee or staff code is created.

Example of PRD Vendor Code

Watch the demo on Default Vendor Code Status to Held.

A new Div column is now available to add in the Insurance Payment Process and Cash Receipts grids. These columns are defaulted to Hidden.

Please refer to the online Help article titled, Changing How a Grid Displays, to un-hide the Div column for AP_110_LIS_1 (Insurance Payment Process) and AR_105_LIS_2 page (Cash Receipts).

Watch the demo on Division Column on Insurance Payment Process and Cash Receipts.

New Payee Name and Insurer Name columns are now available to add into the Policy Selection grid. These columns are defaulted to Hidden.

Please refer to the online Help article titled, Changing How a Grid Displays, to un-hide the Payee Name and Insurer Name for PI.100 (Policy Selection).

Watch the demo on Insurer and Payee Name Columns on Policy Selection.

The Purge / Archive process has been enhanced to simplify the record selection process on the page, which will allow more granular control of the records to be purged or archived.

The Purge / Archive template is available for downloading from the Dashboard, under Utilities > Templates.

To include a Client in the Purge or Archive, add its Item ID to the ClientSeq# column in the downloaded XML file.

On the Purge / Archive Setup page (Other > Maintenance > Miscellaneous), the XML file can be imported by clicking the Import button.

Import is only available for the Client Purge / Archive type, and it is only available when a Reference number is loaded.

The selected Clients and their Policies will be displayed in the Items Selected for Purge / Archive grid. The number policies and clients selected will be indicated below the grid as Item(s) Selected by Import.

Watch the demo on Import Client IDs on Purge/Archive.

A flag has been added to the Certificates/EPI’s personalization page (Other > Personalization > System) titled, Print Additional Interests/Holders Email in Remarks for ACORD 25?

When the flag is set to blank or No, Additional Interest/Holder emails will not print on the ACORD 25 (2016/03).

When the flag is set to Yes, Additional Interest/Holder emails will print to the Description of Operation section of the ACORD 25 (2016/03) form, following Coverage and Supplemental Name Information.

Additional information:

• If no emails exist, the header is still placed, but no addresses are listed.

• This behavior applies only to the ACORD 25 (2016/03) version.

• Emails are also reflected on certificates issued through InsurLink.

Additional Interest/Holder emails will print to the Description of Operation section after Coverages and Supplemental Names, with the exception of Additional Interests that have associated Locations, Vehicles, and/or Scheduled Items. These units will print after the Additional Interest/Holder emails.

Watch the demo on AOI/Holder Email Prints to ACORD 25 Remarks.

Commission Statement Insert GUIDs from BenefitPoint will be deleted after 60 days, regardless of the Commission GUID setting on the Web Service Import page. Commission Statement Insert GUIDS from other sources will be deleted, based upon the setting on Web Service Import.