servicenow gliderecord assignment group

User Object Cheat Sheet

No matter what system you’re working in, it is always critical to be able to identify information about the user who is accessing that system. Being able to identify who the user is, what their groups and/or roles are, and what other attributes their user record has are all important pieces of information that allow you to provide that user with a good experience (without giving them information they don’t need to have or shouldn’t have). ServiceNow gives administrators some pretty simple ways to identify this information in the form of a couple of user objects and corresponding methods. This article describes the functions and methods you can use to get information about the users accessing your system.

GlideSystem User Object

T he GlideSystem (gs) user object is designed to be used in any server-side JavaScript (Business rules, UI Actions, System security, etc.). The following table shows how to use this object and its corresponding functions and methods.

It is also very simple to get user information even if the attribute you want to retrieve is not listed above by using a ‘gs.getUser().getRecord()’ call as shown here…

g_user User Object

The g_user object can be used only in UI policies and Client scripts. Contrary to its naming, it is not truly a user object. g_user is actually just a handful of cached user properties that are accessible to client-side JavaScript. This eliminates the need for most GlideRecord queries from the client to get user information (which can incur a fairly significant performance hit if not used judiciously).

It is often necessary to determine if a user is a member of a given group from the client as well. Although there is no convenience method for determining this from the client, you can get the information by performing a GlideRecord query. Here’s an example…

To get any additional information about the currently logged-in user from a client-script or UI policy, you need to use a GlideRecord query. If at all possible, you should use a server-side technique described above since GlideRecord queries can have performance implications when initiated from a client script. For the situations where there’s no way around it, you could use a script similar to the one shown below to query from the client for more information about the currently logged in user.

Useful Scripts

There are quite a few documented examples of some common uses of these script methods. These scripts can be found on the ServiceNow docs site .

Mark Stanger

Date Posted:

June 23, 2021

Share This:

29 Comments

Thanks for the great tips… My personal favorite:

gs.getUser().getRecord().getValue(‘title’);

never knew you could do that, awesome!

I was looking for a way to get the default set to the User Time Zone. Looked everywhere and it was on my favorite site..!

javascript:gs.getUser().getRecord().getValue(‘time_zone’);

Note that if you use this method, and you have the time zone selector turned on, you may run into issues. The time zone selector sets the User’s Session TZ, but not their default.

For more consistent results, use the following: var tzStr = gs.getSession().getTimeZoneName(); // “US/Pacific” var jTZ = gs.getSession().getTimeZone(); // sun.util.calendar.ZoneInfo java object. APIDoc linked below

Java doc ZoneInfo api: http://www.docjar.com/docs/api/sun/util/calendar/ZoneInfo.html

Thank you for the great work… finally one place to get the information about the UserObject stuff…

Just one note:

– the hasRole() returns true, if the user has the role specified (e.g. hasRole(role)) OR the admin role.

– to get a true/false for a specific role, use hasRoleExactly(role), which will only return true, if the user has the itil-role.

Thanks for the feedback. This method had some issues in the past (which is why I didn’t include it). It looks like it’s in the official ServiceNow doc now though so hopefully I’m safe in including it here :). I just added it to the article above.

I looked at the Usage example for “isMemberOf()” and also checked the wiki article for the function “getUserByID” ( http://wiki.servicenow.com/index.php?title=Getting_a_User_Object&redirect=no#Method_Detail ) but I cannot get it to work.

Is this function maybe retired?

Some code I played with is:

I’m not having any luck with it either. I haven’t heard of it being retired, but you’ll probably need to contact ServiceNow support to see. Please post back here with your findings.

Here we go: first we have to initialize a variable with “getUser()”. After that we can get any user object using it’s sys_id or UserID. Below the updated code to make the example work:

Thanks Andreas! I’ve updated the table above with this solution.

is it possible to check whether he/she is one of the member of Assignment group? Please guide me friends.

Yes. Check out ‘isMemberOf’ above.

sorry Mark. i forget to mention, is it possible to do this in client script?

Not directly. You could easily do a client-side GlideRecord query against the ‘sys_user_grmember’ table to find that though. Just make sure to do an asynchronous gliderecord query with a callback. You can find an example of this type of script here… https://servicenowguru.com/scripting/client-scripts-scripting/gform-getreference-callback/

Thanks Mark.

Thanks for all the info, very handy and interesting indeed. One question though, is there a method like the var hasRoleExactly that will work server-side? I can get it to work okay client-side but that’s it.

Thanks Martin

I don’t know of any built-in way of doing this, but you could always query the ‘sys_user_has_role’ table directly or create an on-demand script include that would allow you to call it in a shorthand way.

Thanks Mark, I thought that might be the alternative :)

