Trying to debug Service Portal issues? We have some helpful tips to share! Our Sr. Developer Evangelist Chuck Tomasi, Sr. Tech Support Engineer Yandy Orellana, and Technical Writer Josh Ortiz lend their expertise to help get you up and running again. Be sure to check out our video at the end of this post to see demos of these debugging procedures:
- Client script debugging options
- Server script debugging options
- Context menu tricks
- Hiding a widget instance on a page
- Using widget diagnostics (new in Orlando)
Use the browser developer console
Use the built in developer tools in your browser to view console messages and errors thrown by client-side scripts. Here's how to access developer tools in the Chrome browser.
Use the widget context menu to output data and show widget customizations
CTRL + right-click on a widget to open the context menu, which allows you to output the scope and scope data object to the console.
The Show Widget Customizations option displays the level of customization of all widgets on the page, allowing you to prioritize your troubleshooting and perform other widget diagnostics.
Check for security restrictions caused by access rules
If you can see records in the platform UI but not in the portal widget, ACLs may be to blame. Use the ACL debugging tools to rule this out.
Hide widgets to narrow your troubleshooting focus
If you set the Active field to false on the widget records, the associated scripts won't execute so you can focus on the widgets you need to troubleshoot.
For more information
See our video below for demos of these debugging procedures:
- Client script debugging options
- Server script debugging options
- Context menu tricks
- Hiding a widget instance on a page
- Using widget diagnostics (new in Orlando)
Widget Troubleshooting guide (product documentation)
Recommendations for developing widgets (product documentation)
Service Portal (Customer Success Center)
Service Portal (ServiceNow Developers)
