To get the variables from task we use task.variable_name To get the variables from RITM we use current.variables.variable_name

---

0 Helpfuls

Hi Anittha, You are right, Ui Policy is client side and Data Policy is server side validation. But better and clear answer would be. If we would like to apply the validations for the data that is entered by user manually on forms then we will use UI Policy. On the other hand, if we would like to apply validations for the data which is coming via Integration (or not entered manually by end users) then we will use Data Policy.

---

0 Helpfuls

Imo, the interviewer was expecting this: UI Policy is applied on the data entered via browser, while Data Policy can be applied on all the data entered into the system be it integrations, data source etc

---

0 Helpfuls

There are user criteria that can be defined to restrict the visibility/ access of a record producer.

---

0 Helpfuls

I think she meant to say, is there any restriction on which table we can create record producer. I was asked the same but I don't see any answer for this on community

---

0 Helpfuls

You can create a record producer for tables and database views that are in the same scope as the record producer. Also for tables that allow create access from applications in other scopes.

---

0 Helpfuls

All tables extending 'Task' table

---

0 Helpfuls

You can create a record producer for any table you want even custom tables, but as per the ServiceNow docs, it is recommended only to create Record producers for tables that are extending from Task table

---

0 Helpfuls

The assignment lookup rule assigns incidents matching the values in the matcher fields (Category, Subcategory, Configuration Item, and Location) to the values in the setter fields (Assignment Group and Assigned To). A valid assignment lookup rule requires at least one matcher field and one setter field.

---

0 Helpfuls

GlideSysAttahment.copy('source tablename', 'source table sys_id', 'target tablename', target table sys_id');

---

0 Helpfuls

var attachment = new GlideSysAttachment(); var incidentSysID = 'ab1b30031b04ec101363ff37dc4bcbfc'; var incGR = new GlideRecord('incident'); incGR.get(incidentSysID); var copiedAttachments = attachment.copy('incident', incidentSysID, 'problem', incGR.getValue('problem_id')); gs.info('Copied attachments: ' copiedAttachments);

---

0 Helpfuls

using Page route map

---

1 Helpfuls

By modifying SPEtryPage script include

---

1 Helpfuls

Private functions are the functions which can be accessed/called from same script include or child script include, which means it cannot be called in background script or Fix script directly. Private function in SN can be defined by using underscore in the beginning of function name e.g. _getUserData:function(){}

---

0 Helpfuls

Try using Dot walking and if statement for example - var gr = new GlideRecord('sys_user') gr.addQuery('sys_id','02826bf03710200044e0bfc8bcbe5d88'); gr.query(); if (gr.next()){ gs.print('User Name - ' gr.name) gs.print('Manager Name - ' gr.manager.name) if(gr.manager.manager.name){ gs.print('Managers Manager Name - ' gr.manager.manager.name) //Make sure that managers field is populated in users and managers record } else{ gs.print('Director Details (I dont have director so not displaying)') } }

---

0 Helpfuls

1. Flow can be scheduled, workflow cannot. 2. Flow have multiple triggers e.g. Inbound email triggers, Application triggers and Rest Triggers, workflow can be triggered based on record creation or update.

---

2 Helpfuls