Personalizing Vertafore Services

Enter: https://api.vertafore.com

Enter: https://contentservice.vertafore.com

Enter: https://globaltenant.v4-proposal.com

A unique identifier when a service is registered.

On-premise agencies: Enter the Speedlink pool name on your Web Services Server. The Speedlink pool makes the connection to the database.

Online Agencies: This field will not be visible.

Sagitta Web Services URL

Enter a URL to the server with Sagitta Web Services installed.

For example: https://agencywebservicesserver.domain.com

Replace the agencywebservicesserver.domain.com placeholder in the above with the name of your server.

Browser / External Web Services URL

This field is used to manage the requests of the Browser Client, such as loading the Dashboard and Widgets.

Check This Box if You Have Installed Sagitta API on its Own Server.

If you are planning to use InsurLink or some other application that relies on Sagitta API, such as those configured in the Client App Registration page, you may choose to install Sagitta Web Services on a separate server and use it for InsurLink (and potentially other web-services-based integrations) in the future.

Consider this, if your agency...:

• Has adopted many web-services-based features that integrate with your Web Services server, such as Benefit Point, ImageRight, Vertafore eForms, eDocs and Messages, User Password Reset, or internal tooling based on the Sagitta SDK.

• Has noticed slowness, when using any of the features listed above, with your Web Services server under its current load.

• Wishes to segment the InsurLink load, and potentially load generated from other features using SagittaAPI, from load generated from your day-to-day work done using the features above.

• Does not utilize a load-balancer to manage traffic to your Web Services server.

• Plans to enable many Clients InsurLink Access.

Two additional fields will also be displayed:

• Sagitta API Connection Code: Enter the Web Services pool code for the separate Web Services server.

• Sagitta API Web Services URL: Enter the URL for the separate Web Services server.

Is Web Services Server Protected Behind a Gateway Server?

This feature is in preparation for future Sagitta integrations and can be ignored at this time. Future documentation will address when it becomes appropriate to personalize this new feature.

• If this checkbox is checked, a new field will appear: Fully Qualified Host Name of the Gateway Server. This is a required field and must be completed to save the page.

• If this checkbox is not selected, the field will remain hidden with no data in it, and the Web Services Server will continue to work as it does today.

Allow Access to All Users

Use the Allow Access to All Users checkbox to enable access to forms stored in CMS.

When this box is enabled (checked), you are giving all users access to Retrieve forms, even when they are not personalized in Role Based Security to create Vertafore eForms.

Test Connection Button

Once you have completed the connection information as described according to the product you are configuring, click Test Connection, which is located in the Registration section.

Enter the eForms Admin ID as assigned from Vertafore. Use the following format: admin@onpremise.com

Enter the eForms admin password as assigned by Vertafore and set by the administrator through registration.

Sagitta Instance Name

Register Sagitta Instance

Click the Register Sagitta Instance button to register your agency.

The Sagitta Instance Status indicator will be displayed as either Registered or Unregistered.

Test Connection Button

Once you have completed the connection information as described according to the product you are configuring, click the Test Connection button (actually located in the Registration section ).

Read the agreement text through the provided link.

Click the checkbox to agree to ACORD’s terms of usage.

Enter: https://proposal.v4-proposal.com.

Enter the users who will access the Proposals Administrator view from the Sagitta Home page. They will have access to create and modify Proposals templates within Vertafore Proposals.

Click Test Connection to test communication between the Sagitta Web Services Server, and the Vertafore Global Tenant and Vertafore Proposals services.

If no errors have occurred during this process, a success message will be displayed at the bottom of the Vertafore Proposals section.

Click Register for Proposals to register the Proposals feature.

If your agency will be using eDocs, click Generate API Key.

When that button is clicked, this action prompts the following message: Generating a new API Key requires that you must also personalize it in TransactNOW. Are you sure you want to continue?

Clicking OK at the prompt adds or changes the API Key, sets the Created On date to the current day and also sets the Expires On date to one year from the current day.

