Loading
Feature degradation | Gmail Email delivery failureRead More
Insurance
Table of Contents
Filter by (0)Add
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

            Search all of Salesforce Help
            Search all of Salesforce Help
            Issue Policy Business Processes

            You are here:

            1. Salesforce Help
            2. Docs
            3. Digital Insurance

            Issue Policy Business Processes

            We've created an Issue Policy business process that takes a quote and issues an insurance policy. This business process is reused across multiple lines of business.

            All our screenshots are currently in Lightning style. Your spin may look different because it's using the Newport style in the Broker Portal and Customer Portal.

            Issue Policy OmniScript

            You can launch this OmniScript from the following applications, where it can be accessed by the types of users described:

            • Broker Portal (Newport)

              Brokers and agents

            • Interaction Console (Lightning)

              Internal insurance agents and call center reps

            • Vlocity Admin Lightning Experience (Newport)

              • Internal insurance agents

              • Vlocity admins

            These OmniScripts now write to the native Financial Services Cloud Insurance Policy object instead of the Asset object.

            Now let's go through the Issue Policy OmniScript step by step.

            First, the OmniScript takes a quote Id and uses the InsQuoteService:getQuoteDetail service to retrieve the data for the quote the user wants to issue a policy for.

            It then displays information about the quote, including the premium price and the term of the insurance policy to be purchased.

            Depending on which payment option the user chooses, the step tree on the right changes. The steps a user takes to create payment information changes based on the choices they make. In the following example, the user chose Payment Plan.

            Illustrates the screen to select billing options.

            After the user chooses Payment Plan and clicks Next, this OmniScript calls another Omniscript named ins/SetupPaymentPlan PaymentPlanSetup1. The PaymentPlanSetup1 OmniScript takes the user through the forms and choices necessary to set up all their payment information for the policy.

            Illustrates the screen to set up billing details.
            Illustrates the screen to select payment frequency.
            Note
            Note

            To make it easy to test this functionality, we use a Lightning Web Component built to integrate with Braintree. Braintree lets us either add testable credit card numbers or click Next. The OmniScript sees the payment inputs as valid and lets the user go on to the next step.

            You can remove or modify the Braintree Lightning Web Component if you clone and use this OmniScript in a production environment.

            Illustrates the screen to select a payment method.
            Illustrates the screen to enter payment details.

            After the payment is authorized, the IssuePolicy OmniScript calls the InsPolicyService:createUpdatePolicy service to create the policy record.

            An Omnistudio Data Mapper Extract action reads the policy record, and the OmniScript displays a confirmation that the policy is active.

            Now let's go through the same flow, with the user making different choices.

            In the same Confirm Quote Details page at the beginning of the previous flow, the user chooses Pay in Full.

            Illustrates the screen to select payment options.

            Then the user chooses the Electronic Check option as their payment method. This OmniScript calls another Omniscript named ins/IssuePayment1. The IssuePayment1 OmniScript takes the user through the forms and choices necessary to get all their payment information to pay for the policy right now.

            The user can choose Credit Card or Electronic Check. In this example, the user chose Electronic Check.

            Illustrates the screen to enter payment details.

            The IssuePayment1 OmniScript integrates with an ACH system to take the customer's bank account information and authorize the payment.

            Illustrates the screen to enter account details.
            Illustrates the screen to authorize payment.
            Note
            Note

            The achAuthorization step in the IssuePayment1 OmniScript is set up to accept and authorize test data.

            You can modify this step in the OmniScript you create or extend.

            After the payment is authorized, the IssuePolicy OmniScript calls the InsPolicyService:createUpdatePolicy service to create the policy record.

            A Data Mapper Extract action reads the policy record, and the OmniScript displays a confirmation that the policy is active.

            What's In It

            Here's what the steps look like in the OmniScript Designer:

            1. getQuoteDetails

            2. getQuoteInformation

              • Component type: Data Mapper Extract Action

              • What it does: Extracts product and account information from the quote.

              • Calls: Ins_ExtrQuoteDetails_IssueOS

            3. setQuoteInformation

              • Component type: Set Values

              • What it does: Sets values for a number of quote elements

              • Calls: None

            4. quoteDetails

              • Component type: Step

              • What it does: Includes the following subcomponents:

                • quoteNumber

                • quoteEffectiveDate

                • quotePremium

                • quoteTerm

                • billType

              • Calls: None

            5. paymentPlanSetUp1

              • Component type: OmniScript

              • What it does: Calls another OmniScript that lets the user set up a payment plan.

              • Calls: ins/SetupPaymentPlan OmniScript

            6. setPaymentAmount

              • Component type: Set Values

              • What it does: Sets values for a number of billing elements.

              • Calls: None

            7. IssuePayment1

              • Component type: OmniScript

              • What it does: Lets a user pay their premium in real time.

              • Calls: ins/IssuePayment OmniScript

            8. createUpdatePolicy

              • Component type: Integration Procedure Action

              • What it does: Creates a policy record.

              • Calls: Insurance_CreatePolicy Integration Procedure

            9. applyPremiumPayment

              • Component type: Integration Procedure Action

              • What it does: Applies a premium paid via the IssuePayment OmniScript in step 7 to the policy record.

              • Calls: Insurance_IssuePayment

            10. readPolicyforconfirmation

              • Component type: Data Mapper Extract Action

              • What it does: Extracts data about the policy, the product, and the payment.

              • Calls: readPolicyLwc

            11. UpdateQuoteStatus

              • Component type: Data Mapper Post Action

              • What it does: Updates the quote status.

              • Calls: UpdateQuoteStatus

            12. CreatePolicyParties

              • Component type: Integration Procedure Action

              • What it does: Creates a record of the policyholder as a party.

              • Calls: PolicyholderParty_Create Integration Procedure

            13. CreateProducerParty

              • Component type: Integration Procedure Action

              • What it does: Creates a party record for the broker who sold the insurance policy.

              • Calls: ProducerParty_Create

            14. policyConfirmation

              • Component type: Step

              • What it does: Contains the following subcomponents:

                1. Congrats: A Text Block that congratulates the user on purchasing the policy.

                2. CustomLWC1

                  • Component type: Custom LWC

                  • What it does: Displays confirmation of the policy purchase, with purchase data.

                  • Calls: vlocity_ins__insOsConfirmation

                3. textBlock2: A Text Block that includes contact information for the insurer.

                4. viewPolicy

                  • Component type: Navigate Action

                  • What it does: Provides navigation

              • Calls: None

            Issue Policy from the Quote UI

            A customer service rep or internal insurance agent with access to the Quote UI can issue policies from that UI. This example shows policies issued from the Quote UI using out-of-the-box LWC-based components from an existing quote.

            Here's what it looks like step by step:

            Start on the Quote list page. Choose the quote you want to issue a policy for.

            On the Quote UI, click Issue Policy - Native.

            On the Issue Policy window, make any changes you want and click Create.

            Vlocity creates the policy and displays a success message on the Quote UI.

            You can also launch the OmniScript described in the previous section from the Quote UI. Click Issue Policy to launch this OmniScript.

             
            Loading
            Salesforce Help | Article