Mark Stanger
Giga Sage
Options
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
09-20-2013
07:06 AM
6+ years ago when I was an admin first being introduced to ServiceNow, I remember being blown away by how simple it was to personalize forms, add fields, and design custom form views. Custom views are very easy to make, but I'm always hesitant to recommend them due to the unintended complexity they can cause. The biggest issue with the 'view' concept in ServiceNow is that the system insists on forcing that form view onto every record referenced from within it. This issue exists in every ServiceNow instance today. In this article, I'll explain why this can be a huge problem, and finally, a good way to break the ServiceNow form view inheritance cycle!
Click here to learn more at ServiceNowGuru!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