Clicking Cancel will leave the API Key unchanged.

Each time an API Key is generated, that API Key must be personalized in TransactNOW. If your system is personalized and working on eDocs, do not click this button unless the API Key has expired.

The API Key must be entered at TransactNOW. See the eDocs and Messages Configuration for IVANS Account section for additional information regarding this personalization. To copy the API Key, click "Copy." The Copy button is located between the API Key field and the Show checkbox.

Depending on your organization’s Internet Explorer security settings, you may be prompted to allow access to your Clipboard. Click "Allow Access" at the Internet Explorer prompt shown here.

The API Key is masked by default. If you need to see the key, click the "Show" checkbox. When "Show" is checked, the API Key will be displayed without masking. It will be masked once again when you save the page.

Enter the staff code(s) for the person/people who will be responsible for updating the API Key when it expires. See the section on API Key Expiration Notifications to API Key Administrators for additional information.

This contains the URL for your agency’s InsurLink. Before you register for InsurLink, enter the following URL: https://clientportal.vertafore.com

Enter the Staff Code personalized as the Service Account. See the Service Account Field Added section (posted below) for additional information.

Enter the Staff Codes of users to receive notifications when the Security Keys are about to expire.

Click this button once you have completed the required fields for using InsurLink and Vertafore Services.

When the Register for InsurLink process is successful, the system will generate today’s date in the Created On section and will populate the Expires On date to be one year from the current day.

When the Register for InsurLink process is successful, the Delta Sync Status will be enabled.

The Created On and Expires On dates will indicate the day the keys were generated and the day the keys will expire, once you have clicked Generate Sagitta API Keys.

Enter the users who should receive notifications when the Sagitta API Keys are about to expire. This field is mandatory when generating API keys.

Save the page and click this button to set up Sagitta API keys.

Pre-populated with the URL for Vertafore Tenant services.

Pre-populated with the URL for Vertafore Tenant services.

Pre-populated with the Vertafore token Issuer URL.

This flag is editable prior to setting up the first user to Vertafore Provisioned on the Sagitta Authentication Management page. Set this field to Yes to activate Multi-Factor Authentication for all Vertafore Provisioned users who log in with SSO.

Pre-populated with the Commercial Submissions URL.

Click the Enable Welland Export checkbox and save the page to set up the Sagitta database for the Welland Export. This action creates the WELLAND.EXPORT.AA account and sets up a report to run as part of the Sagitta overnight process.

Enter the users who you wish to receive the overnight status report of the Welland Export.

Click Generate to create a report of the errors that have occurred during the current day. Use this information to diagnose issues and verify data associated with the Welland Export.

The System Identifier is prefilled from your System Personalization settings.

Enter the password you used to access the Classic AMSeForms Administration page.

The URL to access the conversion services is located on the Classic eForms Server. Enter ONE of the following two URLs, replacing [your server name] with your Classic eForms server name:

• http://[your server name]/eFormsWS/eFormsWS.ConversionService.svc/rest

• https://[your server name]/eFormsWS/eFormsWS.ConversionService.svc/rest

This is the length of time the conversion will run during the overnight process. While this process will not block regular tasks in the overnight process, you will not want it to run during regular business hours.

After saving the page, click Request Conversion to indicate you are ready to start your conversion.

The Approved status will update with Yes if your conversion is ready to begin with the next overnight process.

• If you are a Sagitta Online user, you will initially receive a status of No. Vertafore administrators will change this to Yes once you are approved for conversion.

If you are a Sagitta Online user, there may be other customers who have been queued for conversion before you. Conversion are processed in the order they are received.

• If your agency uses an on-premise Sagitta server, you will automatically see the status as Yes.

The Status value is updated as the conversion proceeds through your overnight processes. However, this value does not indicate the conversion is complete. Instead, the History Conversion Analysis Tool should be used. See Sagitta 19.1.2.0 Documentation for information on this tool.