Hi Vinay, If user don't have READ access then providing WRITE, DELETE or CREATE access doesn't make any sense so I believe, READ ACL should be executing first which will make sure to not evaluate further ACL if user does not pass READ access.

---

1 Helpfuls

Execution order is always : Role >> Condition >> Script

---

0 Helpfuls

Create --> read --> write --> delete

---

0 Helpfuls

Hey Vinay, There is "Change Approval Policies" module in change management where we can create these policies. It is a course of action that can be applied to a change request. It uses a set of variable inputs to evaluate the decisions that are associated with it. For each matching decision, the associated approval definition is applied. More info can be found here : https://docs.servicenow.com/en-US/bundle/utah-it-service-management/page/product/change-management/concept/change-approval-policy.html I was also asked similar question recently so I read and understood about it.

---

1 Helpfuls

scheduled job is used for server side scripting on a scheduled basis. You do not need to trigger it via some other script. Can you please elaborate what you are trying to achieve here?

---

0 Helpfuls

Can you please tell me What is the use of Ondemand scheduled job?

---

0 Helpfuls

Hi Satyapriya, Scheduled job can be executed by using gs.executeNow method in server side script, we need to pass scheduled job glide object as parameter as shown below : var grSchedJob = new GlideRecord('sysauto_script'); if(grSchedJob.get('SCHEDULUD_JOB_SYS_ID_HERE')){ gs.executeNow(grSchedJob); } More info can be found on 'https://www.servicenow.com/community/developer- forum/what-is-the-sys-id-gs-executenow-is-returning/m-p/1577551/page/3' Note : The above script can be found on 'Execute Now' UI action which is available on scheduled job form.

---

1 Helpfuls

Thanks Raj

---

0 Helpfuls

If before query BR is adding filter to show only active incidents and if we try to GlideRecord on incident table then it will return only active incidents. Before query BR executes every time action is performed on database, it doesn't matter if database action is performed via UI or via script.

---

3 Helpfuls

You can write on Submit Client Script with below line of code : var incPriority=g_form.getValue("priority"); if(incPriority==1){ var userInput=confirm("you are trying to submit Critical incident (P1), would you like to proceed?"); if(userInput==false)//user selected no return false; } } return true;

---

2 Helpfuls

With digest functionality end user has option to subscribe for digest notification so that he receives single consolidated notification for certain time period. e.g. Let's say we have "Incident Commented" notification which triggers every time comment is added into incident. If end user subscribes to receive it for 1 day interval then instead of receiving notification for each comment on Incident, he will receive single consolidated digest email for a day.

---

1 Helpfuls

There could be different reasons why user is not able to login but most common is wrong password or user doesn't exist in ServiceNow. Therefore, we can troubleshoot issue by following below steps 1. Verify if user exist in ServiceNow User(sys_user) table. 2. Try resetting user password.

---

0 Helpfuls

If user is not able to login please check below things 1.User is active 2.user id is not empty 3.Most Important - User is not locked out

---

1 Helpfuls

Simillar question already exist above, but anyway users will know that this question is being asked in an interview. Mail script can be called by using below script : ${mail_script:mail_script_name}

---

0 Helpfuls

We can achieve this via workflow. While triggering approval to requester's manager, parallelly we can trigger timer activity for 3 days, preceded by approval to requester's manager manager. If requester's manager approves within 3 days then end the workflow. If requester manager doesn't approve within 3 days then timer activity will complete and then another approval to requester's manager manager will trigger.

---

1 Helpfuls

If approval is triggered to requester's manager and if he does not approve for 3 days then it should pass to manager's manager I need to do it using flow designer, then how can this be achived?

---

0 Helpfuls

Hi, We can achieve the above task by using flow designer by using approval action in it and setting the Wait For Condition of 3 days for Manager to approve it and then in case of not approved it will be assigned to Manger's Manager

---

0 Helpfuls

We can write After BR as below to achieve this requirement: Table : Incident BR Condition : When state changes to Closed var grProblem=new GlideRecord("problem"); if(grProblem.get(current.problem_id)){ grProblem.setValue("state",3);//3 is closed state back end value grProblem.update(); } Tip : Interviewer later asks why After BR, why not before BR or Asynch BR? short and simple answer is, if we are updating other than current record then we are supposed to use after BR. If script is too lengthy and execution time is high then we can go with Asynch BR (which runs in backend so that user don't have to wait till BR executes)

---

0 Helpfuls