Modifying your own requests is a feature that exists on ServiceNow platform, however it is missing for the Service Portal. We will help you to enable this feature on the Service Portal by using what is availabe on Agent Workspace.
First, you should review your processes to see if it makes sense to allow users to modify their own requests and if it does, you should decide until which workflow state you should allow that. You don’t want users to be able to modify their requests once the work has progressed to a certain point.
You would need to create field to allow configuration of catalog items, something like a field called “Can edit requests in SP? (u_can_edit)”.
Now we can re-use Agent Workspace functionality and modify the sp-variable-editor widget to make it suitable for Service Portal.
We added a save and back button, as well when a request is modified, comments section reflects what was changed.
We also do additional handling for most common variable types (they are separated by different numbers and not the name of variable types), however for other variables some modification might need to be done.
Modify line 12 of server side code to define at which workflow states you can edit your request.
You would also need to create a link from your request conversation page to the edit request page.
System logs do not provide all the useful information about your instance. Slow ACL’s, slow business rules and other issues might be important for your instance health and performance monitoring, however they are only found in the node logs. If you never browsed node logs, you will be surprised how many issues it can reveal. However, getting to all node logs is problematic.
If you’ll go to the “Node Log File Download” module and open any log file, you will only see “Download” button. If you press it, you will get a log file from a single node only – that node is the one you are logged onto.
Ok, that’s just one node. I just have to log in another node and download the logs one by one?
Kind of. This was possible prior to Madrid release, where you were able to switch to another node by modifying certain cookies. However, as of Madrid, it is not possible.
We tried raising a case with HI support, and we were told: “It is not possible for SNOW customers to switch nodes and download individual node log files. If you need your node logs you will have to raise a request and HI support will do it for you”.
This is not ideal solution for us, as dealing with HI support is usually slow and inconvenient.
Downloading node logs is easy for on premises customer, they can directly log in to their application servers and download logs directly. But there is a faster way for them as well.
Luckily, some ServiceNow developer actually build a feature which is kind of hidden, not documented and not known, but it allows us to solve this specific issue.
Go to “Node Log File Download” module and stay in the list view.
Locate any node log and right-click it.
Select “Download Logs from Near Nodes”.
You are given an option to select multiple nodes and log date range.
Now, if you go to “Node Log Download History” module, all your previously downloaded logs will be saved as attachments for your future reference.
Also note, there are API’s that allows us to create scheduled scripts to scrape the node logs to search for useful information. This might allow us to supplement and automate our instance monitoring which is not covered by the system logs.
It used to be problematic to give limited access to developers from other teams. There wasn’t an easy way to limit access to change specific scripts or specific workflows, because everything used to be in a global scope or under a custom scoped application. Users would get access to everything or none, unless you wanted to spend a lot of time building heavy custom ACL’s.
This issue was solved by ServiceNow with Delegated Development. Now it is a good practice build everything under scoped applications, for example new features come out as their own applications (Agent workspace, GRC, Change management, Spoke applications).
Note, generally, based on new license subscription model,
there are no license implications and you can build as many scoped applications
as you want.
1) Go to sys_store_app.list where you can see all available applications.
2) Under related links click on “Manage developers”.
3) Choose a user and select limited access to only what they need from this application by application file type: script, workflow, service portal, update set access etc.
4) Now user will have access to application and update set pickers after they enable it from their developer settings. Also, whenever he will open any application file type, the filter with his allowed applications will be automatically set. Other files will be hidden under ACL restrictions.
Note: to enable configuration of update set rights you have to set up com.snc.dd.manage_update_set_enabled system property to true first. Users will have access to update set module and they will be able to choose update sets from there. To enable update set picker access set up glide.ui.update_set_picker.role property with the application role name.
Also, there is a simple way to change the scope programmatically:
One of the biggest complaints ServiceNow receives is that it
is running on old technology. It is true that most of ServiceNow is running on Java,
Jelly, AngularJS, which comes with poor performance, but ServiceNow is working to
New ServiceNow features introduced in Madrid and enhanced in New York comes with more modern technology stack.
To access other specific components, there are at least 50 new OOTB undocumented REST API’s to perform ServiceNow functionality which was only possible by old school HTTP requests only (history, favorites, breadcrumbs, filters, date, impersonation, UI action, etc.). This means almost all the required functionality is accessible in the front end.
However, not everything is upgraded to new stack yet, there are still some iFrames that call Jelly pages and some REST API’s are missing. Those too can be called using REST API’s, but it’s complicated.
More API’s and more components are coming to ServiceNow. A lot of performance optimizations happen when you move away from Java and Jelly.
But the natural problem arises: if we have so many different REST API’s to call to fill our page with everything we need, it becomes too complicated to continue developing and grow. We need some way to perform BATCH REST API operations.
Here is where GraphQL comes to ServiceNow.
As REST replaced SOAP, it is believed by some, that GraphQL
will replace REST due to handy benefits:
You only call one endpoint to get all the date instead of calling many – you do not need to call 20 different REST API’s to get all information into one page
You only get the data you ask for and not what REST API developer wanted you to get – you only get what you ask for, so you can limit the transaction size to be as little as possible – hence performance increase
It iIt is also possible to use GraphQL for your ServiceNow integrations and ditch REST API’s.
You only need to call one endpoint with POST for everything you need.
2. All the parameters are in request body.
How do I call ServiceNow using GraphQL?
For example, if you wanted to get encodedRecord, sys Id and record values for specific incident:
We can also retrieve any other elements from the page (related lists, UI actions, formatters, etc.) or perform GlideRecord equivalent operations, like isValidRecord, lastErrorMessage, canReadRecord.
To get all incidents, it looks more complicated, but way less complicated than the old way. Remember this is all done from client side and you have access to anything you ask for.
Also, as this is fully undocumented yet, I haven’t spent much time around to find the ideal queries. This probably could be optimized a lot.
What are other tools in ServiceNow to support GraphQL?
1 ) You can debug GraphQL execution by opening “Debug GraphQL” module. Session debugger was greatly enhanced with New York release, but is possible in Madrid as well the same way you debug service portal. More can be found here.
You can do some ‘mouse clicking’ in ServiceNow UI while session debugger is running and copy your GraphQL queries.
2) GraphQL subscription feature might enable you to build modern pub/sub message queues for client-side application solutions. Same as for AMB and AngularJS record watchers you could define subscriptions (ServiceNow calls them ‘Channel Responders’). With GraphQL you can do the same by utilizing sys_rw_amb_graphql_action table, which extends sys_rw_amb_action.
3) All transactions using GraphQL have “Batch REST” type and
cannot be tracked separately. Logging can only be enabled at node level
enabling advanced REST debugging.
A useful roll back and delete recovery feature was released to ServiceNow. With each script execution you can track all the database changes with possibility to recover everything with Rollback Executor.
It sounds very useful and seems like it will fix all your oopsies. However, it has flaws, does not always recover everything and might take days or weeks to finish.
One resultant flaw is that RollbackExecutor is being counted an as ‘upgrade’ activity. While it’s running you will not be able to use preview and commit update set functionality – “Update set preview and commit are unavailable because the system is currently upgrading. Click here for the Upgrade Monitor”.
As well as scheduled jobs with upgrade_safe=false parameter will not be executed while rollback is running.
Usual way to stop any transaction is by following:
Go to “Progress workers”, locate the running worker
and change its state to cancelled.
Go to “Active Transactions (All Nodes)” or “Active
Transactions”, locate the transaction you want to kill, right click it and
This is what you must do, however, both steps are not enough to kill RollbackExecutor process. You can verify it’s still running by going to xmlstats.do and looking for background_progress_workers:
Luckily, we can figure out next steps based on the node logs:
The upgrade system is busy because the GlideSystem is Paused
GlideSession message was modified by sanitization. [message=Update set preview and commit are unavailable because the system is currently upgrading. <a href="$upgrade_client.do">Click here</a> for the Upgrade Monitor][sanitized=Update set preview and commit are unavailable because the system is currently upgrading. <a href="$upgrade_client.do" rel="nofollow">Click here</a> for the Upgrade Monitor]
Now we simply use undocumented GlideSystem API functions.
First, we can verify if GS is paused with gs.isPaused();
Then we simply resume GlideSystem with:
Finally, our rollback activity is cancelled and we can use our update sets and scheduled jobs!
Note: this is only applicable to Madrid or older ServiceNow versions. Since New York upgrade session debugging is done in a separate user friendly window.
NOW platform and Service Portal shares a lot of common utilities that are used in many places thorough the platform. For example, ACL’s, user criteria, text search are used in both parts of ServiceNow. We know we can use system diagnostics debugger tool on the platform, but what about the portal?
When we enable the debugger in the platform, at the bottom of our page,we can see what is happening under the hood of SNOW. For example, how are the database records we are trying to reach are processed, how ACL and user criteria rules were evaluated, what was the text search score for each returned item generated.
However, when we enable the debugger, this same information is not available at the bottom of our portal page.
So how do we debug platform-shared features in Service Portal?
You have to have 2 windows open. One must have Service portal opened and another one must have the platform.
On platform under ‘Session debug’ select ‘Enable all’.
Reload the current page you are on the portal or load any other portal page.
Go back to the platform and in the filter navigator type any non existing table/UI page name and add .do in the end, for example, isthisreal.do, or if you just want to get done with it faster something like ‘asdf.do’.
That’s it. Because this ‘ isthisreal’ page does not exist, it loads debugger information of the last page that was loaded successfully, which is in our case, the Service Portal.