- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2019 09:24 PM
Can anyone please help me to understand all these interviews questions
1. What kind of incidents tickets do we get as an admin or developer?
2. what is the main difference between GlideAjax and Sctrachpad?
3. I got an issue (any issue, how to fix) with change management what is the next step would you do to resolve as a Servicenow developer or admin
4. what is the process of Incident, problem and change management. How do we resolve any issue with all these three procedures?
5. What kind of challenges we usually face?
Thanks,
Sunil
Solved! Go to Solution.
- Labels:
-
Change Management
-
Incident Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2019 09:34 PM
Hello Sunil.
1. What kind of incidents tickets do we get as an admin or developer?
As a developer or administrator, you will get tickets for
a. Maintenance activity,
b. Functionality issues
C. Enhancement requests
d. Stories to create functionalities.
2. what is the main difference between GlideAjax and Sctrachpad?
You will most likely be fine with switching to GlideAjax. The g_scratchpad is not always preferable to GlideAjax from a Best Practice standpoint. Each one has its own use case and purpose for which it was designed. You have 3 major costs at play here:
Network Latency
Every GlideAjax call adds an extra network call which takes time.
When it Matters: This matters if retrieving the value prevents the user from interacting with the form in a moment where the user wants to interact with the form (i.e. I can see it but I can't use it) or if it confuses the user by changing the form after the user believes the form to be ready for input ("Where'd that field go!").
Initial Form Load Time
Display Business rules run before a form gets rendered which means any data retrieved at this point costs time between a user clicking something and the form displaying.
When it Matters: This matters if it prevents the user from interacting with the form for an abnormally long time. Usually you won't run into this issue with simple data lookups but it is still worth noting. This is why g_scratchpad is often the "Best Practice".
Maintenance Cost
Why buy one when you can buy two at twice the price, right? Maintaining these scripts, and building them for that matter takes time and effort.
When it Matters: If you find the latency and form load to be negligible, then this factor will probably be the deciding one. It also matters if the maintenance risk is unreasonably high, which probably should not be the case in the current scenario.
So there you have it. Neither one is the best all the time. You have to evaluate your requirements and select the right one for you. Unless you are dealing with a lot of rural users with slow internet, GlideAjax should be fine.
Edit:
A couple other thoughts:
a. Display Business Rules run on every form load. If the data value is not needed on every form load, then the system is wasting resources and time with g_scratchpad
b. GlideAjax is also well suited to use cases where user input is required in order to retrieve the data
3. Quertion 3 and 4:
5.What kind of challenges we usually face?
- Its totally depends upon your instance that how you configured
- If you considered best practices provided by servicenow then in most of the cases you wont get any issue or performance issues.
- Also while servicenow instance, in some cases, you will observe some upgrade issues because use of deprecated APIs, modifying OOTB box functionalities, widgets , scripts
Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade
Abhishek Gardade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2019 09:34 PM
Hello Sunil.
1. What kind of incidents tickets do we get as an admin or developer?
As a developer or administrator, you will get tickets for
a. Maintenance activity,
b. Functionality issues
C. Enhancement requests
d. Stories to create functionalities.
2. what is the main difference between GlideAjax and Sctrachpad?
You will most likely be fine with switching to GlideAjax. The g_scratchpad is not always preferable to GlideAjax from a Best Practice standpoint. Each one has its own use case and purpose for which it was designed. You have 3 major costs at play here:
Network Latency
Every GlideAjax call adds an extra network call which takes time.
When it Matters: This matters if retrieving the value prevents the user from interacting with the form in a moment where the user wants to interact with the form (i.e. I can see it but I can't use it) or if it confuses the user by changing the form after the user believes the form to be ready for input ("Where'd that field go!").
Initial Form Load Time
Display Business rules run before a form gets rendered which means any data retrieved at this point costs time between a user clicking something and the form displaying.
When it Matters: This matters if it prevents the user from interacting with the form for an abnormally long time. Usually you won't run into this issue with simple data lookups but it is still worth noting. This is why g_scratchpad is often the "Best Practice".
Maintenance Cost
Why buy one when you can buy two at twice the price, right? Maintaining these scripts, and building them for that matter takes time and effort.
When it Matters: If you find the latency and form load to be negligible, then this factor will probably be the deciding one. It also matters if the maintenance risk is unreasonably high, which probably should not be the case in the current scenario.
So there you have it. Neither one is the best all the time. You have to evaluate your requirements and select the right one for you. Unless you are dealing with a lot of rural users with slow internet, GlideAjax should be fine.
Edit:
A couple other thoughts:
a. Display Business Rules run on every form load. If the data value is not needed on every form load, then the system is wasting resources and time with g_scratchpad
b. GlideAjax is also well suited to use cases where user input is required in order to retrieve the data
3. Quertion 3 and 4:
5.What kind of challenges we usually face?
- Its totally depends upon your instance that how you configured
- If you considered best practices provided by servicenow then in most of the cases you wont get any issue or performance issues.
- Also while servicenow instance, in some cases, you will observe some upgrade issues because use of deprecated APIs, modifying OOTB box functionalities, widgets , scripts
Please mark as Correct Answer/Helpful, if applicable.
Thanks!
Abhishek Gardade
Abhishek Gardade
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-04-2019 11:44 PM
Thank you, Abhishek Gardade