How does one get the client’s business number? The wiki shows how to get the mobile number, but not the business number.

http://wiki.servicenow.com/index.php?title=Getting_a_User_Object

Up above I explain for both back-end and client-side code how you can get any attribute even if there’s not a specific function defined. You can get any attribute from the back-end like this. gs.getUser().getRecord().getValue(‘title’);

If I understand that correctly, then I could use this in a script of a workflow that works on a condition of an incident being submitted, to set the value of phone for the incident, to the user’s business phone, with the following script?

current.u_cos_contact_no = gs.getUser().getRecord().getValue(‘phone’);

Correct. As long as ‘phone’ is the name of the field you want to pull the value from.

On my incident form, “Contact Phone” variable is called u_cos_contact_no.

In my client’s user form, “Business Phone” variable is called phone.

For my workflow, would I want to do a custom script, or simply put do a Set Values, and then use javascript:gs.getUser().getRecord().getValue(‘phone’) ?

An update, I made a script step in the workflow, and the following works in my system:

var businessphone = gs.getUser().getRecord().getValue(‘phone’); current.u_cos_contact_no = businessphone;

Now to try it as a Set Value step in the workflow, with javascript:gs.getUser().getRecord().getValue(‘phone’); Not sure if it will work, but it’s work a shot to eliminate extra steps in the workflow.

Sorry to keep filling this up, but I can’t figure out how to edit my previous post.

On further testing, javascript:gs.getUser().getRecord().getValue(‘phone’) does work in a Set Value step of the workflow, however it pulls the phone number of the user logging in the incident, not the phone number of who the “client” has been set to for the incident. Any way to modify this?

Much thanks Mark

I wanted to know if we could access the company of the user involved, using the g_user field.

Thanks and Regards, Vivek

Sure. Take a look at the ‘title’ example at the bottom of the article. It shows how you can use a GlideRecord query to get any additional information about the user (including company) that you want.

These articles are so helpful, thank you Mark for making this public information.

Extremely helpful, thank you, Mark!

Article still relevant after 13 years. Amazing !

Comments are closed.

Randall King says:

• Business rules
• Client scripts
• Content management
• Email Notifications
• General knowledge
• Graphical workflow
• Integration
• Knowledge Management
• Miscellaneous
• Relationships
• Script includes
• Service Portal
• Single Sign-on
• System Definition
• Web Services

Related Posts

GlideRecord Query Cheat Sheet

Generate a GlideRecord Query for a List

Comparing the Differences Between Two Strings

Fresh content direct to your inbox.

Just add your email and hit subscribe to stay informed.

Since 2009, ServiceNow Guru has been THE go-to source of ServiceNow technical content and knowledge for all ServiceNow professionals.

• Application Portfolio Management (APM) assessment challenges
• Knowledge Translation using Localization Framework and Azure
• Localization framework fulfillment (LP, LRITM, LFTASK)

© Copyright 2009 – 2024 | All Rights Reserved

  Blog Home

  mvps,   flow designer, recent posts, we've moved, what's new in uib for vancouver, podcast: break point - career conversation with astrid sapphire, get ready, the devvies 2024 is almost here, hacktoberfest 2023, share this post, hands-on with gliderecord query.

#GlideRecord , #GlideRecord Query , #Server Side Scripting , #Scripting

9 minute read

We are experimenting with new training content delivery methods. This tutorial blog post is one of those experiments. We are very interested in your feedback. Please let us know what you think about this format and the content in the comments below.

Introduction

Newer developers in the Developer Program have requested additional hands-on work with GlideRecord. While many of the training modules include examples with GlideRecord, this “bonus exercise” adds hands-on experience with GlideRecords in Business Rules. The topics in this post build on concepts in the Server-side Scripting module.

In this exercise, you create three Business Rules.

• Guided: Create a Business Rule for new Incidents to check for active Incidents from the same caller and post an information message with the caller’s active Incidents.
• Guided: Create a Business Rule for Configuration Items (CIs) to check for active Tasks associated with the CI when the CI is decommissioned.
• Option 1: Create a similar Business Rule for new NeedIt requests.
• Option 2: Create a similar Business Rule for new Change Requests.

