As my efforts to provide full “coverage” of the UI I reasonably expect my users to use in ServiceNow, I’ve aimed my attention at the template form. Templates can be dangerous in ServiceNow, if you let them run amok. I discussed in a previous post how users can potentially enter bad data combinations, or if they have access to the schedule button can schedule records to be generated on an undesired basis, and created some checks and balances so users could create templates, but not go crazy with them. Today I’ll examine how to use automation to create templates with the UI, and validate my error messages happen when users enter bad data.
If you’ve ever poked around the tables list in ServiceNow, or browsed the ServiceNow wiki for “reminder”, you’ve probably run into the “reminder” table. This table seems fairly straight-forward at first glance, but a deeper dig brings up several questions. What is this Reminder Field Name field type? Why can’t I add fields to it, or remove fields from it? Why is the business rule to handle the reminders inactive by default? What is this “addListener” function? Why is there no documentation on any of this, and in it’s stead an article to create a custom field?
Some of my favorite automated tests are the simplest ones: checking forms, quickly creating records, and checking the left nav pane, for example. The notion of checking that the list views are accurate was not high on my priority list until recently, when I had a small user story to make sure certain fields were visible in the default view. A manual test for that is simple and quick for sure, but could I automate it and let it be worthwhile automation?