- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2014 08:01 PM
What are those top skills every ServiceNow cloud developer should have... ?
- JavaScript
- Glide Record
Solved! Go to Solution.
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2014 04:20 AM
I think following skills every ServiceNow cloud developer should have.
- Client Side and Server Side Scripting (Ex. Catalog Client Script, Business Rules, Script Actions, Script Includes etc )
- Client & Server API's (Ex: GlideDialogWindow,GlideForm (g_form), GlideAggregate, GlideRecord etc)
- Administration (includes Reporting, Email Notifications, Creating/Editing Home pages,Personalizing Forms etc )
- HTML/CSS/AJAX knowledge
- UI Pages & Jelly (More than 200 pages user Jelly)
- ACL and its debugging
- Knowledge of ITIL framework and good understanding of (Asset/Configuration/Incident/Problem Management, Product Catalog etc)
- Transformation MAP, Scheduler, Connection with other database/instance, WebService
- MID Server setup and Update set migration
- CMS, you can do lot in this space
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2014 06:33 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2014 07:17 AM
There's a lot of great feedback on this thread. In addition to these technical skills I think it's probably just as important to have some basic consulting skills (whether you consider yourself a consultant or ServiceNow admin).
-The ability to translate business requirements into tool requirements that make sense to all and follow best practices.
-Knowing ServiceNow development best practices and being willing to push back a bit when a particular path may be detrimental long term to your customer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2014 07:32 AM
I liked the best practices part and I strongly believe it is a must have ....
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2014 10:49 AM
yes, this is very important. You can do anything on ServiceNow but that doesn't mean you should. Things need to make sense and the developer should aim to create solutions not just purely coding.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-04-2014 11:30 AM
Brad Tilton (Cloud Sherpas) wrote:
-Knowing ServiceNow development best practices and being willing to push back a bit when a particular path may be detrimental long term to your customer.
If I could like this 10 times, I would.
I know that we had some expectations that our consultants early on in our initial implementation would let us know when our requirements were not in line with ServiceNow best practices and were disappointed when we learned that was not the case. We had to undo a lot of work he did later on as we learned the limitations of our choices.
I really value more than anything the ability for a consultant to let me know the best way to accomplish something, rather than just taking my requirements at face value and implementing them to the letter without much discussion. As I've grown as a ServiceNow admin, I'm much better at sensing that and asking the right questions of consultants, but I would rather a consultant come in with that attitude in mind without me having to force it.
