how to set assignment group in servicenow business rule

Controlling record access using ‘Before Query’ business rules

S ystem security is probably one of the more challenging things to implement in Service-now.com.  While an out-of-box ServiceNow instance comes with the core security built-in, any implementation will inevitably have customizations in this area.  At some point, I plan on writing a basic security guide to help administrators and consultants make informed decisions about how security should be implemented in their systems.

One little-known, but extremely useful access control method is to use business rules to restrict record access in your system.  You can do this by creating what I call a ‘Before Query’ business rule.  These business rules have a ‘When’ value of ‘Before’ and also have the ‘Query’ checkbox selected.  ‘Before Query’ business rules are only used when you need to restrict access to certain rows within a table for certain groups of individuals.  Because the security is controlled by a script, the restriction can be applied based on roles, group membership, company or department information from the user record, or pretty much anything else that you can derive about the user trying to access a set of records.  There are a few of these business rules out-of-box that serve as great examples of how to implement security in this way.  When I need to implement security with a ‘Before Query’ business rule, I usually start with the ‘incident query’ business rule as my template.

The purpose of the ‘incident query’ business rule is to limit the access of records (rows) on the ‘Incident’ table.  Specifically, it says that you need to have the ‘itil’ role to access incident records unless you are the person listed as the Caller or Opened by on the Incident.  It is because of this business rule that your end-users can only see their own incident records in the system!  Below is the script (along with comments explaining exactly how it works).

Here’s another example. This time we will restrict visibility to records if the user is a member of the current assignment group.

Mark Stanger

Date Posted:

January 4, 2010

Share This:

33 Comments

Thanks for this. Exactly what I was looking for. When in doubt, I turn to Service-Now Guru :-).

Would you happen to know if visibility restrictions can be applied to Support Skills? For instance, can I restrict the appearance of a Support Skill to specific roles?

I haven’t ever seen that done for the specific requirement you mention, but it should be possible to limit the visibility of those records using this technique.

Thank you for the link to your site – very useful, I shall enjoy exploring it.

I’ve taken a look at the script above and was wondering if this will restrict the view for all users? What I want to do is restrict it just for a specific group.

I.e. all staff with an ITIL role can see all Incidents, except for members of a specific group who should only see those that are assigned to their group.

Is this possible?

It will apply the restriction for ALL users. If you only wanted to apply it to a specific group you would need to wrap the whole thing in an additional ‘if’ statement to check and see if they were part of the specific group (or if they have some additional role).

This is exactly what I’m looking for but ran into what looks like a problem. I’ve implemented this but it doesn’t apply the restriction to the closed records.

I pretty much copied and pasted the business rule.

Hard to say what the problem might be without having access to the instance you’re working in. The scripts here work correctly and have been tested and confirmed. If you pasted directly into a business rule with the syntax editor on then you might have some errant spaces in there. You might try pasting into the script field with the syntax editor disabled if that’s the case.

Hello Mark, We have run into a situation with our MSP instance where the customers security team has exposed security holes where any system table is readable by any users by accessing it from the url example https://demo.service-now.com/sys_user_has_role_list.do Since we are on “Allow all” model of our instance. What would be the best way to

1) Identify the System tables Total count of tables in the instance 870. 2) Should ACL be used or the business rule mentioned above. 3) In either case we need to create entries for approximately 500 system tables(rest of the tables being data tables) what is the best way to automate this.

Any guidance with this regards woud be appreciated.

Regards, Dhanraj Poojari

I don’t think you’re going to find a quick and easy solution to this problem. If I were you, I would probably start by moving to a default deny model and working from there. You’re still going to have to make some ACL modifications, but I think you’ll end up with a much cleaner solution when you’re done. You’ll need to make sure to go through a thorough QA cycle after turning on the plugin to make sure the default deny doesn’t break anything but I still think that’s the best route. http://wiki.service-now.com/index.php?title=High_Security_Settings

In your article you state that the Before Query can be applied to an attribute from the User table. What is the proper way/syntax to use for this? For example, we have an “External Customer” check box on the user table and I want to start by stating “If the user is external, current.AddQuery…”

Check out my user object cheat sheet for details on accessing specific user information in script. In this case, I think you’ll just need an ‘if’ statement like this…

Hallo everybody,

I tried to apply the logic on to the sc_category table in order to hide some elements dynamically from the service catalog. But whatever I did – the business rule didn’t get executed when the service catalog is requested (catalog_home.do?sysparm_view=catalog_default)

Regards Thomas

I don’t think a before query rule will work there because the query logic works a bit differently for that page. There are some very robust ways to limit access to catalog categories and items though. Check out this wiki article for details.

http://wiki.service-now.com/index.php?title=Service_Catalog_Security

Has this been tested and used on the latest: Calgary? I don’t seem to have access to the ‘curren’t record when running a before BR having the query box selected. Perhaps something else is stopping this from working properly. It runs when testing against the gs user (for roles, etc.) but not any fields within ‘current’.

It works in Calgary. ServiceNow uses this in several places out-of-box, including the ‘incident query’ business rule.

Specifically with the assignment group and isMemberOf. The OOB is only testing for role of the currently logged in user. I plugged this into a demo and is does not work nor does it work on my instance. Again, I’m referring to !gs.getUser().isMemberOf(current.assignment_group).

By the way, this site is such a wealth of information and neat hacks. I love discovering new things to play with.

Thanks Allie. I’m not sure exactly what you’re asking in your comment though. The whole point of a ‘Before Query’ business rule is to secure records based on the currently logged in user. If it’s not working, then there’s probably something else going on in your script.

Apologies for not being clear. Let me try again.

Your example has the following test:

if (!gs.getUser().isMemberOf(current.assignment_group) && gs.getSession().isInteractive())

The OOB incident query has this test:

if (!gs.hasRole(‘itil’) && gs.getSession().isInteractive())

One is testing the user against the field current.assignment_group and the OOB is testing against the user’s roles and nothing to do with the current records. You don’t start querying the current record fields until you are in the loop and doing a current.addQuery. When I add some debug info messages it appears that the current.assignment_group is never queried and all I get is a blank for group and the test always fails. If I change this to display rather than before, my debug messages work but, of course, the outcome is not what we’re after.

What I did to ensure it wasn’t something unique to my instance is try this on demo. I copied your exact example, added a few users to the right groups, and it does not work. I haven’t made any changes to the code yet.

Any chance you can try the example above (with the assignment_group test) in a demo or on a few of your own instances on Calgary? I’m really at a loss.

The only problem is that the code is wrong! :) You’re right that ‘current’ in this case applies to the query, not to individual records. In order for this to work, you have to modify the query, not try to place a ‘current’ condition around it. I’ve updated the code snippet above with something that should work better. Let me know how it goes.

Ahhhh. Thank you much. Works perfectly now.