NOTE : This exercise uses demo data that may vary from your instance.

Create an Incident Business Rule

• Log in to your ServiceNow instance as a System Administrator.
• Use the Application Navigator to open Incident > Open .
• Change Go to to Caller and set the search value to *Berzle . Make note of how many records have Rick Berzle as the Caller.

Create a Business Rule.

• Right-click any column header and select the Configure > Business Rules menu item.
• Click the New button.
• Name: List Open Incidents by Same Caller
• Advanced: selected (checked)
• When: before
• Insert: selected (checked)

Configure the Advanced section.

Replace the contents of the script field with this script. NOTE : this script contains some text you will update in the next step.

Update the script with the class and methods.

• Replace CLASS with the class of the object to create.
• Replace QUERY_CONDITION_METHOD with the method to add a condition to the query.
• Replace RUN_QUERY_METHOD with the method to run the query.
• Replace ITERATE_METHOD with the method to iterate through the returned records.

QUESTION : What parameter do you pass to the CLASS? What are the parameters passed to the QUERY_CONDITION_METHOD? If you are not sure, scroll to the Answers section at the bottom of this page. NOTE : If you need help with any of these, see the Create an Incident Business Rule section in the answers at the bottom of this post for the complete script.

Click the Submit button.

Test the Business Rule.

• Use the Application Navigator to open Incident > Create New .
• Caller: Rick Berzle
• Short description: Received phishing email
• Click the Submit button. An information message lists active Incidents with Rick Berzle as the Caller.

Create a Configuration Item Business Rule

When a Configuration Item (CI) is deactivated, you want to update all tasks associated with the deactivated CI that the CI has been deactivated. In this hands-on section, you create a Business Rule for the Configuration Item [cmdb_ci] table that finds all tasks associated with the CI and writes a Work note that the CI has been deactivated.

• Add the Configuration item column to the Selected list in the location of your choice.
• Sort by Configuration Item so tasks with no Configuration Item are at the top of the list.
• Open the first Incident with no Configuration item.
• Set the Configuration item value to *JEMPLOYEE-IBM .
• Click the Additional actions button and select the Create Favorite menu item to easily return to the Incident later.
• Click the Additional actions button and select the Save menu item.

Create a Business Rule for the Configuration Item table.

• Click the Preview this record button for the Configuration item.
• Click the Open Record button in the preview.
• Click the Additional actions button and select the Configure > Business Rules menu item.
• Name: Update Tasks on CI Deactivation
• Table: Configuration Item [cmdb_ci]
• Update: selected (checked)
• Filter Conditions: [Status] [Changes from] [Installed]

Update the script with the object and methods.

• Replace TABLE with the table to query.
• Replace COMPARISON_FIELD with the field on a task record for the Configuration item.
• Replace COMPARISON_VALUE with the value from the CI record to match to the task.

NOTE : If you need help with any of these, see the Create a CI Business Rule section in the answers at the bottom of this post for the complete script.

• Add the Status field to the Computer form.
• Find and open the Computer named *JEMPLOYEE-IBM .
• Set the Status for *JEMPLOYEE-IBM to Retired .
• From the Favorites in the Application Navigator, select the Incident previously saved to the favorites.
• Find the message *JEMPLOYEE-IBM is no longer active in the Activities.

Did you do the hands-on exercise in this blog? Click here to let us know!

Challenge - Option 1 - Create a NeedIt Business Rule

Create a Business Rule for the NeedIt application from the Developer Portal training that finds and lists open NeedIt requests for the user in the Requested for field. Display the list in an information message.

Starting tips:

• Prepare the instance with the NeedIt application using the directions in Exercise: Prepare Instance for Server-side Scripting .
• Create the Business Rule for the NeedIt table.
• Use the Requested for field.

If you need help, see the Create a NeedIt Business Rule section in the answers at the bottom of this post for a sample script.

Challenge - Option 2 - Create a Change Business Rule

Create a Business Rule for Changes that find and lists other changes opened for the same Configuration Item. Dsiplay the list in an information message.

• What is the name of the Change table?
• What is the name of the Configuration Item field?

If you need help, see the Create a Change Business Rule section in the answers at the bottom of this post for a sample script.

