Transcript:
0:02 [Music]
0:08 welcome today we are diving into another
0:10 interesting topic on Microsoft datae it
0:13 is about combining checklists with the
0:15 business process flow
0:16 functionality Bruce can you tell me more
0:19 about the North52 solution for
0:22 this sure Patrick it would be my
0:24 pleasure but let's start with
0:26 understanding why checklists is so
0:27 powerful they can help break down
0:29 complex process into a series of tasks
0:31 that are more
0:32 manageable Patrick can you think of an
0:34 example where you may have seen this in
0:36 action recently oh good question let me
0:39 think you know I recently had my eyes
0:42 lasered to correct my vision I noticed
0:44 that the Eye Consultant running through
0:46 a series of checks while they were
0:48 setting up for the surgery wow great
0:50 example checklists are used in all
0:52 Industries Pilots doctors construction
0:55 Engineers actually I recommend reading
0:57 an interesting book called The checklist
0:59 Manifesto if you want to dive deeper
1:01 into the
1:02 subject I might just check that out but
1:05 for now I understand a number of North52s
1:08 insurance and banking customers use them
1:10 to great effect within their Dynamics
1:12 365 solutions could you explain
1:15 how sure let's take the scenario of an
1:17 insurance agent taking a claim over the
1:19 phone we'll use the case functionality
1:21 in Dynamics and a business process flow
1:23 called phone to case process I would
1:26 imagine the combination of high level
1:27 stages in the business process flow and
1:30 tasks at each stage is great for
1:32 breaking down complex processes into
1:34 manageable steps
1:36 exactly you can see that I'm creating a
1:38 case with the type of new claim setting
1:40 the customer and the origin as phone
1:43 when I click save North52 rules are
1:45 executed and we see that a set of tasks
1:48 have been created in the checklist
1:50 section this doesn't look that complex
1:52 from the users's point of view which is
1:54 exactly how it should be for the user
1:56 but we are dealing with three different
1:57 tables when processing these rules the
1:59 case the BPF and the tasks so the
2:03 decision criteria for these rules are
2:05 based on values from the case form and
2:08 the stage of the phone toase process and
2:11 the combination of these is what
2:12 determines which tasks are created
2:14 that's
2:17 right can we take a look at the North52
2:21 decision table rules sure this is a
2:24 library calculation formula which means
2:26 that it can be called from other
2:27 formulas the reason we use it here is
2:30 that these checklist tasks items can be
2:31 created as a result of a change in the
2:33 business process flow or a change on the
2:36 case table so there are two trigger
2:38 points that could invoke the processing
2:40 of these rules yes and setting it up
2:43 this way means the rules are defined in
2:44 one formula and do not need to be
2:47 duplicated the First Column has been set
2:49 up as a comment column these do not
2:51 impact the rules but are very useful for
2:53 creating notes or as in this case
2:55 creating a reference to the associated
2:57 user story in aure devops I can see that
3:00 being handy all right let's take a look
3:03 at the rules in row four column B is our
3:06 first condition and is used to determine
3:08 where the trigger came from if this is
3:10 from the business process flow or BPF
3:13 then we check column C the current stage
3:15 of the
3:16 BPF then in column D we determine the
3:19 case type matching on the type of new
3:21 claim and finally column e is checking
3:24 the origin and here we're interested in
3:26 being phon if all these conditions are
3:28 met then the action rules will create a
3:31 new task record with the value specified
3:33 in columns
3:35 g2l so the other rows are for different
3:39 tasks to be created when the conditions
3:41 are met that's right there are a couple
3:43 of other details that make this decision
3:44 table a bit more
3:46 interesting the headit policy exit this
3:49 decision table on first match is
3:50 unchecked which means all rows in the
3:52 table are evaluated when the rules are
3:54 executed and allows us to create
3:56 multiple tasks in one operation as
3:58 demonstrated before
4:00 the other setting is that the sheet
4:02 options are set to use use create record
4:06 most decision table rules are updates to
4:08 existing records but this allows us to
4:10 create new records on rows which have
4:12 matched some
4:13 criteria that's super interesting and I
4:16 can see there is huge flexibility and
4:18 configurability in how you can set up
4:20 decision tables for various requirements
4:23 one thing I noticed was the predecessor
4:25 colum when creating tasks what does this
4:28 do that's a very good observation
4:31 Patrick we have validation rules that
4:33 don't allow the user to complete a task
4:35 before the previous one is completed as
4:37 can be seen
4:39 here we won't go into the validation
4:42 rules in this video however they're
4:43 documented on our support portal viewers
4:46 can look for a link in the description
4:47 of this video or search on the support
4:49 portal for task
4:54 checklists that was a great overview of
4:56 how North52 can help streamline processes
4:59 using business process flows and
5:01 checklists if our viewers want to dive
5:03 deeper into North52 for their business
5:05 what's the best way to start they can
5:08 check out the support articles on North
5:10 52's portal at support. 52.com or
5:13 contact us to learn more about their
5:14 specific needs there's also a YouTube
5:17 channel with plenty of examples and
5:18 tutorials so be sure to subscribe and
5:21 explore further there thanks for
5:23 breaking that down Bruce and that's it
5:26 for today's session thanks for joining
5:28 us and don't forget to subscribe stay
5:29 updated see you next time