3 use cases of Business Rules

No video

3 use cases of Business Rules

Рет қаралды 3,139

Күн бұрын

Hello Tech People !!!
Welcome to ServiceNow Development.
⏱️TIMESTAMPS⏱️
0:00 Intro
0:19 What we have learned in the last video?
0:59 What we are going to learn in today's video?
1:42 Use case 1
11:04 Use case 2
18:56 Use case 3
26:21 Thanks for watching !!
Welcome to ServiceNow Developer series !!
We are preparing for Certified Application Developer (CAD) exam.
We will learn all the relevant topic regarding ServiceNow Development.
-All Playlist -
ServiceNow Developer - • ServiceNow Developer
ServiceNow CSA Exam preparation 2023 - • ServiceNow CSA Exam pr...
ServiceNow Virtual Agent (CHATBOT) - • ServiceNow Virtual Age...
ServiceNow System Administrator - • ServiceNow System Admi...
Microsoft Azure - • Microsoft Azure
#servicenow
#techwithpri
#techworld
#techchannel

Пікірлер: 44

@simhareddy1948 8 ай бұрын

Great session... Pls provide script on if anyone of the child Inc is closed then only the parent should be close

@techwithpri 8 ай бұрын

Hey !! Do one thing try to implement the same in your PDI, take it as a use case. And let me know what are the steps you are taking to solve it. 😄

@swapnilghodekar3781 8 ай бұрын

For BR 3 Br on problem table is good idea. if some one delete incident then it will not update correctly. BR on Problem table (function executeRule(current, previous /*null when async*/ ) { var gr = new GlideRecord('incident'); gr.addQuery('problem_id', current.sys_id); gr.query(); current.setValue('u_associated_prolem_count', gr.getRowCount()); current.update(); })(current, previous);

@techwithpri 8 ай бұрын

Yes perfect !! 👍👍 This can also be done. But whats the condition you put for the business rule to trigger?

@swapnilghodekar3781 8 ай бұрын

@@techwithpri No condition. when to run after, Insert and Update of problem table. Filter Condition blank

@anniss001 14 күн бұрын

@@swapnilghodekar3781 lol before reading your comments, i spent more than two hours trying to apply the same logic, but it didn't work. Thanks for validating those lines of code, because now i know where i went wrong. Much appreciated!😃

@AdrianLobodzinski Ай бұрын

About the Use case 2. (I'm a total beginner) Since the 'problem_ id' is a reference field: What if we used g_form.getReference('problem_id', getId); function getId(problemId){ var id = g_form.getValue('sys_id').... But getReference is used for the forms (client), not the records(server), right? or var gr = new GlideRecord('incident') gr.get('sys_id', "problem_id');... I have currently a big mess in my head regarding what to use for what purpose, as you can see. Hopefully soon I'll get a grasp on it.

@techwithpri Ай бұрын

Hey 👋 No issue you will learn by asking questions and practicing only 🤓 Yes you are absolutely right , by using getReference you can't solve the problem as it has to be solve using business rule as you are creating a record in the task table and both problem table and problem task is a different table 🤓

@AdrianLobodzinski Ай бұрын

15:12 "We need this specific problem". The word 'specific' would be suitable here :).

@techwithpri Ай бұрын

Hey 👋 Thanks 🙏🏻

@PavanKumarReddy-lu3qx 2 ай бұрын

My doubt is on third Use Case - If we remove the attached incident then what about the count? How we decrease the count?

@techwithpri 2 ай бұрын

Hey 👋 yah thats the thing..try something from your end and come to me with a solution if you cant I would help you to solve it.

@KumarVishnuKota 3 ай бұрын

Hi Pritam, When I double-click the Values are not showing (problem_task) under the labels in the form. Please suggest to me. Thank you.

@techwithpri 3 ай бұрын

Hey !! Watch this video of mine and you would understand it 🤓 kzfaq.info/get/bejne/btRzY9dlta6bnas.html

@AdrianLobodzinski Ай бұрын

15:36 Even though we are in the GlideRecord 'problem', the "current" method relates to the incident that the Business Rule is about?

@techwithpri Ай бұрын