Create an Incident Business Rule : Replace the placeholders in the script with the correct object and methods. Replace CLASS with GlideRecord Replace QUERY_CONDITION_METHOD with addQuery Replace RUN_QUERY_METHOD with query Replace ITERATE_METHOD with next If you are still stuck, review the components of a GlideRecord query in the Server-side scripting training module. The resulting script:

Question : What parameter do you pass to the CLASS? What are the parameters passed to the QUERY_CONDITION_METHOD? Answer : Pass the table on which to perform the query to the GlideRecord class. Pass the field name, operator, and value to the addQuery method.

Create a NeedIt Business Rule : Here is an example script for a Business Rule to get the list of other NeedIt requests for a user and write them to an information message.

Create a Change Business Rule : Here is an example script for a Business Rule to get the list of other Changes for a Configuration Item and write them to an information message.

Create a CI Business Rule : Replace the placeholders in the script with the correct table and query parameters. Replace TABLE with task Replace COMPARISON_FIELD with cmdb_ci Replace COMPARISON_VALUE with current.sys_id The resulting script:

• First Share Item
• Creating Your First Action

Developer Blog

Written with by the Developer Advocate team

Featured Posts

Conquer the #BuildWithRPA Challenge & Snag Exclusive Swag!

© 2023 ServiceNow Developer Blog . Powered by Hugo

Advance Your Career

GlideRecord Cheat Sheet

Below is a list of commonly used gliderecord code that you can come back to daily while writing scripts in servicenow., the examples are in no specific order - so just ctrl+f or cmd+f and search to find what you need.

Basic GlideRecord query

Get (sys_id)

Get a single GlideRecord with sys_id. A great way to return a single record when you know the sys_id of that record.

The standard ‘addQuery’ parameter acts like an ‘and’ condition in your query. This example shows how you can add ‘or’ conditions to your query.

OR (the simple way)

In addition to the example above this, you can also chain your ‘OR’ condition like below, which is usually simpler

Insert a new record

Update one or many records by querying the records, setting the values on the records, and then calling .update();

Delete one or many records by querying for the records and then calling the .deleteRecord() method

deleteMultiple (shortcut)

If you are deleting multiple records then the ‘deleteMultiple’ method can be used as a shortcut

addEncodedQuery

Encoded query strings can be copied directly from a filter, by right-clicking on the breadcrumbs

GlideAggregate

Aggregates include COUNT, SUM, MIN, MAX, AVG

orderBy/orderByDesc

Order the results of your recordset by using ‘orderBy’ and/or ‘orderByDesc’ as shown below.

addNullQuery

Used to search for empty values

addNotNullQuery

Used to search for not empty values

getRowCount

Used to get the number of results returned. Not available client-side.

‘getRowCount’ isn’t available client-side, however you can return the number of results in a client-side GlideRecord query by using ‘rows.length’ like below:

Used to limit the number of results returned

chooseWindow

ChooseWindow will return all records between the first parameter(inclusive) and the second parameter(exclusive), so this example will return the 10 incidents between record 10-19 both inclusive. Works with orderBy

setWorkflow

Used to enable or disable the triggering of Business Rules

autoSysFields

Used to prevent updating fields such as sys_updated_on, sys_updated_by, and other 'sys' fields

setForceUpdate

Used to force an update, even when no fields are changed, and thus force the update to execute

setAbortAction

Sets the next database operation to be aborted. Useful to prevent updates if specific criteria is met.

List of Operators

These operators can be used in addition to the standard field/value query searching shown above…

Thanks for using our GlideRecord Cheat Sheet!

Looking for something else? Check out our other Cheat Sheets below!

• GlideForm (g_form) Cheat Sheet
• User Object Cheat Sheet
• Release / Version Cheat Sheet
• gs.getUser - The Complete Guide
• How to find a background script that you lost
• How to add a hyperlink to an addInfoMessage
• How To Export Your Favorites

Credit: ServiceNow Guru

How To Get Certified In ServiceNow

How To Move Updates Between Update Sets In ServiceNow

How To Add A Hyperlink To A Notification In ServiceNow

How To Script In Flow Designer

How To Dot-Walk Inside of a Client Script in ServiceNow

© Snowycode 2022. All rights reserved.

Configure the group type for assignment groups

Use the Type field to define categories of groups. Once defined,\n you can use these categories to filter assignment groups based on the group type using a\n reference qualifier.