How would you control access to sc_cat_item records based on the “Available for company” related list?

If you create a reference field on a form that references the sc_cat_item table, you get all records. We would like to filter the results the same way they are filtered in the Service Catalog.

An example of this is the “Request item” reference field in the New Call module (from the Service Desk Call plugin) — it lists all catalog items, including items that are restricted to other companies.

ServiceNow really hasn’t made that very easy to do…especially in a reference qualifier scenario where the user accessing the list may be ordering on behalf of someone else. I don’t know of an included script to do this and it would probably be pretty complex to come up with on your own.

I’m trying to do something similar to the second example in your article. How would you construct the query if the field on the table is a List (glide_list) field referencing the Group[sys_user_group] table?

I tried the following which seems to work only if the user is a member of all of the groups in the u_group field.

var myGroups = getMyGroups(); var q = current.addNullQuery(‘u_group’); q.addOrCondition(‘u_group’, myGroups);

I want the record to be returned if the u_group field is empty, or if the user is a member of any of the groups in the u_group field.

Hi Mark – is it possible to use this function to restrict access to specific Standard Changes? For example if we have a standard change for changing the firewall it would not be prudent to allow anyone to choose this standard change – how would we go about locking the change for anyone other than a specific group or groups so it doesnt appear in the drop down list of changes for that specific Program Element?

That is possible, and may be a very good use for this type of functionality.

Have you ever tried this on glide list field, the field above is reference field and hence it is doable, but what if the field is glidelist, is it doable or not?

Best Regards, Namrata Jain

This isn’t tied to a particular UI component at all, since it’s tied to the actual database query it should work anywhere in the system.

I am trying to use a business rule to limit the HR Cases (hr_case table) which show via the Open module based on the logged in user’s assignment group AND based on 2 categories.

In short, if the logged in user is in the “Money” group, then they should only see cases where the Category is Benefits OR Payroll. The OR condition is causing me issues!

Thank you for your posts. They are always very helpful!

Shane, thanks for reading and for your comment! The examples above should show a couple of ways to add the ‘or’ condition. Honestly, these are usually pretty tricky for me as well. Sometimes I just eliminate the confusion completely by creating a filter in a standard list to show the records I want to show, then right-click the portion of the list breadcrumb to copy the query. Once you’ve done that, you can easily use ‘addEncodedQuery’ to add the exact same query that appears in the list. Check out this guru article for details on ‘addEncodedQuery’.

https://servicenowguru.com/scripting/gliderecord-query-cheat-sheet/

We implemented your solution and it affected 1 of our catalog itens in the following way: when requesting the item, on submit, the item is generated (REQ and RITM), but the RITM is generated without workflow associated to it. Have you ever seen this kind of scenario?

I don’t know of anything I have in this article that would impact request items at all. Depending on how you’ve implemented it, I suppose there’s a possibility that a query business rule could cause an issue but that’s probably a general ServiceNow question rather than something related to my explanations in this article. I’d contact SN support or the SN community for help on this.

Hi, we’ve noticed that the Before Query shows up in Global Text Searches.

Normally this is probably OK, but one of our Query Rules returns a very long encoded query, which then displays over more than 10 lines before the actual results are shown.

I’ve hidden the Filter using jQuery in a Global UI Script, eg $j(‘span.searchfilterdisplay’).hide(); but hoping there is a better way!

Cheers, Dav

Thanks so much for this! I am coming to express and learning new things about the platform and your site is very helpful, even for me who is very green with scripting. This worked perfectly!

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

Display Messages With UI Notifications

Prevent Redundant Approval Requests in ServiceNow

Schedule-based Date/Time Addition

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

ServiceNow: Building Powerful Workflows by Tim Woodruff, Ashish Rudra Srivastava, Martin Wood

Get full access to ServiceNow: Building Powerful Workflows and 60K+ other titles, with a free 10-day trial of O'Reilly.

There are also live events, courses curated by job role, and more.

Setting the Assignment group with Assignment Rules

Assignment Rules are a simpler alternative to Data Lookup. While Data Lookup is very powerful, allowing you to set any field, it does involve a quite a bit of configuration, including creating a new table.

In contrast, an Assignment Rule uses the simpler condition builder to specify when it should run. If it matches, then it'll either populate the Assigned to and Assignment group fields with a hardcoded value, or you can use a script. We have got the group we want to use in a property, so this option is perfect. Follow these steps:

• Name : Assign to External Team
• Table : Maintenance [x_hotel_maintenance] ...

Get ServiceNow: Building Powerful Workflows now with the O’Reilly learning platform.

O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Don’t leave empty-handed

Get Mark Richards’s Software Architecture Patterns ebook to better understand how to design components—and how they should interact.

It’s yours, free.

Check it out now on O’Reilly

Dive in for free with a 10-day trial of the O’Reilly learning platform—then explore all the other resources our members count on to build skills and solve problems every day.

Add users to Proactive Service Experience Workflows assignment groups

Add users to Proactive Service Experience Workflows assignment groups so\n that they have the necessary role and can be assigned to resolve network-initiated issues at\n the appropriate escalation level.

Role required: admin

• \n Navigate to All > User Administration > Groups . \n
• Network Coordinators
• L1 Network Engineering
• L2 Network Engineering
• L3 Network Engineering
• \n In the Group Members related list, click Edit . \n
• \n Select one or more names in the Collection list. \n
• \n Click Add . \n
• \n Click Save . \n

• ServiceNow Consulting Services
• ServiceNow IT Workflows
• ServiceNow Customer Workflows
• ServiceNow Employee Workflows
• Hyperautomation
• ServiceNow Implementation Services
• ServiceNow Integration Services
• ServiceNow Managed Services
• ServiceNow for Manufacturing Industry
• Digital Transformation In Banking
• Digital Transformation In Insurance
• Digital Transformation in Wealth & Asset Management
• Digital Transformation in Life Sciences
• Digital Transformation in Hospitals
• Digital Transformation for Payers
• Data Migration Utility
• 360 Degree Business Assessment
• ServiceNow Dx Support
• Service Automate
• Rome Release
• Case Studies
• News Events
• Infographic
• Thought Leadership

Handling Assignment Rules in ServiceNow

In ServiceNow, if one is looking for automatic assignments then he can rely on the instance’s ability to assign the tasks automatically to different users and groups depending on the specified conditions. In order to achieve this, ServiceNow has the following modules:

• Assignment Lookup Rules
• Assignment Rules

Assignment Lookup Rules:

This module appears under the ‘System Policy application’ menu. This table is basically generated out of the box as its definition is provided in the ‘Data Lookup Definition’ table in the instance, specifically for field assignments in the incident table. Assignment lookup rules mainly provide the functionality of changing any field value and not just the assignment fields.

Assignment Rules:

