Transcript:
0:04 welcome today we're getting hands- on
0:06 with a North52 decision suite and
0:07 bringing you another five top tips this
0:10 time we're focusing on features that you
0:12 may be underusing or not using at all my
0:15 colleague Patrick is going to help us
0:16 with the
0:17 rundown that's right Bruce let's get
0:19 started what would you say is your
0:21 number one
0:25 tip I would say effective use of inline
0:28 calculations is my number one as they
0:29 can be incredibly powerful inline
0:32 calculations are essentially variables
0:33 that you can set and then later use in
0:36 your decision calculation or
0:39 logic let's have a look at this multi-
0:41 sheet formula which calculates pricing
0:43 for various services at Belfast Harbor
0:45 and specifically the charges relating to
0:47 the use of pilot boats is a three-stage
0:50 process defined on separate decision
0:52 Sheets first we are setting the base
0:54 charges piloted charges and boat rate in
0:57 the calculations columns d and e next
1:00 these values are used in the adjustments
1:02 sheet you may notice that the inline
1:03 calculation columns are named the same
1:06 this means the values will be
1:07 overwritten by the new
1:09 calculations we could have used
1:11 different names but I think in this
1:12 instance it makes sense just to update
1:14 the same variable lastly the two inline
1:17 calculation values are used to calculate
1:19 the price per unit and value for the
1:21 quote line item excellent example what's
1:24 there number two on your
1:28 list it's another another calculation
1:30 type this one called setv concat and as
1:33 the name suggests it concatenates values
1:36 each time the variable is updated for
1:38 example when processing Insurance
1:40 claimed you want to provide feedback to
1:42 a user about what rules have been
1:43 processed or why decisions have been
1:45 made to reduce ambiguity and reduce the
1:47 need for customers to
1:50 call in this dental insurance claim
1:52 scenario there are many checks made over
1:54 several decision sheets we can see here
1:56 on the coverage rule sheet we are
1:58 setting messages when is a match on a
2:00 row this one labeled external is
2:03 intended for the customer and the
2:05 internal for employees similarly on the
2:08 next sheet we are setting messages when
2:10 there is a row match relating to a
2:13 previous claim these were appended to
2:15 the messages variable from the previous
2:17 sheet because they are concatenation
2:20 calculations as the rules are processed
2:22 on the various decision tables more
2:24 messages are appended before finally
2:26 being saved to the claim detail record
2:28 and presented to the end user as can be
2:30 seen here on
2:32 screen I love it I can see many
2:35 applications for you want to store these
2:36 kinds of messages moving on to number
2:42 three I think it's time to talk about
2:44 the fit XML wizard of course you can
2:46 manually add fit XML to the global fit
2:48 XML tab but why do that when the wizard
2:51 gives so much more to illustrate this
2:53 we're going to create a formula which
2:55 will return and open a case record when
2:57 a ribbon button is clicked how however
3:00 we will filter the cases that can be
3:02 returned based on the user settings for
3:04 our demo user this will be cases with
3:06 the subject equal to service I have the
3:09 fetch XML here which returns all in
3:11 progress cases where the subject
3:13 assigned is service and orders them by
3:15 the creation tape however depending on
3:18 the user this could change so we need to
3:20 remove this ID and replace it with a
3:22 zero and curly braces North52 will
3:25 replace this value when the formula
3:27 executes in the formula editor we select
3:30 the fetch XML Tab and click the plus
3:32 icon enter get next case for the name
3:35 and copy it in the modified fetch XL we
3:38 need to pass in the user's case
3:40 assignment subject as parameter zero and
3:43 to speed things up I've already created
3:44 the global calculation to retrieve this
3:47 value I click in the parameter zero
3:49 field and then select the source tab
3:52 expand Global calculations and click on
3:54 get user case assignment subject our
3:57 fetch XML query is now ready so I
4:00 generate this adds The Fitch query as
4:03 can be seen here on the global Fitch XML
4:05 Tad and also generates a global
4:07 calculation which we will use
4:10 next we go back to the decision table to
4:12 implement our logic we want to open the
4:15 case form so we use the open entity form
4:17 function shift click to display the
4:19 function wizard ignore the friendly name
4:21 as we will inject the function directly
4:23 into the cell for this demo and select
4:25 the case from The Entity name search now
4:29 this is where things a little more
4:30 interesting we're going to use the
4:32 global calculation that was created
4:34 automatically to return the first record
4:36 of any cases that were found by our
4:38 fetch query click the ID field on the
4:42 wizard go to the source tab expand
4:45 Global calculations if it is not there
4:47 already then expand get next case the
4:51 fields specified in now fetch query are
4:53 available to select under the primary
4:55 node we want the ID of the case so we
4:57 click on the incident ID field
5:00 then click
5:01 generate our formula needs some
5:03 additional logic to handle messaging to
5:05 the user when there are no cases
5:07 available and requires a command button
5:09 set up but we're not going to go into
5:10 that detail in this short demo the main
5:13 objective of this demo was to show how
5:15 we simplify working with parameterized
5:17 Fitch XML and how easy it is to obtain
5:20 the values of fields from the first
5:22 record returned in the query wow quite a
5:25 bit to take in there but that looks
5:27 really powerful thanks for that tip
5:30 let's hear about number
5:35 four I'm going to highlight an
5:37 administrative feature this time it's
5:38 the bulk feature available from the
5:40 North52 start page towards the bottom
5:43 of the start page click to show the
5:45 administration options the first button
5:47 is bulk delete if we click on it we can
5:50 then enter a table name in the panel one
5:52 of the best uses for this is to clear
5:54 out North52 Trace logs so you can debug
5:57 more easily simply enter N5 2 and select
6:00 n52 Trace then choose all records and
6:03 click execute confirm and a bulk delete
6:07 job will be
6:08 started obviously be very careful which
6:10 table you
6:12 select if we go to the trace log list we
6:14 can see the records being
6:16 deleted another great use case for this
6:18 is when using test shield and you want
6:20 to clear out the test
6:21 results brilliant stuff and the last tip
6:24 for this video number five
6:30 it's another admin feature tracing I
6:33 highly recommend taking the time to
6:34 understand North52 tracing as it is
6:36 invaluable for identifying issues that
6:38 may arise when creating complex logic
6:40 and there are many articles on this
6:42 topic on our support portal in North52
6:45 a trace log which is sometimes called a
6:47 trace file is the output of a formula
6:50 execution North52 tracing has two
6:52 primary purposes first one information
6:56 reporting which is what the formula did
6:58 M and and secondly error reporting which
7:02 is what the formula did and what went
7:04 wrong we can set different levels of
7:06 tracing using the options in the
7:08 configuration let's open the
7:09 configuration
7:11 file the options for tracing level
7:13 settings
7:14 are off well this one's pretty
7:18 self-explanatory internal this can be
7:20 ignored as intended for North52 use
7:23 only information show exception details
7:26 this level of tracing is used when you
7:28 want to display information from a
7:29 nested exception this will not create a
7:32 North52 Trace record but will be
7:34 available to download from the business
7:35 process error
7:37 dialogue information this setting will
7:40 produce a trace log when the formula has
7:42 finished executing this will create a
7:44 North52 Trace record that can be examined
7:46 afterwards and would usually only be
7:48 used in a development
7:50 environment and finally information
7:52 system logging this is similar to the
7:55 information setting however the trace
7:57 records get created by the system user
7:59 and there therefore regular users will
8:00 not be able to access the logs this is
8:03 useful when the logs could potentially
8:04 contain sensitive information thanks
8:08 Bruce that's five great tips covered
8:11 these should really help users of North
8:13 52 to work more effectively we can users
8:15 go for more information and help the
8:18 first Port of Call should be our support
8:20 portal at support. 52.com there's a ton
8:23 of great information there but any
8:25 question should be emailed to support at
8:27 North52.com and one of our team will
8:29 respond very
8:32 quickly okay that's all for today's
8:34 session thank you for joining us Bruce
8:36 don't forget to subscribe keep
8:38 yourselves updated and see you next time