For example, when selecting an assignment group from the Incident form,\n Type can be used to filter groups based on whether they are typically\n involved in the Incident management process. Groups such as Network or Help Desk are displayed\n as they are typically involved. Groups such as HR or New York are omitted.

The following items are provided in the base system.

• The types catalog , itil , and\n survey .
• The reference qualifier on [task.assignment_group] filters on [Type] [equals]\n [null] .
• A reference qualifier named GetGroupFilter is available to filter for\n group types using Create a dynamic filter option .

Add a new group type

You can add additional group types to filter assignment groups for tasks.

You may need to configure the form to display the Type \n field.

• \n Navigate to All > User Administration > Groups . \n
• \n Select a group record. \n
• \n Click the lock icon beside Type . \n
• \n Click the lookup icon beside the selection field. \n The Group Types dialog opens. \n
• \n Click New . \n
• \n Enter the group type name and description. \n For example, to define a type for a group as\n incident and problem ,\n enter: incident,problem . \n Click Submit . \n
• Optional: \n Add additional group types if needed. \n
• \n Click Update . \n

Assign a group type

You can assign group types to filter assignment groups for tasks.

• \n Navigate to All > User Administration > Groups and select the desired group. \n
• \n Click the lookup icon beside the selection field and select one or more group\n types. \n \n Note: Because the default behavior of\n task.assignment_group is to filter out groups with\n group types defined, adding a type to a group filters it out of the\n Assignment Group field on tasks. To change the\n behavior, set up the reference qualifier. \n\n \n

Best Practices - GlideRecord

• Use the appropriate object methods based on your scope - GlideRecord - Scoped GlideRecord
• Use GlideAggregate instead of getRowCount() for large tables and production instances
• Perform all record queries in server-side scripts for improved performance
• Use _next() and query() for tables containing next and query columns
• When deleting/inserting/updating records with GlideRecord methods, practise writing the list of records to a log to insure you do not accidentally modify records you still need before enabling the methods and modify the database (there is no undo!)

results matching " "

No results matching " ".

• Integrations
• ServiceNow Basics
• Service Mapping
• Scripting In ServiceNow

gliderecord examples in servicenow

GlideRecord is a class used to interact with your ServiceNow instance’s database from inside of a script . This GlideRecord class provides many helpful API methods to retrieve, update, create or delete records stored in your ServiceNow instance.

Query From Table

Standard GlideRecord Query Example

Output: Use while statement if you want to get multiple record, in my case i have used if so its return only one record. Value might be differ in your case.

Insert Example

Create a new Incident record and populate the fields with the values.

Update Example

Find all incident records which has empty coller and make them cancel and inactive.

Output: It will make inactive and cancel list of record which has empty caller.

Delete Example

Find incident records and delete them one-by-one.

deleteMultiple(): can be use to delete all record from set.

glideAggregate Example

GlideAggregate is an extension of GlideRecord. It provides the capability to do aggregation (COUNT, SUM, MIN, MAX, AVG).

These operations also we can perform with regular GlideRecord, but if you are doing with GlideAggregate, then it will be optimized and responsive.

Output: Value might be differ in your case.

setAbortAction Example

Abort the operation if validation fails.

Lets say you have two fields date1 and date2 on incident form and you want to make sure that date2 should always be grater or equal to date1 and if it fails then stop the operation and display message to user stating that Start date must be before end date.

Output: If validation fails then it will display message to user stating ‘Start date must be before end date’ and abrupt the operation.

OR Query Example

Note: Use addQuery() for ‘And’ operation

Output: It will give you list of incidents which has state Resolve or Closed or Canceled.

Shortest way to query from Table

Get single record from table

Explanation:

• Create an object using new operator and pass table name as parameter of GlideRecord.
• Now use get() function and pass the sys id of record.
• This two line of code will give you single record.
• Now you can get the value using object.column_name

Output : Value might be differ in your case.

Get multiple records from table

• Now use get() function and pass key pair value.
• This two line of code will give you multiple records.
• You can run the loop and get the value using object.column_name.

Output: You will get list of problem number which has category = ‘software’.

setLimit In Query

To enhance the query performance its recommended to use setLimit.

ChooseWindow will return all records between the first parameter(inclusive) and the second parameter(exclusive), so this example will return the 10 incidents between record 10-19 both inclusive. Works with orderBy()

getRefRecord Example

It is used to get the object of any reference field.

Encode Query Example

orderBy Example

orderByDesc() can be used in the same way to display data in descending order.