This module appears under the ‘System Policy application’ menu. It helps to automatically assign the tasks to a particular user or a particular group using the assigned_to and assignment_group fields respectively, depending on the specified set of conditions. One can define these assignment rules readily for their desired table.

Following are the steps for defining the assignment rule:

• Navigate to System Policy -> Assignment -> New

• From the above figure, one can see that the dot-walking can also be done in the condition builder field. Just select the ‘Show Related Fields’ option in the condition and then select the appropriate attribute.
• Further, in the ‘Assign To’ tab, select the appropriate user and group to whom the task is to be assigned.

If two assignment rules conflict, then the assignment rule with the lowest execution order runs first. The lower the execution order, the higher is the precedence.

Distinguishing Factors between the Data Lookup Rules and Assignment Rules:

Precedence among the assignment rule and business rule:.

In certain circumstances, the business rules gain precedence over the assignment rules.

The business rules and assignments rules run in the following order:

• All the ‘before record insert’ business rules having order less than 1000.
• First and foremost, assignment rule with lowest execution order and matching condition.
• All the ‘before record insert’ business rules having order more than 1000.
• All the ‘after record insert’ business rules.

We are pretty sure that this blog must have given an overview of dealing with Assignment Rules in ServiceNow.

Any comments\suggestions are most welcome. We have posted further blogs as well on other topics and will frequently come back with something innovative.

Share This Story, Choose Your Platform!

Your browser or one of your plugins is not allowing JavaScript to be run. This is a bummer since the ServiceNow Developers Site is dynamic and depends on JavaScript to function. If you want to visit this site, please disable the plugin, activate this site for JavaScript or use another browser.

The Snowball

A ServiceNow Blog & Newsletter

How To Randomly Auto Assign Tasks in ServiceNow

Auto Assign Capabilities – What is Out Of Box? By default, when any record is assigned to a group, there’s no automatic behavior to update the “Assigned to” user. There is no round robin or …

Written by: Team Snowball

Published on: July 8, 2021

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

Auto Assign Capabilities – What is Out Of Box?

By default, when any record is assigned to a group, there’s no automatic behavior to update the “Assigned to” user.

There is no round robin or auto assignments for groups, out of box. There is on-call scheduling but this requires an extra license and needs to be implemented properly.

A lot of IT Managers like the idea of using platform automation to make decisions. This solution can ultimately save people a lot of time and removes a lot of manual intervention. But it’s not a “one size fits all” solution. 

Usually when any task is created, there is just a notification set up to inform all of the members of the group that the case has been created, and that someone needs to go in and take ownership of it. While this is definitely helpful, notifications decrease in impact over time as the system continues to push them out. Notifications from ServiceNow should be used only when necessary.

So what happens if you have certain groups that are repeatedly unwilling to assign cases out? This feature can be implemented and skip any need for a manual intervention when it comes to assigning cases.

We can also properly “load balance” users that come in, but that’s for another and more detailed post. This post just covers how to have ServiceNow randomly select a user from a group, whenever it is assigned to a group. It does not count nor assign to individuals completely evenly.

Why Would You Want To Automatically Assign A Case?

There are countless reasons a team might ask for this.

Common reasons are “use of automation” or “not wasting time reading and assigning cases”. The ServiceNow Platform can be enhanced to make decisions dynamically.

This could be helpful if there are teams that have trouble delegating. The system makes the decision for them. But this should also not be used as a crutch, if teams aren’t doing their work in ServiceNow, this is probably not the best solution to encourage them.

For organizations that are large enough, I have seen it be the full time job of people to manually come in and assign cases to people, on a case by base basis. This is a huge waste of resources and can be easily solved via automation efforts.

A good use case for automatically assigning a case to a user of a group when it comes in would be if all of the users of a group can equally solve the cases that come in. If there’s no large knowledge gap, then it makes sense to implement some sort of auto triaging solution.

You may be able to further expand upon the idea here. You can take the script and modify it to auto assign based on any other condition you can think of.

This solution does not count assignments and make decisions based on that. For example, if there is a group of 2 users – it could assign 4 cases to one and 6 cases to another.

Something To Also Keep in Mind – Related To SLA’s

There is a debate amonst ServiceNow professionals on when to have the “Response SLA” condition met. Some companies prefer to the Response SLA met when a case is “assigned”. Others prefer to have the Response SLA met when the case has a fulfiller add a comment. That’s for you and your organization to decide.

But if your company has your Response SLA conditions set up to be met when an incident has an “Assigned to” user populated – then continue reading here. If that is the case, then the Response SLA will be instantly met, and will become a metric that doesn’t provide a lot of value. If all your incidents are being assigned on insert, then 100% of the SLA’s measuring response will be met on insert, and won’t even be tracked. It will appear that you are meeting 100% of responses, every time.

So be aware of this if you decide to implement this functionality.

How To Automatically Assign A Case At Random?

The solution here is a rather straightforward business rule.

Condition : current.assignment_group.changes() && current.active == true && current.assigned_to == ”

Note : You will likely want to update this condition. This condition will auto assign cases for EVERY group that exists.

So if you only want to limit this to certain groups, make sure to define that in the condition.

