Learn 10 Secrets to Become a Top-Tier ServiceNow Admin

Wouldn’t it be crazy if everyone who was new to the ServiceNow ecosystem all rushed to obtain their CSA? …let’s be honest…how competitive in the job market are you? We need to raise the bar…let’s go beyond the CSA certification, beyond lists, forms, client scripts, and flow designer.
At a higher level, a ServiceNow Admin is the first line of defense for platform health, security, license management, user management, releases, governance, and more! So, how can you learn about those topics to become a top-tier ServiceNow Admin? Do you have to wait until you come across those “lessons” on the job? Or is there a way to get prepared beforehand?
I invite you to watch this video as the ServiceNow world today is much different than it was yesterday and it’s only fair for you to be aware of the additional skills needed to stay competitive and succeed.
Follow me on LinkedIn - / allenandreas
Twitter/X - x.com/allenova...
Other resources:
ServiceNow - www.servicenow.com
Now Learning - nowlearning.se...
Admin Center/Clone Admin Console - • Platform Academy Sessi...
Subscription Management - • Subscription Managemen...
Patching FAQ - support.servic...
Master Cloning - • Master ServiceNow Clon...
What else should you know as a new CSA - • What You Should Know a...

[@igorkochetkov3399]

Great tips. I discovered Subscription Management just 1 month before this video. There is a list of paid roles which are marked as a Fulfiller , in our CSM v5 we have around 212. But it’s not clear does “admin” paid ? As it’s not listed but as we all know it contains a bunch of roles. 2. I have a Fulfiller (paid) role listed, my users don’t have it directly but I surprisely found that it included into snc_internal role lol. So each my Fulfiller now counts as paid?(it’s included ootb )

[@Allenovation]

Hi! I’ll first say that you definitely speak to your or your clients SN Account Executive for the most accurate and up to date answers. However, to give you some guidance, Admins do usually consume a fulfiller license because of their access on the platform. They don’t count 10 times for just the 1 admin, it’s 1 charge for each admin. For your other question, if fulfiller roles are nested within your snc_internal role, which means basically everyone gets that role out of box, then you may be under a license model that it per user, versus per role…or….someone on added this fulfiller role to the snc_internal role when they shouldn’t have. Again, you’ll want to check with your SN Account Executive for the best answer. I hope this helps! 😊

[@nouamandehmani]

Hi there , Thanks for your videos they are very informative :) can you please let us know how can we showcase our Portfolio for Service-now Admin ? say I create tables , users rules etc using SN Dev instance and want to share that in my resume like a link or something like GitHub but for service-now.

[@Allenovation]

Hi, thank you for the kind words! To showcase a development/design portfolio you could consider creating a custom portal/app with the "Public" role configured so that they don't have to login. Alternatively, you could record yourself giving a demonstration/walkthrough and then link to that. I think allowing people to SEE it versus see an app repo (such as in Git) will go a long way. Give that a shot?

[@nouamandehmani]

@@Allenovation Hi , Thank you so Much for your suggestion , since I am new to service now admin/dev I will dig to see how I can create a custom portal/app with the "Public" role configured as you suggested Keep the valuable info coming , Thanks again

[@Allenovation]

@@nouamandehmani You're very welcome! Thank you for your support!

[@dominikabak6786]

Thank you for the great KZbin episode with tips and insights! Could you please provide some material on AI in ServiceNow? Looking forward to it.

[@Allenovation]

You're very welcome! Thank you for the comment and definitely, I'll add that topic for a future video! Thanks for the suggestion!

[@dominikabak6786]

@@Allenovation ❤❤❤❤❤❤❤❤❤❤ Did You know Document Intelligence or Task Intelligence???

[@preeet007]

That was great! Can you also make videos on all the mentioned topics and explain best practises. That will be awesome. Anyways thanks for informative video.

[@Allenovation]

Thank you! I'll definitely consider this for future videos. I do have several videos already that are focused on leading practices for areas of the platform such as client scripts, business rules, and so on. Check those out if you get time!

[@7kena7]

Thank you for sharing these secrets. I think Allenlightenment would be another fitting channel name 😄

[@Allenovation]

You’re awesome! That may be something in the future, haha!! Thank you!

[@bobbybob1932]

Once again, thanks a lot Allen! I always learn something new through your content. I can say your tips definitely helped me get promoted twice in a year and a half :) Keep it up!

[@Allenovation]

Wow! That’s great news! Thanks for your support and feedback!

[@NyxrPalmer]

Thanks Allen!

[@Allenovation]

You're welcome! 😊

[@EdServiceNowAdmin]

Great, Video. so many of those new applications are helpful and easy to learn and use

[@Allenovation]

Very true! 😀

[@mskoddow]

Great video as always!

[@Allenovation]

Maik!!!!! Thank you! Can't wait to watch your livestream soon about importing!

[@JosiphiaLekeane]

Great video 😊

[@Allenovation]

Thank you for watching and leaving a comment!!

[@OneAndOnlyMe]

With a good release testing process and good governance of the dev environment, there is no need to clone prod to dev. Prod to QA, yes, but no need to clone to dev.

[@Allenovation]

Hi. Cloning Prod to Dev isn’t just for syncing development. It’s also to sync data, such as groups and other records, as applicable. These may have been created manually or by another process such as LDAP. Instead of exporting and importing, cloning would be much more efficient. In any case, I appreciate your input and thank you for commenting!

[@OneAndOnlyMe]

@@Allenovation Dev should not have production records, instead there should be production like data in dev for unit testing, etc. Any dependencies on SYS_IDs should be migrated to using constants in a script class. Even for LDAP I would only sync a sub scope of the developers and for SSO, for example.

[@Allenovation]

No Prod data at all in Dev may be what you’re used to, which is completely understandable as each organization has their own governance and processes. For the group sys_id, yes, when scripting you wouldn’t hardcode it, when using no-code/low-code, which would be preferred if the option is available for the use case, the record would need to be there. And instead of exporting and importing, cloning Prod (and this is for far more data than just groups), would be the most efficient. I believe I saw UK in your name somewhere? For our friends overseas and across Europe, yes, you all have different regulations that may cause the normal cloning process to skip Dev. For Americas, at least, it’s common to clone Prod to Dev and use excludes and preservers as needed. Although some do skip Dev here as well, so it all depends on the environment. Take care!

[@Tony_20000]

Thank you Allen!

[@Allenovation]

You’re very welcome! Thanks for watching and taking the time to leave a comment as well!

[@IAmWandaful]

Thank you !!!!!!

[@Allenovation]

Thank YOU for watching and leaving a comment!!