SNOW

1) Endpoint This is the URL or Address where the SOAP request is delivered. It must be able to reach that endpoint over the network in order for the communication to succeed. 2) Action String that is often optional with the SOAP web service. However, some services do require this to be set. The string is often descriptive of what action should be performed by the web services. 3) Headers/Attributes Found within the HTTP request. They contain information regarding the protocol being used as well as other custom information such as session IDs, authentication token, etc. 4) Envelope Actual document that describes the details of the SOAP request. This is written in XML format. Has a header and a body similar to an HTML webpage. Header and body details are dictated by the web service and explained in a corresponding WSDL document

${URI} Shows the word LINK where as  ${URI_REF} shows the display value of the record as the link text.

Response Times Remove unused inactivity Monitors Optimize queries to search Adjust auto-complete wait time in increments of 50ms, no more than 750 Check SLA trace level -Monitor process duration of scheduled jobs Default Row Count Go To Search Option Auto-complete Search Option Table Rotation

Yes, you can do it by using a function autoSysFields() in your server side scripting. Whenever you are updating a record set the autoSysFields() to false example: var gr = new GlideRecord('incident'); gr.query(); if(gr.next()) { gr.autoSysFields(false); gr.short_description = "ServiceNow" ; gr.update(); }

 Both allow creation of reusable javascript • GBRs can impact performance unless contents are wrapped in functions • GBRs load on every interaction between a user and the platform • Script includes only load on demand and do not impact performance

Use async whenever possible Use display to pass data from server to client side during form load Wrap code in functions to make variables local Use condition builder rather than script whenever possible