ServiceNow Project Training Guide

[toneyvecchio1]

Hello Project Subspace! Just wrapping up my second Project Go-Live, had to put together two training labs for PMs who had never touched the tool prior. Thought this might be useful for other starting off in the PM space. I tried to teach the wide range of mechanics in as a controlled way as I could.

Note that as you'd expect there are customizations involved and we have molded it around requirements for process that is specific to one company so keep that in mind. The only real customization I can think off the top of my head that are at odds with Out-of-box is that our Actual start/end inherit the planned dates. Less dynamic but also less dates jumping all over the place like OOB can do.

Enjoy!

[michellelim]

These are great! Thanks so much for sharing.

A couple of questions...

1. Do you recommend using Project Workbench over Planning Console?
2. Templates - do you know how to limit (preferably by group) who has ability to update templates?. For example, IT Facilities group to be able to update the templates they created (own) but not other templates created/owned by Network Engineering.

One last thing... what does 'recall' mean on the title of your documents?

Thanks!

[toneyvecchio1]

Glad to help Michelle!

1. We are not on Geneva yet so do not have the Planning console however we are very much looking forward to it. I have found that Work Bench is mostly valuable to showing the project at a high level. Unfortunately you don't get good access to the bottom level tasks that PMs really work from.

2. Depending on how many groups and how scaleable you need, at first glance I would approach that through ACLs - Add a drop down on the Project Template table for options such as Network Engineers and IT Facilities. Then give a unique role to each of those groups members. Finally, add an ACL to Project Template so that they can only create/read/write if they have the right role and right drop down.

3. Recall is the name of the company I deployed for.

[mariemathew]

Would anyone know how long knowledge articles (published or otherwise) stay on an instance?

[Steven Young]

Knowledge articles on our instance are scheduled for 1 year from published date.

however, you can edit those KB's and extend them.

I think we are running a rule preventing them from being extended past 1 year from published date.   you can turn that off and put whatever expire date you want.