Transcript:
0:00 hi everyone mike from north52 here in
0:02 today's video
0:03 we will show how decision table can
0:05 dynamically build up
0:06 the set attributes of an update record
0:08 function depending on the conditions
0:11 so the business requirements for this
0:12 scenario is as follows
0:14 we will have three custom options sets
0:16 that will be tied to their corresponding
0:17 fields
0:19 and when these option sets are set to
0:21 true their corresponding fields will be
0:23 set to a value
0:24 if the option sets are set to false
0:27 their corresponding fields will not be
0:28 interacted with
0:30 at all this scenario is useful for when
0:33 you have other processes that will
0:34 trigger off the change of certain fields
0:37 using this approach we can conditionally
0:39 set the fields and avoid
0:40 triggering other processes when we do
0:42 not want to okay so let's look at the
0:44 initialization sheet first
0:47 so this will set the default for the
0:49 three variables
0:52 and we will explain later how the no up
0:54 values here
0:56 will be used okay so let's have a look
0:58 at the set variable sheet
1:00 so this sheet will check each of the
1:02 three custom options sets
1:04 to see if they are set to yes if they
1:06 are set to yes
1:07 the decision table will set each of the
1:09 corresponding variables to a value
1:12 note that these are the same variables
1:14 we initially set to in the
1:16 initialization sheet
1:18 so let's have a look at the update
1:19 account sheet now
1:21 this sheet updates the account by
1:23 setting each of these three fields to
1:25 their corresponding variable
1:28 note that if the condition wasn't met in
1:30 the set variable sheet
1:32 the variable will still be set to no up
1:35 here
1:36 if the north52 is told to set a field to
1:39 no
1:40 op it knows to instead ignore that field
1:43 for the update
1:44 so even though we have three field
1:46 updates set here
1:47 north52 knows to only update the fields
1:50 that actually have their conditions met
1:53 so let's see this in action
1:56 here is an account record and we will
1:58 set the field like so
2:00 we can see that the field gets set to
2:02 the value we expect
2:05 and we can also see in the auto history
2:07 tab that only one field was set
2:10 now when we set two fields to yes
2:13 we can see that two fields get set to
2:15 the values we expect
2:17 and again using the order history tab we
2:19 can say that only two fields were
2:21 changed
2:25 thank you for watching and if you have
2:26 any questions about how North52 can
2:29 help your organization
2:30 please get in touch also please
2:33 subscribe to our youtube channel by
2:35 clicking the subscribe button