Keep going @Ravi. Finally got the correct instructor to learn SNOW from scratch. Especially it is 100% useful for beginners. Guys I don't know about @Ravi but plz support him.
Thank You Ravi !! your efforts are greatly appreciated👏🏻❤The way you break down complex scripting concepts is truly commendable. Your expertise and clear explanations make each video a must-watch. Keep up the outstanding work👏🏻👏🏻👏🏻👏🏻
Ravi sir For this I watched almost 3-4 other videos but didn't understand anything but here you explain so well with examples now I understood what is business rule properly Thank u so much sir❤
After watching you are videos now I am playing with Java script before I am very scared on scripting part now I am understanding from basic to create my own, Thankyou so much Ravi
20:00 am executing AFTER BR requirement but on saving , the short description field is getting updated as "Test"(i guess before BR is also getting executed thts why this is happening) m not able to write what i want to write in short description... what to do? so that while executing only After BR should be considered. pls help
Hii Sir, Your videos are highly informative and helpful. Keep doing this. Also want to ask you a question that is this level scripting is enough for SNOW DEVELOPER ?
Hello, Ravi A single query: Since FixScript, Background script, Schedule Job, and Business Rule are all comes under serverside scripting, why are we using the .update() function in FixScript, Background script, and Schedule Job but not in Business Rule?
Because.. business rule have current object .. so we don’t use current.update() But in other we don’t have current object.. we create our own object.. then we do x.update ()
Great video 😀,easy and to the point explanation 😁, i do have a question though. How can we attach the newly created problem record in the related record tab of the incident ticket in case of after business rule, is it possible ?
Hi Ravi, thank you for the explanation. I have one question regarding After BR example. When I update an incident it is creating a problem record. However if I make any other update like updating short description to the same incident it is creating another problem. How can we avoid creating multiple problems tickets for the same incident record. Looking for your inputs. Thank you in advance 😊😊
It satisfies the condition and created another problem. Example - Inc1 having state on hold and reason awaiting problem. If I update short description of the Inc1 then it created a problem1 now .if I update my short description again to the same incident which is satisfying my BR condition it creats another problem2 record when I make any update. I wan to make sure that if a problem record is already created to the same incident then it should not create any other problem record. Can you provide me some code or logic how to check this
Could you please create Development series comprising all the videos including Client and server script and possibly additional related to development consolidated into one link?
What I mean here is Info message will not work as there is no running order in async BR, but you can use both current and previous objects in BR, it will work.
I tried doing above mentioned example , but its not working.. Could you please tell me what can be the reason . I am getting below error when i run this script at background Evaluator: com.glide.script.RhinoEcmaError: Cannot read property "category" from null script : Line(2) column(0) 1: var gr = new GlideRecord('problem'); ==> 2: gr.category = current.category; 3: gr.description = current.description; 4: gr.business_service = current.business_service; 5: gr.insert();
Async Business Rules allow ServiceNow to return control to the user sooner but may take longer to update related objects. Asynch BR : As name suggest, it runs asynchronously. Whenever Asynch BR is triggered, system creates new entry in event queue to process. Execution time varies for Asynch BR based on the load on event queue.
If you look closely at the out-of-the-box example script: (function executeRule(current, previous /*null when async*/) { So current will work, previous won't work. It clearly mentions null when async.
Keep going @Ravi.
Finally got the correct instructor to learn SNOW from scratch.
Especially it is 100% useful for beginners.
Guys I don't know about @Ravi but plz support him.
Thanks a lot for your feedback… many more to come :)
@@learnservicenowwithravi
Yes @Ravi will support you np😊
Thank You Ravi !! your efforts are greatly appreciated👏🏻❤The way you break down complex scripting concepts is truly commendable. Your expertise and clear explanations make each video a must-watch. Keep up the outstanding work👏🏻👏🏻👏🏻👏🏻
Thanks for beautiful feedback 😍😍
actually, this question is asked in interview. thanks alot.
Thanka
Easy to understand, good initiative 👍
Thanks for liking
Yes bro I'm liking, ur way of teaching is soo simple and understanding
Ravi Sir, I have no words to describe how good your content is! Please keep educating us this way. God Bless You !
Thanks ❤️
Excellent
keep upload more videos @Ravi
Hi Ravi, You have a lots of patience. To explain in detail & clearly. Hats off to you 👏👏👍👍
Awesome 🤩 thanks for your feedback
Ravi sir For this I watched almost 3-4 other videos but didn't understand anything but here you explain so well with examples now I understood what is business rule properly
Thank u so much sir❤
It's my pleasure
Thank you so much for your efforts Ravi ❤
thanks a lot. i learnt something new from this video. very nicely explained...
easy to understand .and like the way of teaching .keep doing such scenario based video
Thanks a lot❤️
nice explanation loved it
you cleared my all concepts. This is a excellent explaination
Thank you! Cheers!
After watching you are videos now I am playing with Java script before I am very scared on scripting part now I am understanding from basic to create my own, Thankyou so much Ravi
❤️❤️
❤️❤️
Bahut badhiya 😂
your videos are very good ,way of explanation is nice
Thanks man 👨
Sending me whatsup group no,am searching job@@learnservicenowwithravi
You have wonderful teaching skills sir.thanks a lot😊
Thanks 🤩
20:00 am executing AFTER BR requirement but on saving , the short description field is getting updated as "Test"(i guess before BR is also getting executed thts why this is happening) m not able to write what i want to write in short description... what to do? so that while executing only After BR should be considered. pls help
Choose after update
Choose after update
Thanks for creating this stuff brother ❤
My pleasure!
Appreciate your work bro. Keep it up
ya bro your teaching is very nice ..
Thanks and welcome
Very useful information
Good explanation bro
Thank you so much 🙂
Nice video sir ji thanks so much
So nice of you
on point , no fluff
very good explanation
Thanks 😊
Hii Sir, Your videos are highly informative and helpful. Keep doing this. Also want to ask you a question that is this level scripting is enough for SNOW DEVELOPER ?
Yes, it is
Hello, Ravi
A single query: Since FixScript, Background script, Schedule Job, and Business Rule are all comes under serverside scripting, why are we using the .update() function in FixScript, Background script, and Schedule Job but not in Business Rule?
Because.. business rule have current object .. so we don’t use current.update()
But in other we don’t have current object.. we create our own object.. then we do x.update ()
@@learnservicenowwithravi Thank you
Tnks bro❤
Great video 😀,easy and to the point explanation 😁,
i do have a question though.
How can we attach the newly created problem record in the related record tab of the incident ticket in case of after business rule, is it possible ?
Yes you need to create br and glide to the problem table and insert it
Hi Ravi, thank you for the explanation. I have one question regarding After BR example. When I update an incident it is creating a problem record. However if I make any other update like updating short description to the same incident it is creating another problem. How can we avoid creating multiple problems tickets for the same incident record.
Looking for your inputs. Thank you in advance 😊😊
Add a conditions in the script.. based on that condition only it will execute
It satisfies the condition and created another problem.
Example - Inc1 having state on hold and reason awaiting problem. If I update short description of the Inc1 then it created a problem1 now .if I update my short description again to the same incident which is satisfying my BR condition it creats another problem2 record when I make any update. I wan to make sure that if a problem record is already created to the same incident then it should not create any other problem record. Can you provide me some code or logic how to check this
when ever am trying to update incident each time its creating new problem ticket here, actually it should not correct ?
Can you ping the script please
Could you please create Development series comprising all the videos including Client and server script and possibly additional related to development consolidated into one link?
th-cam.com/play/PLKH9bPqlw1neGCJbunoZl7ag-zYxyi8Oe.html&si=PFkPCAq6rrqggGIh
why you have used x.insert() at last, does it will not work without insert?
insert means we are creating new record
Nice video @Ravi. Can we write condition also in scripting like state is on hold
Yes you can write.. if(x.getValue(‘state’)==‘3’) and so on ..
This also you can do
@@learnservicenowwithravi but x variable from problem table
👍👍👍👍
If we are using async business rule : 'gs' variable methods will not work.Is it correct? why so? It will ignore the Glidesystem API.
What I mean here is Info message will not work as there is no running order in async BR, but you can use both current and previous objects in BR, it will work.
I tried doing above mentioned example , but its not working.. Could you please tell me what can be the reason . I am getting below error when i run this script at background
Evaluator: com.glide.script.RhinoEcmaError: Cannot read property "category" from null
script : Line(2) column(0)
1: var gr = new GlideRecord('problem');
==> 2: gr.category = current.category;
3: gr.description = current.description;
4: gr.business_service = current.business_service;
5: gr.insert();
What current table you have selected
@@learnservicenowwithravi incident
Async Business Rules allow ServiceNow to return control to the user sooner but may take longer to update related objects.
Asynch BR : As name suggest, it runs asynchronously. Whenever Asynch BR is triggered, system creates new entry in event queue to process. Execution time varies for Asynch BR based on the load on event queue.
what if two after-business rules are there and both have 100 as order and work on the same table which will work 1st
Then it chexk the condition and both will be places in a queue
Thankyou so much
Most welcome 😊
when i tried for joining whats grp it is showing the group doesn't exist
Yes the group is full.. check another group link on the latest video
where is the latest video please can u provide the link@@learnservicenowwithravi
Is the whatsapp group still active?
th-cam.com/video/WI2vcgUS5Ok/w-d-xo.html
Hi can you please do the viodes on IRM
After HRSD
in async why addinfo not worked ?
If you look closely at the out-of-the-box example script:
(function executeRule(current, previous /*null when async*/) {
So current will work, previous won't work. It clearly mentions null when async.
@@learnservicenowwithravi thank you for help and your videos
can you please tell me how its intelligence work. is there any external script
@learnservicenowwithravi can you please tell me how its intelligence work. is there any external script
Its maintained by servicenow
Tq sir I understand very well but I am not able to any task on PDI my self
Is your pdi is hibernating?
@@learnservicenowwithravi I have PDI it's working it means I am able to perform live scenarios
@@learnservicenowwithravi no sir I feel it's understanding but I am not able do that task
If anything wrong forgiveme
generate a report daily at 13hrs for the new incident that are created yesterday and send the email to team lead async business rule in servicenow
Yes you can schedule your report
can you explain this