Output: orderBy() can be used when you want to display/order your data in ascending. In this example incidents will be displayed in ascending order by category.

getRowCount Example

Output: You will get count of active incident.

addNullQuery And addNotNullQuery Example

addNotNullQuery() is just opposite to addNullQuery, it will give list of incidents which caller id is not empty.

Output: It will give list of incident which caller id is empty.

setWorkflow(false) Example

If you wanted to update the record but at the same time you don’t want to trigger any other business rule which are running on the same table.  To overcome from this situation you can use setWorkflow(false).

Output: Query will update the target record but other business rule which are running on incident update will be skipped.

autoSysFields Example

Sometime you might come in a situation where you want to update the record but at same time you want to update the system field like updated, updated_by etc.

You can use autoSysField(‘false’) in your code to do so.

Output: It will update the short description with value ‘This should not be empty..’ but it will not update the system fields.

System field which will get update skip: sys_updated_by, sys_updated_on, sys_mod_count, sys_created_by, and sys_created_on.

Get Latest Update From Runjay Patel

We don’t spam! Read our privacy policy for more info.

You’ve been successfully subscribed to our newsletter!

RELATED ARTICLES MORE FROM AUTHOR

Return multiple values to glideajax from script include, g_scratchpad in servicenow, client script in servicenow, leave a reply cancel reply.

Save my name, email, and website in this browser for the next time I comment.

EDITOR PICKS

Barcode or qr codes generation in servicenow, how to become a certified system administrator (csa), servicenow versions / release, popular posts, access control list – acl, software asset management servicenow – sam-pro, customer service management (csm), popular category.

• ServiceNow Basics 22
• Scripting In ServiceNow 20
• Integrations 4
• Service Mapping 2
• Terms & Conditions

The Snowball

A ServiceNow Blog & Newsletter

Creating Records With GlideRecord initialize() and insert()

What Are initialize() and insert()? In ServiceNow scripting, a common requirement is to create new records in a table. While this can be done manually through the UI, using scripts with initialize() and insert() methods …

Written by: Team Snowball

Published on: July 16, 2023

Buy The 'ServiceNow Developer Manual' Here!

Buy The " ServiceNow Developer's Manual " Now

We've packed over a decade of ServiceNow Development advice, into a single e-book.

The Snowball will contribute 5% of your purchase to remove CO₂ from the atmosphere.

Table of Contents

What Are initialize() and insert()?

In ServiceNow scripting, a common requirement is to create new records in a table. While this can be done manually through the UI, using scripts with initialize() and insert() methods automates the process, saving time and effort. But what makes scripting such an essential tool for ServiceNow admins and developers?

Scripting for record creation not only increases efficiency but also promotes data integrity by reducing human error. It’s crucial, however, to exercise caution. Misuse of these scripting methods can lead to unintended consequences, like data overwriting or duplication. Always ensure your scripts target the correct tables and fields, and employ good practice like validating data before inserting.

In ServiceNow, initialize() and insert() are methods of the GlideRecord class. The initialize() method prepares a new record for entry into a database table, and the insert() method submits the new record to the database. It’s like preparing a letter ( initialize() ) and posting it ( insert() ).

Using initialize() and insert() In A Coding Example

Here’s a real-world scenario. Imagine you need to automate the creation of a new incident record when a specific type of email is received. You might create a script like this:

In this example, we’re using initialize() to prepare a new incident record. We then set the ‘short_description’ and ‘description’ fields before using insert() to add the new record to the ‘incident’ table.

Alternatively, you might need to create a new user in the ‘sys_user’ table based on data received from an external API as a JSON object. Here’s an example:

In this script, we’re using a JSON object named userData to store the new user’s information. We then use initialize() to prepare a new record in the ‘sys_user’ table and insert() to create the new user.

Can I Leave Out Initialize()?

The initialize() method in ServiceNow is used to initialize a new GlideRecord. When you’re creating a new record, initialize() sets default values for the fields in the record and prepares it to be filled with data before being inserted into the database.

If you leave out initialize() , ServiceNow will still let you create a new GlideRecord and set its fields. The insert() method will create the new record in the database, even if initialize() was not called.

However, the initialize() method can be useful if the table has default values set for certain fields. When initialize() is called, it sets these default values in the new GlideRecord. If initialize() is not called and you don’t manually set these fields, they may not contain the correct default values when the record is inserted.