Script : (function executeRule(current, previous /*null when async*/ ) { // Call the function random(); // Define the function function random() { var group = current.assignment_group.toString(); // Find the group members of the current group var grMembers = new GlideRecord(“sys_user_grmember”); grMembers.addQuery(“group”, group); grMembers.query(); var array = []; // Add them all to an array while (grMembers.next()) { var user = grMembers.user.toString(); array.push(user); } var arrayLen = array.length; // Randomly select the user from the elements in the array var randomUser = array[Math.floor(Math.random() * arrayLen)]; var userName = new GlideRecord(‘sys_user’); userName.get(randomUser); // This is optional, but could be helpful current.work_notes = “Auto assigning ” + current.number + ” to random user: ” + userName.first_name + ” ” + userName.last_name; // Set the randomly found user in the group current.assigned_to = randomUser; } })(current, previous);

How To Test The Auto Assignment Business Rule

Go to the table that you created the rule against. For my example, I am used the incident table and didn’t limit it to any group, just for the example.

Create an incident and assign it to any group. Make sure not to populate the “Assigned to” field.

At this point, once you save/update the record – it should auto assign to a user in that group.

Are there other ways to accomplish this feature? Is your IT Organization doing something differently to handle this?

Go ahead and take the code above and improve upon it. The above script is just an idea of what you can accomplish.

What Do You Think About This Article?

About Team Snowball

How To Call a Script Include from a Business Rule In ServiceNow

How to delete (and restore) records with a background script.

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

business rules in servicenow

Table of Contents

Business Rule overview

What is business rule?

A business rule is a server-side script that runs when a record is displayed, inserted, updated, or deleted, or when a table is queried.

When business rules run

Business rules run based on two sets of criteria:

• The time that the business rule is configured to run relative to a record being modified or accessed.
• The database operation that the system takes on the record.

How to navigate to business rule in ServiceNow

• Go to System Definitions > Business Rules .
• Click  New .
• Fill in the fields, as appropriate.

Let’s have a closer look on the business rule form and see the purpose of each field.

Note – Delete and Query operations are available only when advanced checkbox is true.

Thanks for reading this article, i hope you liked it, if that so, do like and subscribe my YouTube channel. You can also join our telegram channel to clear your technical doubt.

YouTube Channel

Telegram Group

Facebook Group

Linked-In Group

Types of business rules in ServiceNow

We have four different type of business rules present in our system.

Let’s understand each one of them in detail

Before business rule

Before BR as name itself justify works Before a record is saved to the database. Business rules execute after form submission and before the record update in the database. It runs before the database operation, so no extra operations are required.

As shown in the figure above the user provides an input before BR is executed and then only changes are made to the database.

Scenario – We need to copy the short description from variable present on RITM to the short description of catalog task.

We will start by creating a new Before BR filling all the required fields.

Here is the script to achieve the above-mentioned scenario.

After business rule

After a record is saved to the database. Business Rules execute after form submission and after the record update in the database.

Scenario – We need to close the task if the respective RITM moves to Closed incomplete.

We will start by creating a new After BR filling all the required fields.

Async business rule

Async Business Rules run after records are inserted/modified/queried. Async and after works similar the only difference is async run asynchronously as Scheduled Jobs. Async BR are queued by the scheduler to run as soon as they can be fit in. This allows the current transaction to finish without waiting for the rule and give the control back to user to continue working.

Tip – Use async Business Rules instead of after Business Rules whenever possible.

Scenario : Attachment add to a particular variable in a certain catalog item should get attach to the record as well.

We all are aware that attachment made to a variable in any catalog item is not attached to the record itself and make it somehow difficult to send the same attachment via notification for the respective record. So, to achieve the same we are using Async Business Rule. Now, why async not after BR the answer is attachment might take time to get attach to the record so to make this smooth and without blocking user experience, we will be using this.

We will start by creating a new Async BR filling all the required fields, here we want this BR for a particular catalog item, so we are mentioning the same under filter conditions.

Display business rule

Display Business Rules run after the data is read from the database and before the form is presented back to the user. Display Business Rules execute when a user requests a record form.

Scenario – We need to set certain values on incident form if the logged in user is member of a particular group.

To achieve this use case, we first need to create a Display BR and then call the same in our client script. Please refer to the below attached screenshots.

Here is the BR to fulfil our work at server side.

Now, moving onto the client-side scripting to see how this g_scratchpad is called, and our requirement is achieved.

Before Query Business rule

Other than the four above mentioned rules we have Before Query rule. It is a type of business rule in ServiceNow that we can use to limit that what all records users can access from a given table. In other words, we can also say that it is used for data segregation on an instance. To understand this more clearly see the scenario mentioned below.

Scenario – We need to restrict the visibility of incident on our instance in such as way that user should only be able to view them if he is a part of the assignment group to which that incident is being assigned or is the caller for that incident.

We will start by creating a new Before BR and selecting the query operation then filling all the required fields.

Here is the script to achieve the above-mentioned scenario. In this you can see we have used the condition under advanced section to disable this rule if the user is ‘admin’.

Why should we use Before Query instead of ACL?

With the concept of before query first question which comes to our mind is that why we actual need this when we have ACL for restricting any kind of record in system. The answer is when Query BR restrict the access than user will not see any message at the bottom of page related to access restriction but if the same record is restricted from ACL than message such as “Numbers of rows removed from the list by Security constraints: 20” displayed to user.

So, for smoothening the user experience query BR is preferred over ACL.

Order of execution of different Business Rules

The above image show use how database is being updated once something is entered by user. We can clearly see the execution order of the different business rule and how they work one by one based on the conditions and operation selected.

QUERY > DISPLAY > BEFORE > AFTER

This is in simple words to make you understand the flow. First, the query rule runs to restrict the access of the data being presented to the user. Then the display rule is executed. After that Scripts are configured to execute before the database operation works. And finally, async and after is carried out. 

Best practices for a Business Rule

• Prevent recursive business rules – We should avoid using update() in a business rule script. The update() method triggers business rules to run on the same table for insert and update operations, leading to a business rule calling itself over and over.
• Enclose your script in functions – We should always enclose our script in functions because when a code is not enclosed inn functions it is available to all server side scripts.
• Write specific business rule – Always avoid writing complex rules as they will be difficult to debug.
• Know when to run business rule – There should be clarity about when to use Business Rule and specify the same in conditions for running your BR.

Advantage vs disadvantage

• Performance. When running code on the server, it often has a faster load time and   processing time than a client script.
• Can perform complex database lookups.
• Can dot-walk many levels, however three levels is often a recommend maximum.

Disadvantage

• They are not as user friendly as client scripts.

What is async business rule in servicenow?

What is before business rule in servicenow?

What is after business rule in servicenow?

What is display business rule in servicenow?

What is before query business rule in servicenow?

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

Barcode or qr codes generation in servicenow, how to become a certified system administrator (csa), servicenow versions / release, leave a reply cancel reply.

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

EDITOR PICKS

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 Now Platform® Washington DC release is live. Watch now!

ServiceNow Community servicenow community

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

• ServiceNow Community
• IT Service Management
• call script include from assignment rule and set g...
• Subscribe to RSS Feed
• Mark Question as New
• Mark Question as Read
• Float this Question for Current User
• Printer Friendly Page

call script include from assignment rule and set group value

• Mark as New
• Report Inappropriate Content

‎07-25-2023 02:19 AM

• All forum topics
• Previous Question
• Next Question

‎07-25-2023 02:30 AM

‎07-25-2023 02:32 AM

• How to retrieve values from table into a multi text field in ITSM forum Thursday
• Add the uploaded file to sys_attachment table in ITSM forum Thursday
• Widget is not updating the date selected in the Widget on the target record in ITSM forum Thursday
• Set values dynamically to a list collector catalog variable(Groups) in ITSM forum Wednesday
• Advance Reference Qualifier not Working in ITSM forum Wednesday

Tokyo Now Platform Administration

Define assignment rules, table of contents.

• Adoption blueprints
• Select your adoption blueprint
• Install applications for an adoption blueprint
• Activate a plugin on a personal developer instance
• Request a plugin
• List of plugins (Tokyo)
• Find components installed with an application
• Add a system property
• Create a system properties module
• Handle HTTP 500 errors
• Query join and complexity size limits
• NTLM authentication
• Proxy servers for SOAP clients
• Bypass the proxy server
• Table extension and classes
• Global default fields
• Tables module
• Delete a custom table
• Delete all records from a table
• Roll back patch upgrades or plugin activations
• Use the Deleted Records module to restore a deleted record
• Use the Delete Recovery module to restore a deleted record
• Use the Script Execution History module to roll back a Scripts-Background execution
• Create a table index
• Create a task
• Assignment lookup rules example
• Assignment rules module
• Condition editor example
• Data lookup rules
• Precedence between data lookup, assignment, and business rules
• Workflow assignments
• Baseline assignment rules example
• Create an assignment rule
• Important Task table fields
• Journal fields
• Create a planned task
• Create a baseline
• Measure time and effort
• Important planned task table fields
• Planned task scripts
• Planned task hierarchy
• Configure rollup for planned task fields
• Reminder table
• Task table modifications
• Tasks workflow
• Activate Time Card Management
• Create a time sheet policy
• Set a time sheet policy as default policy
• Assign a time sheet policy to a user
• Create a rate type
• Create time cards and log time through Time Sheet Portal
• Submit time sheet through Time Sheet Portal
• Log time and submit time sheets of your resources
• Create a time sheet
• Submit a time sheet
• Approve or reject a time sheet
• Copy time cards from a previous time sheet
• Auto-generate time cards
• Submit a time card
• Approve or reject a time card
• Record time worked
• Manage costs
• Domain separation and Time Card
• Tools for driving tasks
• Request many to many task relations
• Plugin manifest
• Define a relationship type
• Define a task relationship allowed from the task relationship type record
• Modify the displayed field
• Mark as Solution button
• Define task relationships with UI actions
• Define a dictionary override
• Dictionary entry form
• Dictionary attributes
• Modify the Glide durations format
• Generate a schema map
• View the schema map
• Reference default many-to-many relationships
• Create a database view
• Add a table to the database view
• Example left join in creating a database view
• Specify a field to return
• Relabel a column
• Specify the number of records to return
• Test the database view
• Create a function field to perform a database function
• Display function results in a database view
• Use disjunctions in complex queries
• Database views in the base system
• Configure the list layout
• Configure list calculations
• Omit record count in a list
• Configure list controls
• Advanced list control with scripts
• Controlling the sort sequence used to display lists
• Configure list editor properties
• Configure list control settings for the list editor
• Example - Restrict a table
• Example - Restrict a field
• Example - Restrict a field with a script
• Example - Restrict a field with a condition
• User preferences for list editing
• Enable or disable personal lists
• Control which roles can personalize lists
• Manage personal lists
• Administer detail rows
• Suppress filters and breadcrumbs with list controls
• Use script includes to suppress filters and breadcrumbs
• Increase the allowed number of breadcrumb entries
• Use list controls in hierarchical lists
• Activate context ranking
• Create a ranking definition
• Apply a new sort order to a list
• Rank stories in a related list
• Action script for list context menus
• Dynamic actions script for list context menus
• onShow script for list context menus
• Using the form designer
• Configuring the form layout
• Administering form personalization
• Administering form annotations
• Configure attachment system properties
• Disable attachments on a table
• Index attachments on a table
• Hide the attachment [view] link
• Configure attachment icons
• Create a UI macro for a formatter
• Create a formatter and add it to a form
• Activity formatter
• Process flow formatter
• Parent breadcrumbs formatter
• Approval summarizer formatter
• Override a formatter with macros
• Limit the number of activity stream entries
• Create a template using the Template form
• Create templates for related task records
• Create a template by saving a form
• Create records based on a template
• Create a module for a template
• Template bar
• Toggle the template bar
• Scripted templates
• Create a UI action
• Override a UI action for an extended table
• UI policies
• Advanced form configuration
• Choice list security
• Values to associate with choice labels for scripting
• Integer values for default choice lists
• Configure state field choice values
• View choice list definitions
• Add the condition count to a condition field
• Update a conditions field to use condition builder v2
• Database field type
• Dictionary entry data types
• Document ID field
• Function field
• Configure TinyMCE to allow deprecated tags
• Configure TinyMCE to allow JavaScript in URLs
• Formatting icons for the HTML field editors
• Extended functions
• Table functions in TinyMCE
• Customize TinyMCE attributes
• Highlight text in TinyMCE
• Insert a line break in the HTML editor
• Add a table to the HTML field
• Embed images in HTML fields
• Link to a website in HTML fields
• Embed videos in HTML fields
• Define video file types for HTML fields
• Disable user access to the image library
• Paste content into the HTML editor
• Image field type
• IP address field type
• Restrict the CODE tag in journal fields
• Validate HTML in journal fields
• Journal field display limits
• Enable the text field character counter
• Name-value pairs field type
• Target threshold colors attribute
• Territories assigned
• Dependent fields
• E.164 phone number field configuration
• Configure a territory phone display rule
• Enable dynamic creation for reference fields
• Configure cascade delete rules
• Define the reference key
• Display a reference field as a choice list
• Select a field as the table display value
• Tree picker lookup
• Reference field icon
• Configure the related incidents icon
• Configure the show workflow icon
• Constrain the assigned to field by role
• Constrain the assignment group field
• The INSTANCEOF operator in reference qualifiers
• Auto-complete for reference fields
• Recent selections
• Configure suggested text for string fields
• Configure suggested text for journal fields
• Supported wiki tags
• Create a Wikitext field
• Extend the functionality of a Wikitext field
• Make a field mandatory
• Change the field label or hint
• Delete a field from a table
• Hide email addresses in a watch list
• Configure order buttons on the watch list slushbucket
• Highlight list fields
• Modify string field length
• Specify a default field value
• Make a field dependent
• Require unique values for a field
• Define field styles
• Add auto-numbering records in a table
• Configure left padding of a system number in a table
• Prevent numbering gaps
• Enforcing unique numbering
• Installed with field normalization
• Enable a field type for normalization or transformation
• Create a raw field
• Run a single data job
• Run multiple data jobs
• Rollback a data job
• Create the normalization record
• Create a normal value
• Create aliases
• Apply aliases
• Create rules
• Coalesce records on a normal value
• Transform a field
• Create a transform definition
• Create a transform variable for a transform definition
• Create a script for a transform definition
• Create a transform category
• Pattern matching
• Domain separation and Field Normalization
• Installed with data policy
• Data policy fields
• Convert a UI policy to a data policy
• Convert a data policy to a UI policy
• Data policy debugging
• Create custom data lookups
• Add a state model and transitions
• Implement process flow and UI actions with a state model
• Installed with State Model
• Locale settings
• Session and reference currency
• Single-currency mode
• Price fields
• Default currency values in forms
• Default currency values in reports
• Default currency values in lists
• Default currency values in import and export
• Default currency values in scripts
• Schedule the rate update job
• Use your own currency-conversion rates
• Control default currency field configuration and use in an instance
• Change default currency decimal places
• Configure default currency fields in audit records
• Configure the currency optimizer
• Updating the Currency Instance record
• Understanding how FX Currency field conversions work
• Life cycle of records containing FX Currency fields
• Dot-walkable Currency Instance fields
• Understanding FX Currency values in lists and reports
• Add conversion rates using a custom rate table
• Configuring FX Currency global settings
• Add an FX Currency field to a table
• Identify the FX Currency field and its display parameters
• Set the reference currency
• Specify the rate table and date source for currency conversions
• Select the rate and target table fields used for filtering
• FX Currency values in import and export
• Define locales
• Activate a language
• Set the default language for an instance
• Set a fallback language
• Configure a language as reading from right to left
• Map languages and regions with the language selector widget
• User specific language
• Languages table
• Translated Name / Field table
• Message table
• Field Label table
• Choices table
• Translated text table
• Debug translations
• Localize price fields
• Set up locations
• System localization properties
• List non-translated items
• Create a new choice record
• Create a new language record
• Translate a client script message
• Translate a field label
• Translate a field value
• Translating text fields
• Translate a related list name
• Import a translation from an Excel spreadsheet
• Translate to an unsupported language
• Translating the knowledge base
• Translating Service Catalog cart labels
• Activate Localization Framework
• Components installed with Localization Framework
• Localization Framework support for Service Catalog items
• Virtual Agent Designer integration with Localization Framework
• Localization Framework support for Natural Language Understanding models
• Localization Framework support for Surveys
• Localization Framework support for Knowledge Base
• Localization Framework support for email notifications
• Localization Framework support for HR Service Delivery
• Create and configure a custom artifact
• Create a processor script
• Processor script functions
• Create a UI action for the custom artifact
• Read script helper functions for LFDocumentContentBuilder
• Create a custom email subflow
• RWS Translation Management System spoke
• Configure RWS TMS in the Localization Framework
• XTM Translation Management System spoke
• Configure XTM TMS in the Localization Framework
• Integrate with a translation management system
• Create a custom translation management system
• Configure the Localization Framework preferences
• Localization Framework Roles
• Workflows in the Localization Framework
• Creating Localization Project
• Adding localization request items to a project
• Request translations for Service Catalog items
• Request adhoc translation for Service Catalog items
• States of localization projects and tasks
• Translation modes
• Fulfill a localization task
• Approve a localization task
• Error messages in the Localization Framework
• Request translations from Insights Dashboard
• Activate Dynamic Translation
• Dynamic Translation properties
• DynamicTranslation API
• Create a credential for the MicrosoftTranslation alias
• Create a connection for the MicrosoftTranslation alias
• Activate the Microsoft translator configuration
• Create a credential for the IBMTranslation alias
• Create a connection for the IBMTranslation alias
• Activate the IBM translator configuration
• Create a Java KeyStore certificate
• Attach a Java KeyStore certificate to Google Cloud Translator Service spoke
• Create a JWT signing key for Google Cloud Translator Service spoke
• Create a JWT provider for Google Cloud Translator Service spoke
• Configure the credential for the GoogleTranslation alias
• Configure the connection attributes for the GoogleTranslation alias
• Access Dynamic Translation spoke actions from the Flow Designer
• Actions in Dynamic Translation spoke
• Language Detection spoke
• Create a translator configuration
• Create a language code mapping
• Migrate to version v3 of a translator configuration
• Limitations in Dynamic Translation
• Enable dynamic translation for a field
• Error messages in Dynamic Translation
• Translate a knowledge article from a translation task
• Dynamic Translation for Agent Chat overview
• Request for domain separation in Dynamic Translation
• Personalize the system date format
• Personalize the system time format
• Configure the date picker for the list editor
• Time worked
• Display resolve time as a duration
• Export date and time formats
• Default schedules
• Create a holiday schedule for multiple regions
• Parent and child schedules
• Schedule fields
• Schedule entry fields
• Schedule for the fifth instance of a week date
• Repeat a monthly schedule
• Invoke the Schedule page and view a calendar
• Schedule calendar
• Domain support and schedules
• Automate generation and distribution of a report
• Automatically generate something from a template
• Automatically run a script of your choosing
• Special cases in job schedules
• View a schedule item
• Event registry
• Register an event
• Escalation intervals and pause conditions
• Create a business calendar
• Create a business calendar group
• Define business calendar entries
• Define business calendar filtering options
• Pair business calendars with packages
• Activate Fiscal Calendar plugin
• Generate a fiscal calendar
• View, modify, and validate fiscal periods
• Set a system time zone
• Change the time zone choice list
• Change a time zone in a scheduled report
• Change a time zone in a scheduled data import
• Define a relative duration
• Use a relative duration
• Metric definitions
• Time configuration SLAs
• Time worked fields
• Create a timeline page
• Customize the timeline page span style
• Timeline sub item
• Display a metric as a timeline
• Make a timeline visible to a selected user
• Range calculator scripts
• Changes in perspective
• Managing spans
• Components installed with Client Transaction Timings
• Timing values
• Predictive Intelligence for Contextual Search
• Features of Search administration
• Exploring Search Suggestions
• Schedule the Build Search Suggestions script
• Schedule suggestion pruning
• Set maximum age for searches used in suggestion generation
• Test regular expression patterns in Search Suggestion Exclusion List Rule entries
• Analyze search relevancy
• Use the GraphQL REST API to view suggestions created from external user searches
• Search Suggestions tables
• Domain separation and Search Suggestions
• Search signal tables
• Features of Zing text indexing and search engine
• Global search displays a page of matching results
• Default display fields for global search tables
• Search settings filter and group global search results by table
• Global search displays exact matching records
• Global search displays your most recent search queries and results in Next Experience UI
• Configure parallel processing of search groups
• Revert to the legacy global search UI
• Set the preview limit for global or workspace search in Next Experience UI
• Hide per-table search result counts in Next Experience UI
• Add a workspace application to the Unified Navigation search context menu
• Update a type-ahead suggestion
• Configure "Did you mean?" suggestions
• List search finds records from the current table
• Boolean operators allow conditional search results
• Quotation marks allow exact phrase searches
• Wildcard characters allow searching for patterns and variations
• Enable or disable the Zing junk filter
• Zing generates search results in four phases
• Zing filters search results with access controls
• Score search terms by inverse document frequency (IDF)
• Set the relative weight of a field
• Zing indexes punctuation as part of some words
• Zing indexes some HTML elements
• Configure a table for indexing and searching
• Configure a text index group to search across multiple tables
• Zing index and search dictionary attributes
• Reindex a table without impacting text search results
• Regenerate the text index for a single record
• Remove an index
• Remove an index for a specific field
• Remove the text index for a child table
• Change the query mode of an indexed table
• Text indexing statistics and status
• Configure tables to use the Japanese tokenizer
• Configure a global stop word
• Configure a table-specific stop word
• Enable automatic stop words for a table
• Disable a stop word in Zing
• Zing matches derived words with stemming
• Enable search synonyms
• Create synonym dictionaries
• Select synonym dictionaries for a table
• Disable synonyms for a table
• Debug synonym searches
• Enable and disable Search Suggestions in Zing
• Set the maximum number of suggestions Zing displays
• Installed with Zing
• Exploring AI Search
• Assign roles to AI Search administrators and users
• Create an indexed source
• Indexed source retention policies and filter conditions
• Indexed source attributes
• Field settings
• Perform a full table index or reindex for a single indexed source
• Perform a full table index or reindex for multiple indexed sources
• Create a search source
• Preview matching records for a search source
• Create a search profile
• Link a search source to a search profile
• Publish a search profile
• Create a synonym dictionary linked to a search profile
• Create synonyms
• Clone a synonym dictionary
• Link a synonym dictionary to a search profile
• Unlink a synonym dictionary from a search profile
• Delete a synonym dictionary
• Create a stop word dictionary linked to a search profile
• Create stop words
• Clone a stop word dictionary
• Link a stop word dictionary to a search profile
• Unlink a stop word dictionary from a search profile
• Delete a stop word dictionary
• Modify settings for a typo handling dictionary
• Exclude a term from a typo handling dictionary
• Default Genius Result configurations
• Activate Q&A Genius Results
• Activate People Genius Results
• Link a Genius Result configuration to a search profile
• Set the evaluation order for Genius Result configurations in a search profile
• Create a Genius Result configuration
• Link an NLU model and intents to a Genius Result configuration
• Create a result improvement rule
• Boost search results using a result improvement rule
• Block search results and Genius Results using a result improvement rule
• Promote search results using a result improvement rule
• Create a search application configuration for AI Search
• Create a facet in an AI Search application configuration
• Configure navigation tabs in an AI Search application configuration
• Auto-complete suggestions in AI Search applications
• Using search scripted post-processors in AI Search application configurations
• Search result sort options in AI Search application configurations
• Enabling and configuring AI Search in Now Platform applications
• Enable automatic domain updates for a referenced table
• Request the External Content for AI Search plugin
• Create an external content schema table
• Defining access permissions for external documents
• Mapping external users and groups to Now Platform users
• Components installed with External Content for AI Search
• Configure AI Search Assist for a record producer
• AI Search Assist admin role
• AI Search Assist properties
• Domain separation and AI Search Assist
• Using AI Search
• Lemma and Unicode normalization
• Internationalization support for AI Search
• Machine learning relevancy in AI Search
• Content security in AI Search
• Encrypted fields in AI Search
• View AI Search ingestion log messages
• View all AI Search log messages
• Review ingestion history for an indexed source
• Enable session debugging for AI Search
• Diagnose search result access issues using the Search Preview UI
• Debug search source and content security filters
• Debug external content security filters for a Now Platform user
• Review record counts for indexed sources
• Plugins installed with AI Search
• Components installed with AI Search
• AI Search system properties
• Now Platform tables excluded from AI Search indexing
• Variable types supported by AI Search indexing
• AI Search index fields
• AI Search External Search User Mapping Table Data Source Relationship form
• AI Search Genius Result Configuration form
• AI Search Genius Result Configuration NLU Model Mapping form
• AI Search Results Improvement Rule form
• Child Table form
• Dictionary and AI Search Dictionary forms
• Dictionary Term form
• Field Setting form
• Indexed Source form
• Indexed Source Attribute form
• Indexed Source History form
• Navigation Tab form
• Record Producer Configuration form
• Rule - Action Mapping form
• Search Application Configuration form
• Search Profile form
• Search Profile - Dictionary Mapping form
• Search Profile - Genius Result Mapping form
• Search Profile - Search Source Mapping form
• Search Scripted Post-processors form
• Search Source form
• Sort Option form
• Suggestion Reader Group form
• Activate the Performance Analytics and Reporting Solution for Advanced AI Search Management Tools
• AI Search Profile dashboard
• AI Search dashboard
• Create a cross-scope access privilege for the AI Search dashboards
• Customize the banner logo for the AI Search Analytics dashboard
• Configure Service Portal to send analytics data
• Search Preview UI for AI Search
• Advanced AI Search Management Tools reference
• Install AI Search for Next Experience
• Verify that your instance meets the prerequisites for AI Search for Next Experience
• Migrate Zing search application configurations to AI Search
• Enable AI Search for Next Experience
• Add a new Unified Navigation workspace search configuration to AI Search for Next Experience
• Revert to Zing as the Unified Navigation search engine
• Repair AI Search for Next Experience after activating a new Now Platform language
• Enable search-based auto-complete suggestions in AI Search for Next Experience
• Using AI Search for Next Experience
• AI Search for Next Experience reference
• Components installed with Contextual Search
• Contextual search concepts
• Contextual search components diagram
• Contextual search properties
• Define a search context
• Configure table for a contextual search
• Create a filter configuration using mapping
• Create a filter configuration using scripts
• Configure search resource context properties
• Set a search context as default
• Set the default source for search context
• View a searcher
• Show the related search box in a form
• Add multiple search fields for contextual search
• Add additional resources to the source selector of a form
• Edit search resource display field record
• Specify fields for the Cxs_popup view
• Modify or disable search actions available for contextual search
• Enable viewing of search results for the current and another selected user
• Define contextual search for record producer
• Provide knowledge in incident email notification
• Edit an email notification for the search results
• Specify field for attached Knowledge article links
• Run a report on contextual search usage
• Domain separation and Contextual Search
• Intelligent Search for CMDB
• Event states
• The incident events business rule
• Sample scripts from the change events business rule
• Script actions
• Global events
• Create an event
• Reprocess an event
• Pass event parameters from a workflow to a notification
• Unique record identifier (sys_id)
• Create an archive rule
• Create a destroy rule
• Archive rule and destroy rule properties
• Manage archived data
• Data archive table size limits
• Data migration process for archiving table data from non-reference fields to reference fields
• Export limits
• Form export
• Determining which list fields are exported
• Use a URL query to filter a list result
• Query parameters for display value and header
• Export Set fields for display value and header
• System properties for display value and header
• Field types affected by export controls
• Default values for column headers and column values
• Exporting currency fields to Excel
• Call URL export programmatically
• Break up a large export
• Enable export debug logging
• Import an XML file
• Create an export set from a list
• Create an export definition
• Export set supported file types
• Schedule an export
• Cancel an export set
• Export Set properties
• Import sets key concepts
• Concurrent imports
• Processing custom CSV files
• Importing JSON files
• FTP data source extended properties
• JDBC type data source
• LDAP type data source
• Data Stream (Integration Hub) data source
• Custom (Load by Script) type data source
• Create a File type data source
• Create a JDBC type data source
• Create an LDAP type data source
• Create an OIDC type data source
• Define action properties
• Create a Data Stream (Integration Hub) type data source
• Create a Custom (Load by Script) type data source
• Data source fields
• Transformation script variables
• Map with explicit transform map scripts
• Map with transformation event scripts
• Create a robust import set transformer
• Robust import set transformer properties
• Create robust transform definitions
• Temporary entity model
• Define ETL entities
• Define ETL entity mappings
• Create ETL entity field definitions
• Define Robust Transform Engine operations
• Import run details
• Updating records using coalesce
• Standard import set tables
• Import sets maximum row size
• Create a transform map
• Mapping options
• Create a field map
• Field map script variables
• Run an import
• Importing date/time values
• Review the import set
• Viewing the import log
• Import run history
• Scheduled data import scripting options
• Monitor scheduled data import executions
• Monitor concurrent import sets
• Monitor concurrent import set jobs
• Posting a CSV file - Perl and Java examples
• Delete import sets
• Delete import set tables
• Import sets properties
• Creating an import set web service
• Web service import set mode
• Inserting multiple records using insertMultiple
• Web service import sets security requirements
• Download an import template
• Add a record in the template
• Update a record in the template
• Import a record from the template
• Show reference fields as lists in Excel templates
• Easy import template validation
• Easy import properties
• Troubleshoot import set performance
• XML records from lists
• Create an XML data source to another instance
• Add onBefore scripts to the transform map
• Retrieving data from a CSV formatted file
• Create a clone target
• Exclude a table from cloning
• Data preservation on cloning target instances
• Clone profiles for clone requests
• Cancel a clone
• Schedule cloning
• Modify cloning schedules
• View clone status
• View clone history
• Roll back a clone
• Post-clone cleanup scripts
• Activate database rotation
• Activate table cleanup
• Mark records for deletion
• Preview affected records for deletion
• Schedule or execute a job to delete records
• Rollback a delete job
• Mark records for updating
• Schedule or execute a job to update records
• Rollback an update job
• Domain separation and Data Management
• Set up Google Maps API
• Activate a supported Microsoft SCCM plugin
• SCCM data import process and source tables
• Configure the SCCM integration and schedule an import
• Activate SCCM Asset Intelligence scheduled imports
• Upgrade the SCCM integration version
• Migrate the Verizon eBonding Integration to a Production System
• Request Google custom search integration
• Legacy Import set data for Altiris
• Legacy: Web services import set tables for Altiris
• Computer Telephony Integration
• Integrating ServiceNow with your Intranet
• Direct JDBC Probe
• JDBC Probes via Data Source
• Select * JDBC Probe short cut
• Using the Work Element
• Build a search provider for your instance
• Syslog probe
• Domain separation in third-party application and data source integration
• Deactivate the validation script during user creation
• User self-registration
• User preferences
• Create a user group
• Configure group types for assignment groups
• Hide groups
• Special administrative roles
• Read-only role
• Create a role
• Add a role to an existing role
• Assign a role to a group
• Assign a role to a user
• Define role delegators and delegate roles
• Prevent a role from being delegated
• User administration system properties
• Audit user roles
• Security jump start - ACL rules
• Impersonate a user
• Manage user sessions
• Non-interactive sessions
• Add a new company
• Add a department
• Application Usage Overview dashboard
• ServiceNow Store Usage Overview dashboard
• Implementing Normalization Data Services using guided setup
• Normalized Company Names table
• Normalized Mappings table
• Normalization Properties
• Change a normalized company name
• Define a metric
• Sample field value duration script
• Metric instance
• Response time on forms
• Network response times
• Browser settings and performance
• Slow mutex locks record detail
• Slow events log record detail
• Slow scripts log record detail
• Slow interactions log record detail
• Slow transactions log record detail
• Use a slow query log
• Generate an index suggestion for a slow query
• Review index suggestions for slow queries
• Export an index suggestion to a non-production instance
• Schedule an index suggestion for creation
• Test index performance
• Schedule an index to be dropped
• Create a transaction call chain register
• Review a transaction call chain
• View and kill active transaction
• Canceled-transaction logging to a table
• Import set performance
• Thread performance monitoring
• ServiceNow Performance dashboards
• Asynchronous Message Bus (AMB)
• Instance View
• MySQL Global Status
• ServiceNow Servlet
• Slow Pattern
• Application Insights overview graphs and metrics
• Application Insights detail graphs and metrics
• Monitoring users and transaction performance through Application Insights
• Monitoring semaphore queue efficiency through Application Insights
• Monitoring database performance through Application Insights
• Monitoring event queue efficiency through Application Insights
• Monitoring MID server performance through Application Insights
• Troubleshoot a slow pattern
• Troubleshoot a scheduled job through Application Insights
• Application Insights p1 prediction model
• Configure Application Insights thresholds
• Configure Application Insights threshold triggers
• Components installed with Application Insights
• Application Insights properties
• Apply table rotation
• View a table hierarchy and the extension model
• Add a module to test connection speed
• Add variable information to the cancellation message
• Enable transaction quota debugging
• Configure a transaction quota rule
• Example system log messages
• Modify the transaction cancellation page
• Application-quota property
• Configure an application-quota rule
• Use table extension
• Create an operational toggle
• Create an operational toggle level to define thresholds
• Create run level toggle mapping
• Resolve a skipped update and set a resolution status
• Skipped Changes Reviewed related list
• Revert a customization
• Changes Applied related list
• Claim Outcomes to Review related list
• Upgrade Details related list
• Upgrade Monitor overview
• Factors affecting upgrade duration
• Upgrade Monitor
• Upgrade Progress
• Upgrade Summary Report
• System Upgrades form
• Upgrade Details form
• Resolve Conflicts form
• Enable and use debug upgrade
• Upgrade Preview module
• Upgrade Monitor schedule states
• Building your Upgrade Plan
• Refreshing your Upgrade Plan
• Installing your Upgrade Plan
• Preview Upgrade Plan
• Review skipped records with upgrade plan
• Upgrade History module
• View previewed upgrade
• Preview predicted changes
• View loaded files for a plugin
• System Upgrade form
• Upgrade details form
• Review skipped records using related lists
• Upgrade History Task form
• Update default labels in VTB view
• View import history
• Quick access to plugins and history records
• Explore upgrade history log
• Upgrade Center VTB Labels list
• Release version :  Tokyo Washington DC Vancouver Utah
• Updated Aug 4, 2022
• 1 minute read
• Table Administration

The instance can automatically assign a task to a user or group based on pre-defined conditions by using data lookup rules and assignment rules.