servicenow disable assignment group

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

ServiceNow Community servicenow community

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

• ServiceNow Community
• Service Management
• Service Management forum

ACL - Restrict Groups by User Roles (Script)

• Subscribe to RSS Feed
• Mark Question as New
• Mark Question as Read
• Float this Question for Current User
• Printer Friendly Page

• Mark as New
• Report Inappropriate Content

‎03-05-2018 08:07 AM

• All forum topics
• Previous Question
• Next Question

‎03-05-2018 08:19 AM

‎03-05-2018 10:29 AM

‎03-05-2018 07:46 PM

• Update and Delete Entries from MRVS in Service Management forum 3 weeks ago
• Add user to multiple groups after individual manager approval in a workflow in Service Management forum 12-13-2023
• Reference Qualifier with Script Include in List Collector Variable - not returning value in Service Management forum 12-07-2023
• Using group sys id in client script. Want to Convert group sys id into System Properties in Service Management forum 07-22-2023
• How can I restrict a field to accept alphanumeric values - first 2 characters use alphabets? in Service Management forum 02-23-2023

SNow Underground

ServiceNow Development Tips!

ServiceNow Group Best Practices

Groups in ServiceNow are a container (many lovingly call a bucket) for users that have similar purposes or functions. It’s really easy to go astray with groups, and there isn’t much guidance on how to best use them and govern them (besides some honorable mentions ).

Table Structure

Just a quick refresher, a Group is a record/row in the sys_user_group table. This table has a couple notable columns, including:

Manager - Should be MANDATORY, every group should have an active manager that is responsible for keeping the group up to date, in terms of purpose, members, description, etc. They should be responsible for quarterly reviewing the group. Note: Many organizations also add a custom field for manager delegates to specify additional users, or they use the OOB delegates feature in ServiceNow.

Group Email - Should be OPTIONAL and sparingly used, depending on it’s purpose some groups should never should receive any email. Also some areas abuse this field and put a dummy email address and are none the wiser.

Parent - Should NEVER BE USED, most modern day implementations, it is best to not leverage parent groups, especially for the purposes of granting roles, reporting hierarchy (use department/business unit/cost center), or “rollup”. Just hide the field and wipe your hands clean.

Description - Should be MANDATORY, every group should have a clear concise description saying what the group is for, and in a certain repeatable format. Typically it should be several sentences to fully describe the audience, usage and related process area.

Source - Should be OPTIONAL, if you use LDAP integration, this field is populated automatically. Otherwise you may choose to populate it with something, but most people choose to leave it as is otherwise. Blank for manually managed groups, and filled in for LDAP/other source.

Group Type - Should be MANDATORY, every group should have one or more group types that help categorize what process areas/purposes the group is used for. This is arguably one of the most critical fields, so you can properly filter down to relevant groups on different forms.

Notable Mentions: Hourly Rate (may be important to populate for chargeback/routing decision trees), Default Assignee (usually not used in the wild… but maybe in small organizations), Exclude Manager/Include Members (usually left as default), Points field (if you are using gamification on communities)

Best Practice Guidelines

1) Separate Process and Security Groups. As a general rule of thumb you should separate the way you grant a role, and the group you use for Catalog Tasks or Incidents. In small organizations this can make sense temporarily, but as you scale, the management of roles almost always is handled by a separate group and has separate criteria for acceptance (training, department, etc.).

2) Define and govern Group Types. As mentioned above it is critical to define a list of group types and have central control over any changes to the list. The related reference fields that point to group should all have a reference qualifier based on the type, so only the proper groups are selected. Also most of the OOB group types aren’t very good… Here is an example of groups types:

security - used for groups that grant roles

catalog - used for catalog request fulfillment

incident - used for groups that can be assigned and work incidents

problem - used for groups that can be assigned and work problems

change - used for groups that can be assigned and work change requests

vulnerability - used for groups that can be assigned and work vulnerable items

knowledge - used for groups that can be assigned and responsible for knowledge articles

approval - used for groups that are used for the primary purpose of group approvals (like a Platform governance group!)

3) Avoid Duplicate Groups. Minimize any potential for creating multiple groups that grant the same roles, and have the same purpose. Every time a new group is created, the current list should be consulted to make sure nothing else fits the need.

4) Groups should not mimic Department structures. Probably one of the easiest traps people fall under is thinking that groups somehow align to departments. Work doesn’t happen in silos, work is collaborative - therefore groups should be collaborative and cross functional. ServiceNow already has a department table structure for that purpose.

5) Don’t Hardcode groups. Besides the cloning aspect, in general it’s still not a good practice to hard code groups into things like UI actions, ACLs, and yes even flows. For security, you should be coding in Roles, and for routing, you should leverage assignment rules or a reference field on a table. The one rare exception where it may make sense to put in groups is within a User Criteria record, but even then, you still have the option to use roles.

6) Use Management Catalog Item. For handling all group related actions, new groups, adding members, updating fields, retiring, should all be handled through a catalog item with the proper approvals built in. There should be built in steps on the create group to check existing groups, and vet the business case. Then on the retirement request, it is important to check related data elements, like where groups “could” have been hardcoded, and make sure data elements like knowledge articles and incidents are moved under a new group.

7. Have a Group Management Dashboard. This is the cherry on top that brings the process full circle. Set up different reports and metrics to see how your groups are being used and if all the correct fields are being populated. Example: Set up a report for catalog groups, and make a list of how many haven’t been used in 6 months. Another example, set up a report for any groups without an active manager. Have an admin check this dashboard once a week/month and take any corrective actions.

Interested in what other best practices people have for managing ServiceNow groups, feel free to comment below!