Therefore, the best practice is to use initialize() when creating a new GlideRecord to ensure that all fields have their correct default values. This can prevent bugs and unexpected behavior in your scripts and applications.

Creating records with initialize() and insert() in ServiceNow scripting can profoundly enhance your workflow by automating routine data entry tasks.

Utilizing JSON objects in your scripts allows you to handle complex, structured data efficiently, making your scripts more dynamic and powerful.

As a ServiceNow admin or developer, mastering these scripting methods will equip you with a valuable toolset to streamline your operations and ensure data integrity.

Remember, the key to effective scripting is understanding your data, knowing your tables and fields, and always testing your scripts thoroughly. Happy scripting!

What Do You Think About This Article?

About Team Snowball

How To Send A JSON Object Body With The RESTMessageV2 API – Use setRequestBody()

Using nil() to check for null values with gliderecords.

The Now Platform® Washington DC release is live. Watch now!

ServiceNow Community servicenow community

• English (US)
• English (UK)
• Portuguese (Brazilian)

• ServiceNow Community
• Discussions
• Developer forum
• Background script to resolve the incident and upda...
• Subscribe to RSS Feed
• Mark Question as New
• Mark Question as Read
• Float this Question for Current User
• Printer Friendly Page

Background script to resolve the incident and update the state of all attached sla to complete.

• Mark as New
• Report Inappropriate Content

‎07-24-2023 09:10 AM

• All forum topics
• Previous Question
• Next Question

‎07-25-2023 12:20 AM

• Converting Text to a PDF Attachment in ServiceNow: A Complete Guide in Developer forum yesterday
• Facing an issue with background color on chart in certain themes in Developer forum Monday
• Create Custom Automated Playbook Activity in Developer blog 3 weeks ago
• Issue with Do the following until checkbox variable lookup in Developer forum 4 weeks ago
• Elevate Your Mobile Experience with ServiceNow's Latest Innovations in the Washington DC release🌐✨ in Developer Advocate Blog 03-27-2024

Victor Mukhin

• Scientific Program

Title : Active carbons as nanoporous materials for solving of environmental problems

However, up to now, the main carriers of catalytic additives have been mineral sorbents: silica gels, alumogels. This is obviously due to the fact that they consist of pure homogeneous components SiO2 and Al2O3, respectively. It is generally known that impurities, especially the ash elements, are catalytic poisons that reduce the effectiveness of the catalyst. Therefore, carbon sorbents with 5-15% by weight of ash elements in their composition are not used in the above mentioned technologies. However, in such an important field as a gas-mask technique, carbon sorbents (active carbons) are carriers of catalytic additives, providing effective protection of a person against any types of potent poisonous substances (PPS). In ESPE “JSC "Neorganika" there has been developed the technology of unique ashless spherical carbon carrier-catalysts by the method of liquid forming of furfural copolymers with subsequent gas-vapor activation, brand PAC. Active carbons PAC have 100% qualitative characteristics of the three main properties of carbon sorbents: strength - 100%, the proportion of sorbing pores in the pore space – 100%, purity - 100% (ash content is close to zero). A particularly outstanding feature of active PAC carbons is their uniquely high mechanical compressive strength of 740 ± 40 MPa, which is 3-7 times larger than that of  such materials as granite, quartzite, electric coal, and is comparable to the value for cast iron - 400-1000 MPa. This allows the PAC to operate under severe conditions in moving and fluidized beds.  Obviously, it is time to actively develop catalysts based on PAC sorbents for oil refining, petrochemicals, gas processing and various technologies of organic synthesis.

Victor M. Mukhin was born in 1946 in the town of Orsk, Russia. In 1970 he graduated the Technological Institute in Leningrad. Victor M. Mukhin was directed to work to the scientific-industrial organization "Neorganika" (Elektrostal, Moscow region) where he is working during 47 years, at present as the head of the laboratory of carbon sorbents.     Victor M. Mukhin defended a Ph. D. thesis and a doctoral thesis at the Mendeleev University of Chemical Technology of Russia (in 1979 and 1997 accordingly). Professor of Mendeleev University of Chemical Technology of Russia. Scientific interests: production, investigation and application of active carbons, technological and ecological carbon-adsorptive processes, environmental protection, production of ecologically clean food.   

Quick Links

• Conference Brochure
• Tentative Program

• Phone: +90 (212) 875 19 08
• E-Mail: [email protected]

