Transcript:
0:00 hi my name is Bruce and I'm a partner at
0:02 North52. in this video I'm going to
0:05 demonstrate how the North52 decision
0:06 Suite alongside the Microsoft Power
0:08 Platform can help insurance companies
0:10 deliver a full-featured quoting system
0:12 all using no Code and low code tools
0:15 that's right for the functionality
0:17 you're about to see not one line of
0:19 JavaScript or c-sharp code was written
0:22 we're going to look at the process where
0:24 an agent provides a quote over the phone
0:26 which is then emailed to the customer to
0:28 review and pay via power Pages website
0:32 let's get started I'm on the compare
0:35 coverage screen of my dental insurance
0:36 model driven app and I've got a customer
0:38 Susan Dove on the phone who is
0:40 interested in taking a dental policy
0:43 we are using the custom page feature and
0:45 I can select the various coverage
0:47 options gold silver and bronze initially
0:50 we select the first of April for the
0:52 policy start date and add in the
0:54 beneficiary details we'll include her
0:56 husband Mike on the policy too
0:58 now let's just pause it here and take a
1:00 look at what's going on behind the
1:01 scenes North52 rules have been set up
1:04 to trigger from a call to a custom
1:06 action this enables flexibility for the
1:09 rules to be used by canvas apps and
1:10 custom Pages power automate or via an
1:14 API call
1:15 we can see here that the action has two
1:18 parameters adjacent payload in for
1:20 inbound information and adjacent payload
1:23 out to return the results
1:25 this is called from our custom page when
1:28 the calculate button is selected
1:31 the custom action is run for each
1:32 beneficiary passing the required
1:34 information as Json
1:36 the North52 formula executes and uses
1:39 this information to retrieve the
1:41 relevant treatment exclusions and
1:42 inclusions for the specified coverage
1:45 for each treatment a premium calculation
1:47 is done this calculation is defined in
1:50 another formula which looks up rating
1:52 tables to determine the premium to
1:54 charge each beneficiary is evaluated
1:58 let's take a look at the calculation to
2:00 determine the base rate we can see here
2:03 that we are using the x-cash get Global
2:05 table function to find the rating data
2:08 we pass in the table name the coverage
2:11 name and we want to return the base rate
2:13 for a given age and treatment defined
2:15 here as the exclusion inclusion line of
2:18 business
2:19 the policy start date is also included
2:21 to ensure we look up the correct X cache
2:23 table
2:24 using Susan as our example and the
2:26 policy start date of the 1st of April
2:28 2023 we can go to our x-cash tables and
2:31 see where the premium base rate comes
2:33 from
2:34 the first of April will be in this table
2:36 as we can see that this table's
2:38 information is for the first of March
2:40 onwards
2:42 Susan is 30 years old and for the
2:44 treatment of crowned resemend the base
2:46 rate premium will be 12.10 on the gold
2:49 plan
2:50 the rate tables are used for all the
2:52 different treatment types for the
2:54 specified coverage which determines the
2:55 final premium amount
2:57 now back to our model driven app with
2:59 our custom page calculating the premiums
3:01 we can see that the three policies have
3:03 different premiums and coverages the
3:06 agent informs Susan that if the policy
3:08 is started before the end of February it
3:10 will be cheaper so we recalculate to
3:12 find that the change premiums are indeed
3:14 cheaper the North52 rating tables
3:17 determine this
3:19 Susan is okay with the earlier start
3:21 date and wants the silver policy so we
3:23 create a quote
3:25 let's pause here and look at the North
3:27 52 formulas making all this happen once
3:29 again this is triggered by a call to a
3:31 custom action which means the create
3:33 quote process could be started from a
3:35 variety of sources but in this case it
3:38 is our custom page which makes the call
3:41 similar to the calculate premiums action
3:43 the create quote action has two
3:45 parameters adjacent payload M for
3:48 inbound information and adjacent payload
3:50 out to return the results
3:52 this is the North52 formula which
3:54 executes when the custom action is
3:56 called
3:57 the first sheet creates the policy quote
3:59 record
4:00 following that contact records are
4:02 created for the beneficiaries if they
4:04 don't already exist
4:05 and adds the IDS of the contact to an
4:07 array to be used in the next sheet which
4:10 creates the related party records for
4:12 the policy quote
4:14 the next sheet updates the main
4:16 policyholder on the quote
4:18 followed by the creation of a record
4:19 which defines the coverage Associated to
4:21 the policy
4:22 and finally the Json payload out
4:25 parameter of the action is output
4:28 let's go back to our model driven app
4:30 and we can open the quote record that
4:31 has been created by the North52 rules
4:33 engine and look into the final details
4:35 for example if we click into the
4:37 coverage we can view what's included or
4:39 Not Included the North52 rules engine
4:41 builds this table using the silver
4:43 policy template and adjust items like
4:45 waiting periods based on the policy
4:48 start dates
4:50 if we go back to the quote we can enter
4:52 contact details and email the policy to
4:54 Susan we move on the business process
4:57 flow which triggers North52 rules to
4:59 generate a PDF and email it to Susan the
5:02 PDF is generated from Json data created
5:04 by North52 and sent to Adobe Document
5:07 Services to be processed once again
5:09 let's pause here and review the rules
5:11 making this happen
5:13 this formula executes on stage change of
5:16 the business process flow in this case
5:17 we are moving to the confirm quote stage
5:19 and are all shown here is to execute an
5:22 action that will create a PDF for the
5:24 quote like previous actions this one
5:26 will trigger a North52 formula to
5:28 execute the rules required to generate
5:30 the PDF these rules include retrieving
5:33 the policy header details each policy
5:35 beneficiary and details of the coverages
5:37 on the policy
5:39 the next step is to create a document
5:41 placeholder record which will eventually
5:43 store the created PDF
5:45 a document party record is then created
5:47 to relate the policy document to the
5:49 document record
5:51 finally all the information is compiled
5:53 into Json and sent to Adobe Document
5:55 Services via power automate flow to
5:58 render the PDF
6:01 Susan receives the email and reviews the
6:03 quote you can see all the details of the
6:05 policy including waiting periods defined
6:08 for various treatments
6:09 so you can click the link in the
6:11 document or email to accept and pay for
6:14 the quote once payment has been made the
6:17 record and Dynamics is updated to
6:19 reflect that the quote is now policy
6:21 let's pause once more to review the
6:24 client-side formula that renders the
6:25 progress indicator on the portal
6:27 each step of the progress indicator is
6:30 represented by a decision sheet and
6:32 depending on the conditions met the name
6:34 and Status may change
6:36 the conditional message displayed under
6:38 the progress bar is also defined on a
6:41 decision sheet
6:42 the final step is for the policy
6:44 documents to be emailed to Susan
6:46 this also includes links to a register
6:49 on the portal to enable claims to be
6:50 processed
6:52 be sure to see our video showing how
6:54 claims are validated and processed using
6:55 the North52 decision suite and
6:57 Microsoft Power Platform