That’s my prediction. Service Portal will no longer get updates by the Orlando release. It will be like Workflow, Execution plans, Homepages, and the Content Management System. It will still work but will not get future development. I know it’s only been out since Helsinki and that means since April 2016 which is ~4 years. But after you look at these findings, you’ll agree. Why bring it up? Well, I don’t like to work on something that isn’t going to get support.

Robert Fedoruk has been killing it with his content, and one of theses posts needs to be retold because it is, just that good. Source: Youtube Tired of only the pros knowing how work fast in #ServiceNow. In <5 minutes, learn to pinpoint stuff most relevant to you, and bookmark it for later. — Robert Fedoruk (@rfedoruk) October 1, 2019 I feel like this should be searchable and isn’t today.

So I’ve built many automation tasks that didn’t account for what to do during an error or an expected output. Do you know who has to work on that stuff? Likely, it’s you. That’s a fine way to go if that’s the intention. I never intended for that to happen. I was working with a stakeholder on some automation and he wanted to keep a task in place. It didn’t matter to me at the time.

First, I have to say, thank you @paige for making me aware. I really appreciate you and this info. Form annotations can be really helpful and powerful. You can use them help users enter the right information and users can turn them off when they feel comforatable. The other day on slack I think Paige mentioned they just flat out do not work on service portal. This is a real shame.

Syntax Editor Macros are rarely talked about. Effectively, they are a text replacement table for script elements. That might not seem that big of a deal, but for me. It could have saved me some serious headaches. Let’s look at the examples provided on the docs site. vargr will replace itself to; var gr = new GlideRecord(""); gr.addQuery("name", "value"); gr.query(); if ( { } As much as I dislike the use of variable name gr as using just that name can cause issues, its nice!

I posted a survey on Twitter a few weeks ago; Prosective #servicenow employers, what do you find more telling of a quality applicant? #servicenowdev. If it's something else, reply to this. — Jace Benson 👨‍💻⚙️ (@jacebenson) July 1, 2019 Why does this matter? Average developers using ServiceNow think they need a certificate to validate that they really do in fact know something about ServiceNow. I think having a certificate is great for ServiceNow, and for your employer if you’re a consultant because it adds to their partner level stuff.

I posted a survey on Twitter a few weeks ago; What's better? Fully Automated with many questions, or nearly automated process with very simple inputs? #ServiceNowDev #ServiceNow #Survey One means, make it and forget, the other means a better user experience. — Jace Benson 👨‍💻⚙️ (@jacebenson) September 19, 2019 Once I came to this realization that User Experience(UX) is literally more imporant then getting all the details from an end user, it literally took me three days to sort it interally.

I took this from, Hi’s styleguide as I don’t trust anyone to keep anything online. So this is just a local copy with opinions about word choices. Note: Consider consulting with a technical writer before you commit UI text. Tech writers can help with clarity and consistency of UI text. Avoid Using “Please” Using “please” is unnecessary, unless you are asking the user to do something that is inconvenient or a result of a system error.

It seems this page was lost in the rearrangeing of files. I pulled it out of storage I often use the recordless rest calls to test things. I didn’t see it on my blog, so here’s an example so I can find it in the future. var instance = "dev40379"; var requestBody = { short_description: "test incident" }; var restMessage = new sn_ws.RESTMessageV2(); restMessage.setBasicAuth("slack", "slack"); restMessage.setHttpMethod("post"); restMessage.setEndpoint("http://"+ instance +""); restMessage.setRequestBody(JSON.stringify(requestBody)); var response = restMessage.

So this is really a small update. I’m slowly but surely working my way through things. One of them was to improve access to some of the tools I use. I’ve used often to help discuss the flow of a process or complex logic in the past. I like that I don’t have to decide the layout of the lines and I think it looks fine. If you’re unfamiliar with PWA’s they can be installed on Desktops, Tablets, and phones.