• Company Profile
• Company Policy
• Mission and Vision
• Certificates
• Aluminium Windows
• Aluminium Doors
• Aluminium Sliding Elements
• Aluminium Curtain Walls
• Aluminium Skylight Elements
• Aluminium Frames for Safety and Security
• Aluminium Conservatories
• Metal Panel Sheet Claddings
• Aluminium Entrance Frames
• Glass Structures
• Complementary Items
• Lightweight Steel Structures
• Human Resources OPEN

Metropolis Office & Shopping Center

Sheremetyevo airport, new georgian parliament building, be ready to view the world from our frame.

Our Projects

New airport, tobolsk, russia.

In progress

Rumyantsevo Home City Residential, Russia

200 East 20th Street, USA

St Pancras Campus, London, United Kingdom

Central Bank of Iraq

Poklonnaya 9, Moscow, Russia

Dar Es Salaam Station, Tanzania

Msk Symphony 34 Residential, Moscow, Russia

Morogoro Station,Tanzania

Multifunctional Medical Center, St. Petersburg, Russia

Setun (JK Hide), Moscow, Russia

Donbass Arena, Donetsk, Ukraine

ЖК FORIVER, Moscow, Russia

AFI PARK, Moscow, Russia

Paveletskaya Plaza, Moscow, Russia

Upside Berlin, Germany

Nobu Hotel London Portman Square, London, United Kingdom

Perrymount Road, London, United Kingdom

Nusr-ET Restaurant, Knightsbridge, London, United Kingdom

Istanbul Grand Airport, Turkey

New Georgian Parliament Building, Georgia

Anthill Residence, Istanbul, Turkey

Arcus III Office Center, Moscow, Russia

168-176 Shoreditch High Street, London, United Kingdom

Apex House, London, United Kingdom

Addlestone Town Centre, London, United Kingdom

Dream Island, Moscow, Russia

Skolkovo Business Center ‘Gallery’, Moscow, Russia

Cisco IT Skolkovo, Moscow, Russia

Studio Stage ‘Mosfilm’, Moscow, Russia

Sheremetyevo Airport, Moscow, Russia

Varobevskoe Housing, Moscow, Russia

Tushino Housing, Moscow, Russia

Yasniy Housing, Moscow, Russia

One Trinity Place (2nd Phase), St. Petersburg, Russia

Trinity Place, St. Petersburg, Russia

Action 44, Moscow, Russia

White Gardens, Moscow, Russia

I’m Moscow, Russia

Metropolis Office & Shopping Center, Moscow, Russia

Mayak Housing, Moscow, Russia

Dostoyanie Housing

Nasledie Housing 1

Nasledie Housing 2

Nasledie Housing 3

Life Botanic Garden Residential Complex

K2 Business Park, Moscow, Russia

Prisma Business Center

V-House Housing

Kuntsevo Office Complex

House of Justice

Algoritm Business Center, Moscow, Russia

Demidov Business Center

Rublevo Park Housing

Novopetrovskaya Shopping Center

Shopping-entertainement Complex ‘Kaleidoskop’

Barrikadnaya Bank Building

Beyoglu Loft

Radisson Blu, Istanbul

Sutluce Office

Information Center, Istanbul

• Client log in

Metallurgicheskii Zavod Electrostal AO (Russia)

In 1993 "Elektrostal" was transformed into an open joint stock company. The factory occupies a leading position among the manufacturers of high quality steel. The plant is a producer of high-temperature nickel alloys in a wide variety. It has a unique set of metallurgical equipment: open induction and arc furnaces, furnace steel processing unit, vacuum induction, vacuum- arc furnaces and others. The factory has implemented and certified quality management system ISO 9000, received international certificates for all products. Elektrostal today is a major supplier in Russia starting blanks for the production of blades, discs and rolls for gas turbine engines. Among them are companies in the aerospace industry, defense plants, and energy complex, automotive, mechanical engineering and instrument-making plants.

Headquarters Ulitsa Zheleznodorozhnaya, 1 Elektrostal; Moscow Oblast; Postal Code: 144002

Contact Details: Purchase the Metallurgicheskii Zavod Electrostal AO report to view the information.

Website: http://elsteel.ru

EMIS company profiles are part of a larger information service which combines company, industry and country data and analysis for over 145 emerging markets.

To view more information, Request a demonstration of the EMIS service