This best practice article offers practical guidelines for debugging in Fuji. Jam-packed with useful information, it includes two videos that detail the new debugging features in the ServiceNow Fuji release, as well as the best ways to optimize instance performance. The new methods in Fuji provide you with consistent control over how your application manages debugging output in terms of verbosity — or what's logged — and the destination where it's logged.
The new custom applications recognize two properties. The first property, the verbosity, allows you to specify the verbosity of the output. The second property, the destination, allows you to specify the output destination.
Follow these debugging best practices to help you get started:
- Create both destination and verbosity properties for your custom app in System Properties.
- Create a Properties page for your custom app's debugging properties.
- Set your application's default verbosity to error and the default destination to db.
- Use the new Sequence field in the log list to sort entries accurately.
- Use all methods appropriately.
Check out ServiceNow KB: Best Practices - Debugging in Fuji (KB0550844) for details on each best practice, as well as additional tips for debugging in Fuji to improve performance. Watch the videos for specific examples, or use the article as a quick reference for debugging successfully in Fuji. For a video demo of our best practices for debugging in Fuji see Best Practices for Debugging in Fuji Part 1 and Best Practices for Debugging in Fuji Part 2.
For more info about debugging, see:
2 Comments