Yes we are doing Gliderecord in the problem table but the business rule that we are writing it is in Incident table so here current represents field from incident table not from problem table 🤓

@Shoaibshaafishorts 8 ай бұрын

excellent.waiting for the next video

@techwithpri 8 ай бұрын

Coming tomorrow, keep watching and keep learning !!

@charansai-xx1po 8 ай бұрын

superrrrrrr. waiting for next videos

@techwithpri 8 ай бұрын

Keep watching and keep learning !! New video is coming tomorrow.

@shaziyasultana3703 13 күн бұрын

HI i want to know under which cases we will use Business rules and whcih cases we will use script include , can u pls let me knwo

@techwithpri 8 күн бұрын

Hey 👋 Business Rules are ideal for actions tied to specific record events and conditions whereas use script include for reusable code, complex logic, or functions used in multiple places.

@Rohitsharmaa161 6 ай бұрын

great video bro. When can i expect a server side debugging video. There is a huge concept on debugging in Scripting in service now module lab 4(in business rules - debugging). If possible can u please make a video in it ASAP.

@techwithpri 6 ай бұрын

Yes I know its there in the CAD syllabus and also it is very important one,It would be there soon in ServiceNow Developer series 🤓🤓 Keep watching and keep learning 👍👍

@Rohitsharmaa161 6 ай бұрын

@@techwithpri Thank You

@swapnilbandaru1433 5 ай бұрын

At 4:21 how are you getting all the names of the field. I am unable to get by double clicking

@techwithpri 5 ай бұрын

Hey !! You have to download a plugin for the same. Watch this video to understand the process step by step - kzfaq.info/get/bejne/btRzY9dlta6bnas.html Let me know for any further concerns 🤓

@viswasivakumarvalluri_fvnk9886 Ай бұрын

How can you display the backend names of fields in a table itself

@techwithpri Ай бұрын

Magic 🪄 Haha just use sn_utills plugin 🤓

@MLucky-mc7hk 7 ай бұрын

Small doubt pritam, in second use case already we are using after update business rule... And again why we are doing, gr. Update .. If we use it it run but it will go in loop sometimes... Please clarify

@techwithpri 7 ай бұрын

Hey !! In the second use case I mentioned the condition After - Update thats for triggering the business rules in the incident table. Now gr.update () will update the record in the problem table after generating the work notes and its necessary. Now if I have written current.update() that can cause some looping issue what you have mentioned. Let me know for any further query.😀

@MLucky-mc7hk 6 ай бұрын

Tq pritam.. For clarification..

@techwithpri 6 ай бұрын

@@MLucky-mc7hk keep watching and keep learning 👍

@vijjipagadala4329 8 ай бұрын

hi in realtime in which situation will do these tasks

@techwithpri 8 ай бұрын

Hey !! These 3 tasks is based on real scenario only. Like in the first task I showed how task can be created automatically based on a trigger condition, 2nd task I have shown , how you can copy journal field information in other ticket. Finally how you can count number of associate incidents. All of these are very practical.😃

@vijjipagadala4329 8 ай бұрын

Still how many topics are there in development

@techwithpri 8 ай бұрын

Ha ha..This is just the beginning, there are many important things to cover. Keep watching and keep learning 😃

@praveenreddy2442 8 ай бұрын

hi pritam , in use case 1 why u had taken gr.problem = current.sys_id. //////////// why not gr.problem = current.number . why sys_id is giving number field of problem record.

@techwithpri 8 ай бұрын

Hey!! That's a good question.. gr.problem is a reference field in the problem task table and in reference field you know it stores the sys_id only. current.sys_id will pass the sys id (which means the current problem record) Feel free to ask question if you have any further concern 😊

@praveenreddy2442 8 ай бұрын

@@techwithpri tq very much

@jithinek3399 3 ай бұрын

(function executeRule(current, previous /*null when async*/) { if(!gs.nil(current.problem_id)){ var gr = new GlideRecord('problem'); gr.get(current.problem_id); var entry = current.work_notes.getJournalEntry(1); if(entry){ gr.work_notes = entry; gr.update(); } } })(current, previous);

@techwithpri 2 ай бұрын

Perfect !! Thank you for sharing 🤓