ServiceNow Advanced Reference Qualifier | How to filter the Assignment group based on Assigned To

Been in a predicament in ServiceNow, where you know the person a task needs to be assigned to, but don’t know the right group? I got you!

In this video, we add an advanced reference qualifier on a dictionary override on the assignment group fields (for incidents) that calls a server side script include to run some funky glideRecord queries and return as back a refined list of group sys_id’s. Its then these groups that are shown when you click the Assignment Group magnifying glass.

https://docs.servicenow.com/en-US/bundle/tokyo-platform-administration/page/script/server-scripting/concept/c_ReferenceQualifiers.html

https://www.servicenow.com/community/developer-forum/dynamic-advanced-reference-qualifier-examples/m-p/1386576

Reference Qualifier bit:

javascript:new global.AssignmentGroupFilter().refineAssignmentGroup(current.assigned_to)

Script Include:

Tags: advanced reference qualifier beth anglin GlideRecord reference field reference qualifier script include servicenerd servicenow admin servicenow demo servicenow tutorial sysid in

You may also like...

How to create a Variable Set

ServiceNow San Diego Flow Diagramming | Flow Designer stuff #Shorts

ServiceNow: How to embed hyperlinks in work notes | clickable links

• Next story Flow Designer Error Handling ServiceNow | How to…
• Previous story ServiceNow GlideAggregate Count | Is it better than GlideRecord getRowCount()

All Videos / New Features / Tips & Tricks

AI in ServiceNow with Justin Meadows | What does it mean?

February 27, 2023

New Features / Tips & Tricks

What is ChatGPT and Can We Use it for ServiceNow

December 18, 2022

• Recent Posts
• Popular Posts
• Recent Comments

ServiceNow Process Automation Designer (PAD) | What does it do?

December 19, 2023

All Videos / Flow Designer

“Do the Following Until” Flow Logic in ServiceNow Flow Designer

September 1, 2023

Exploring Dynamic Flow and Get Flow Output Logic in ServiceNow Flow Designer!

July 24, 2023

All Videos / Flow Designer / Tips & Tricks

Flow Designer Error Handling ServiceNow | How to…

July 3, 2023

June 11, 2023

Service Catalog / Tips & Tricks

October 30, 2022

Integrations

ServiceNow Inbound REST API | Import Set API

September 12, 2022

New Features / Shorts

ServiceNow San Diego Polaris | ServiceNow Next Experience UI #SanDiego #Polaris #Shorts

February 7, 2022

Flow Designer

ServiceNow Flow Template Builder | Create a template using Flow Template Builder

October 6, 2022

• artificial intelligence business rule client script flow Flow designer Flow designer development flow designer for service catalog flow designer servicenow flow designer servicenow orlando flow designer servicenow training flow design tutorial g form glideajax GlideRecord integration hub onload script include service catalog service catalog in servicenow service catalogue servicenerd servicenow servicenow admin servicenow administrator training servicenow community servicenow demo servicenow developer servicenow developer training servicenow flow servicenow flow designer servicenow flow designer approval servicenow flow logic servicenow glideajax example ServiceNow how to servicenow integration servicenow microsoft teams servicenow new features ServiceNow Next Experience ServiceNow Polaris servicenow reference field ServiceNow San Diego servicenow shorts servicenow training servicenow tutorial subflow

Learning ServiceNow by Tim Woodruff

Get full access to Learning ServiceNow 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.

Assigned to and Assignment group

The Assigned to [assigned_to] field is a reference  field type that points to the Users [sys_user] table. This field is generally used to designate a user to work on, or be responsible for the task. By default, this field has a reference qualifier (role=itil) set on its dictionary record that prevents any non-itil user from being assigned to a task. You can override this reference qualifier on tables that extend task though, as the Project Task and Service Order tables do, if you have the relevant plugins installed.

The Assignment group [assignment_group] field serves pretty much the same purpose. The reason for having both, is that a workflow might automatically assign a certain type of task ticket to a group, ...

Get Learning ServiceNow 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.

• Victor Mukhin

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.   

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

Quick links.

• Conference Brochure
• Tentative Program

First refuelling for Russia’s Akademik Lomonosov floating NPP

!{Model.Description}

The FNPP includes two KLT-40S reactor units. In such reactors, nuclear fuel is not replaced in the same way as in standard NPPs – partial replacement of fuel once every 12-18 months. Instead, once every few years the entire reactor core is replaced with and a full load of fresh fuel.

The KLT-40S reactor cores have a number of advantages compared with standard NPPs. For the first time, a cassette core was used, which made it possible to increase the fuel cycle to 3-3.5 years before refuelling, and also reduce by one and a half times the fuel component in the cost of the electricity produced. The operating experience of the FNPP provided the basis for the design of the new series of nuclear icebreaker reactors (series 22220). Currently, three such icebreakers have been launched.

The Akademik Lomonosov was connected to the power grid in December 2019, and put into commercial operation in May 2020.

Electricity generation from the FNPP at the end of 2023 amounted to 194 GWh. The population of Pevek is just over 4,000 people. However, the plant can potentially provide electricity to a city with a population of up to 100,000. The FNPP solved two problems. Firstly, it replaced the retiring capacities of the Bilibino Nuclear Power Plant, which has been operating since 1974, as well as the Chaunskaya Thermal Power Plant, which is more than 70 years old. It also supplies power to the main mining enterprises located in western Chukotka. In September, a 490 km 110 kilovolt power transmission line was put into operation connecting Pevek and Bilibino.

Image courtesy of TVEL

• Terms and conditions
• Privacy Policy
• Newsletter sign up
• Digital Edition
• Editorial Standards