Types of Business Rules in SNOW

-

BEFORE:

  • Use before insert/update business rule to do some validation and if validation fails stop form submission
  • Use before insert/update business rule to set values for current record based on some other fields on the form such as calculated field
AFTER:
  • Use after insert/update business rule to insert/update data in related list table
  • Use to update information on related objects that need to be displayed immediately, such as GlideRecord queries.
ASYNC:
  • Use to update information on related objects that do not need to be displayed immediately, such as calculating metrics and SLAs.
  • Mostly used to call 3rd party SOAP or REST endpoints
DISPLAY:
  • Mostly used to send field value from server side to client side; for the fields which are not available on the form, this value can be used in onload, onchange, onsubmit client scripts

Comments

Post a Comment

Popular posts from this blog

Background Scripts

-
BACKGROUND SCRIPT CODE VAULT RECORD QUERIES ACTIVE REQUESTS WITHOUT REQUESTED ITEMS (function() { var grRequest = new GlideRecord("sc_request"); grRequest.addEncodedQuery("active=true"); grRequest.query(); gs.print('Active Requests without Requested Items :('); while (grRequest.next()) { var gaRequestedItem = new GlideAggregate("sc_req_item"); gaRequestedItem.addQuery("request",grRequest.sys_id); gaRequestedItem.addAggregate('COUNT'); gaRequestedItem.query(); var req = 0; if (gaRequestedItem.next()) { req = gaRequestedItem.getAggregate('COUNT'); if (req == 0) { gs.print(grRequest.number); } } } })(); DISTINCT OPERATING SYSTEMS OF CIS (function() { var gaServer = new GlideAggregate('cmdb_ci_server'); //GlideAggregate query gaServer.addAggregate('count'); //Count aggregate (only necessary for a count of items of each OS) gaServer.orderByAggregate('count'); //Count aggregate ordering gaServe...
Read more

Glide Record Cheat Sheet

-
Query Can also be used in Client scripts and UI policies A standard GlideRecord query follows this format. var  gr  =   new  GlideRecord ( 'incident' ) ;   //Indicate the table to query from //The 'addQuery' line allows you to restrict the query to the field/value pairs specified (optional) //gr.addQuery('active', true); gr. query ( ) ;   //Execute the query while  ( gr. next ( ) )   {   //While the recordset contains records, iterate through them     //Do something with the records returned     if ( gr. category   ==   'software' ) {       gs. log ( 'Category is '   +  gr. category ) ;     } } UPDATE:  This same function applies to client-side GlideRecord queries! If at all possible, you should use an  asynchronous  query from the client.  See this post  for details. var  gr  =   new  GlideRecord ( 'sys_user' ) ; ...
Read more

Setup OAuth2 authentication for RESTMessageV2 integrations

-
Image
1. Configure OAuth provider on instance 1 (OAuth Application Registry -> Create an OAuth API endpoint for external clients) Create unique provider profile name. We need to generate client ID along with Client Secret. Both can be generated by system normally. Token lifespan are optional, generated by default system policy. 2. Configure OAuth consumer on instance 2 (OAuth Application Registry -> Connect to a third party OAuth Provider) Create unique consumer profile name. (very important, script will need pass in this consumer profile name as parameter) Client ID and Client secret are the values were generated from step 1. Grant type. Value can be either "password" or "refresh_token". Suggest to use password since you won't have refresh_token info initially. This refresh_token only will be generated during first time when access token is generated. Token URL will be provided by OAuth provider. In this example, it would be the  https://oauth_...
Read more