It’s been a while since I’ve posted anything, but I wanted to say I’m working on several interesting pieces of functionality right now. I hope to write full posts on some of these topics in the near future.
- Change Tasks generated based on either a time element on a form or the closure of multiple other change tasks.
- Dynamic system documentation so users reporting on ServiceNow have a go-to place to learn about what information is present and what it means. It will also pull in data about what’s on the forms, so users can see in that report what field we actually use. The only “manual” part of this documentation is giving a description to each field and table. It updates on every dictionary and table update.
- A two-way Rally Integration (although we’re going to just use the data extraction piece and move out of Rally into ServiceNow SDLC).
- Skipping approvals for the same user (both with skipping the generation of their approval record in the future only, and skipping the entire phase of approval they are associated with in the future).
- Mentioned before, but an integration with Jenkins that creates a change request in ServiceNow, then once the change is approved, builds the Jenkins job at the planned start time.
- A script the dynamically generates the import set table and data table for BDNA Technopedia Integrations.
- A field on a catalog item that copies the data from a similar request item so users can submit multiple requests that are similar (but one or two changes) faster. Example: Onboarding 10 different interns – the only difference in each form is the name. Normally this could take several minutes to fill out the forms.
- I’ve been using the Left Nav more often in ServiceNow browser testing automation. So I have code to generate the left nav as a page object. It’s been helpful to write quick tests to just ensure that the links have the correct filters.
- Changing how surveys are generated so they are included in the email with every resolved incident. Also, deleting surveys which aren’t taken after 7 days.
- Cleaning up the cmdb_rel_ci table to automatically delete records that aren’t needed (ie, when a CI is deleted, or possibly even retired/decommissioned).