Sagitta 2020 R1.1.0 Release Notes

For information about recommended and supported system configurations for all Vertafore products, see the Supported Configuration Matrix (DOC822 on My Vertafore). You must be registered with My Vertafore and signed in to access this document.

For optimal performance of the application, we recommend the following as a minimal workstation configuration:

It is now possible to access TransactNOW via VSSO instead of using a desktop install. Get a VSSO ID and password, change Import/Export Personalization, and then click TNOW Inquiry or TNOW Quote as normal to log in to TransactNOW. When using VSSO to access TransactNOW, no diaries are created in Sagitta; use Audit Logging in TransactNOW instead. The feature can be turned on for one user, or all users, in Import/Export Personalization.

Sagitta Configuration

To enable this change:

1. A Vertafore VSSO ID and password are required for each user for this integration. If your agency does not have a VSSO Admin with an ID and password yet, contact Vertafore Customer Service.
2. Go to Import/Export Personalization (Other > Personalization > Integration).
3. Enter PI.101 in Program ID.
4. Enter a Staff Code in Staff Id, if you wish to make this change for only one user rather than all.
   1. A separate record will be needed for each Sagitta user to be moved to the new method.
   2. Any user that already has a user-specific PI.101 record in Import/Export Personalization should be updated separately.
5. In the Export section edit the TRANSACTNOW product, or if not there, add it.
6. Enter VSSO in OPTS.
7. Enter https://transactnow.vertafore.com in Data Dir.
8. The other fields in the section: File Mask, Program Dir, Program fields, are no longer needed – clear them out.
9. Repeat steps 6, 7, and 8 for the TRANSACTNOWI product.
10. Note: In Import/Export Personalization, Program ID CI.INTEGRATE, the lines for TRANSACTNOW and TRANSACTNOWI are no longer needed and can be removed.
11. Additional personalization of users and companies will be required in TransactNOW. Contact Vertafore Support for help with this, either by visiting My Vertafore at support.vertafore.com or calling Customer Care at 800.444.4813.

Additional VSSO and PL Rating Configuration

Refer to this VSSO Help file for a checklist on how to continue configuring your agency to fully utilize the VSSO TNOW.

The Accounting Flags page has been updated to include personalization to only allow a vendor type of PRD when entering values into Producer Fields.

The new Allow Only PRD Vendor Type to Producer Fields flag has three options: Blank, Yes, and No. The flag affects new entries only. If the flag is set to Yes (allow PRD only), and there are Producer fields on your system already filled with non-PRD type vendors, no error occurs. The field defaults to Blank (or No) upon installation of this release, and Blank or No indicate that any type of vendor can be entered. When the flag is set to Yes, a Search on a Producer field will display only Staff Codes with Vendor Type set to PRD.

If your agency uses SOAP Web Services to insert and update clients, policies, agency bill invoices, or direct bill commission statements, when the PRD-only flag is set to Yes, these transactions will fail when a non-PRD vendor code is sent in any of the producer fields. The item will not be added or updated.

Reports that include filtering against Producers are not affected by this new personalization.

These pages have been updated to respect this new personalization:

• Client Details
• Client Multi
• Policy Details
• Policy Multi Information
• Direct Bill Commission Processing
• Submission Tracking
• Multiple Submissions
• Invoice Wizard
• Web Service Import
• Client Code Creation
• Company Mailbox Match
• CI.Integrate Match (for policy matching on exports from integration products such as ProducerPlus)
• SOAP Web Services, such as clientInsert, clientUpdate, policyInsert and policyUpdate

The source to pull agency percent on invoices has an updated hierarchy:

• First Policy Multi Information – Multiple BillTo grid
  • If there are two lines with the same matching insurer/payee combination, the system will pull the first one it finds.
• Second Payee – Commission grid
• New: Third Policy Details – Commission %

If Policy Multi Information and Payee have an applicable line for the policy, and there is a number in Commission %, Agency % will prefill from Policy Multi Information. If there is nothing in Policy Multi Information, Agency % will pre-fill from the Payee. If there is no applicable line in Policy Multi or Payee, Agency % will pre-fill from the Commission % field on the Policy Details page.

There will be text (Policy Multi, Payee, or Policy Detail) to the right of Agency % on the Data tab of the invoice to let the user know where the Agency % is pre-filling from. This new text replaces the previous text on that tab: (Original Agency%).

As part of our continued effort to modernize and improve workflow efficiencies, most of the messages that required users to click OK have been updated. The messages now appear at the top of the page for five seconds and do not require user interaction.

Users will also be able to continue interacting with the page by entering data or navigating while the message remains displayed.

Updated Message Style – Example 1

Updated Message Style – Example 2

Prior Message Style

There is a new drop-down on the Benefits Web Services Personalization page to ignore Broker of Record dates sent in on BenefitPoint transactions.

Set the flag to Yes to ignore the BOR dates.

This flag only applies to Benefit Point transactions - policies created through Sagitta Web Services for other integrations will continue to respect the Broker of Record dates when this flag is set to Yes.

Agency Bill invoices with errors (Status X), and non-numeric IDs will no longer appear on the Production Report.

In Sagitta release SAG18R1, OWC10.dll was deprecated, as it was no longer needed to import client schedules, but it was left on the Sagitta Client Components Installs page. In this release, OWC10.dll is removed from the Sagitta Client Components Installs page.

The Sagitta Launcher has been updated in preparation for upcoming releases that eliminate ActiveX controls. The new version number is 1.3.0.0.

The table below lists the new form now available through the Create Forms page.

A Security vulnerability was found in the current tomcat version (v9.0.8). To address the issue, an updated version of tomcat is included in Web Services eForms install of this release. The Ghostcat vulnerability has been fixed at this version.

An issue was discovered with an Adobe PDF crash when generating PDF reports in many areas of the Sagitta application. To address this issue, the Adobe PDF windows have been disconnected from Sagitta. The functionality on the page remains the same, but if there is an issue with Adobe PDF, it will not affect Sagitta.

If you encounter problems or have questions regarding this releases, Vertafore offers the following helpful resources:

• Search the Knowledge Base on MyVertafore.
• Open a case at MyVertafore.

We value your feedback to ensure we are working on what is most important to you. Please use My Vertafore to provide feedback. We appreciate your input, whether positive or negative, on any visible change.

https://support.vertafore.com/