Frequently Asked Questions

Microservices refer to an application architecture that breaks down a single, monolithic application to small, discrete, granular services. These services are:

• • • • • • Highly maintainable and testable
          • Loosely coupled
          • Independently deployable
          • Organized around business capabilities
          • Owned by a small team
            
            

The microservice architecture enables the rapid, frequent, and reliable delivery of large, complex applications. It also enables an organization to evolve its technology stack.

Rating – Performs rating calculation, either stateful or stateless. 

Document Generation –Creates documents by merging forms, templates and/or data. This microservice could be stateful or stateless.

Transaction – Out-of-the-box or custom microservices that perform to insurance transaction activity (i.e. get quote, lapse quote, issue policy, issue endorsement, cancel policy, etc.). These microservice are stateful and generated based on product structure.

Workflow – Orchestrated microservice. This involves other microservices or performs rules and actions required in a business scenario. These microservices are stateful.

Product Management – Microservice which can retrieve product configuration data used in Policy Lifecycle process. Example: Available Products or coverages

Common/Utility – Microservices that are used commonly like Authentication, Authorization, SendMail, etc.

Software-as-a-Service (SaaS), Platform-as-a-Service (PaaS), and Infrastructure-as-a-Service (IaaS)

Solartis Insure SaaS is our “total solution” option that provides all the needed sales and policy life cycle capabilities - including the microservices infrastructure, platform, and user interface; as well as business flow, required integrations, and reporting database.

The Solartis Insure PMT is the toolkit that Solartis uses to configure insurance products, and that our customers use to maintain them. 

New products can be configured from scratch, or created from existing products or bureau-based content (like ISO ERC).

Referral rules are risks that fall outside the user’s authority level and must be referred to another user for review.

A kill question describes when an eligibility rule is triggered, and the risk is then declined.

These are risk acceptance and rejection rules, which may be specific to a carrier or to an MGA.

Workflow rules affect the flow of the user interface/user experience (UI/UX). A specific answer to a single question may trigger a subtask that requests additional information, for example.

If a certain condition is met the system triggers an action / certain result, which can apply to both coverages and to forms.

Error messages are displayed to the user when inaccurate information has been entered, alerting the user to the issue and preventing further actions until corrected.

Exceptions may be created for different categories of rules, setting parameters for different situations where the pre-stated rules do not apply.

The Solartis Insure platform supports versioning of information, maintaining prior versions of the policy to support out-of-sequence endorsement.