Never use current.update in a Business Rule

The more I read about Business rules I notice that they are being used the wrong way by many people. Every rule has it's exceptions and I bet there is one here as well. But I can say that I haven't yet come up to a reason why you should use current.update in a Business Rule. I written a post about this and Business rules in general.

Having knowledge public with Version 3

As some of you may have noticed, upgrading to knowledge version 3 made a big impact by making it impossible to have the a knowledge base "real" public. What I mean with real public is that user can use the knowledge base without having to log in first. This was possible in version 2, but right now in version 3, the user need to be logged in, even if the user doesn't have any roles.

This was a critical problem for us since we had a deadline to migrate our current knowledge base into Servicenow. Here is the solution.

Import Word doc is finally here!

Finally we are able to import word documents with pictures into knowledge articles with an build in functionality.

This has been an issue for me and spend many hours trying to get the scripts found in the community to work for us in Fuji and it doesn't work flawless...

But now the hero has arisen. In Geneva,  ServiceNow has heard the voices of the community and added the function to import a word document to a knowledge article with a few clicks.

Extend the time on your personal developer instance

We all know that our free personal dev instances have a limit of 10 days of inactivity, then it's returned to the pool and it's a pain to try and get a new one. Solution for many has been that once a week go in and do something, like create a client script. This just so your counter for inactivity should be reset. Well, now they have made a new function which help with this.

Part 3 - Giving the service status a nicer look.

On the last part I build the page without giving to much into how the whole thing looked. Now I had some time to look into this and also taken some help from colleagues with more eye for design than I will ever have. I also thrown in some HTML-fields and client script to automate the function of Valid to. This is how I did it.

Making your own "new Feature" window

Been having some trouble reaching out to the users with our own "new releases" and the information about our own fixes and new functionality. Looking at the community I realized that I wasn't alone with this problem. Today people are getting flooded with information through email so we threw that idea out the window. We also tried to publish the releases with knowledge articles, but the success hasn't been overwhelming.

So now I was thinking that perhaps we should do like ServiceNow and throw up a popup windows when user logs in. And this is how I did it.

PART 1 - The magical tables that ain't so easy to know about in the beginning

When I started to wander into the land of ServiceNow I had a hard time trying to do the easiest thing.

For example:
I had a Service Manager coming to me and asking a simple demand like: I want a list over all my groups that I mange and its members. It sounded like a easy thing but all I knew was that I could go the the "groups" list and then I hit the wall trying to figure out how to filter/config layout to give me the result I wanted.

And after searching quite some time since I didn't believe I was the only one with this problem I found the solution. There are a few tables that combines other tables by default. You just need to know them.