Bulk Case creation scheduled job was completely disabled in Rome and has been replaced by Create bulk HR cases script action which is triggered by sn_hr_core.process_bulk_case_request event. The script runs asynchronously and you don’t have to worry about setting up the right time for the job
Employee Relation COE (sn_hr_core_case_relations) is no longer available, instead new customers are going to use sn_hr_er_case table which is sets in Human Resources Scoped App: Employee Relations [com.sn_hr_employee_relations] not in Human Resources: Core App. New Employee Relation provides a data model that supports tighter security and saves tons of work that usually spends on customization ACL or data segregations
like many ServiceNow pros, Semaphore comes to mind when there is a performance issue, however, Semaphore is much bigger than that. here I am trying to learn more about Semaphore.
What is Semaphore? according to ServiceNow docs and JVM docs, Semaphore manages and protects ServiceNow resources and limits the number of activities for a specific resource. Semaphore does that by controlling transaction queues in a first-in-first-out fashion(FIFO).
We all come across situation where we have to look at a code that it’s written by someone else and try to figure out what is that variable does or what is this function suppose to do.
This is where good naming is important. it saves us time and significantly reduce error. I know naming variables and functions can be tricky. In this post, I share two characteristics that can be a foundation or starting point for good naming
Every now and then I find myself debating with a friend or colleague on whether we should use ACL or Business rules query.
Personally, I think the use of business rule query should be minimised. if you think about it, ACL called ACL for a reason! your security admin is the only one who can change ACL where anyone in your organisation with personalize_rules role can play with a query business rule that can be integral to your team.
again, I am not saying never use query business rules , I am just saying it should be minimised.
Here is when you shouldn’t use query business rules
Your query BR is going to run on large table.
Your query BR might contain a lot of OR clauses or LIKE operator.
You are not concern about your instance performance.
In Quebec release, ServiceNow introduce new capability to enable users to insert multiple records into a staging table and trigger a transformation that is based on predefined transform maps in a single API request. In this post i am going to use the Insert Multiple REST API end point.
First thing, I am going to structure my JSON, I use company.do?JSONv2 to help me structure my JSON
This is my first trip to Quebec and I am excited to start of with ITSM.
Service Desk Call
First thing you notice in Quebec( If you enter from ITSM gate) that Service Desk Call (com.snc.service_desk_call) plugin is deprecated . Service Desk and New Calls are replaced completely by Interaction and Work space.
Today, I recognize that a custom interactive filter can be mighty. Here is why.
I wanted to create a dashboard containing 2 reports. The first report should show incidents grouped by Category, and the second should show incidents grouped by CI. So far, all is well & easy, and no need for a custom interactive filter.
I also wanted to enable my end-users to filter on a short description; in other words, I would like them to be able to interactively use the Short Description CONTAINS filter on my dashboard.
Using import set for populating CMDB is always a challenging activity. setting up the right coalesce field to your transform map makes this activity particularly challenging, correctly identify CI primary attribute is a key to reduce the risk of introducing inconsistencies through duplicate records.