Identifying stale Standard Change Templates

Jimmy Scott
Tera Contributor

I have a request to report on the Standard Change Templates to identify those that have not been used to submit a Change Request in the past 12 months. I have tried to create a relationship between [std_change_record_producer] and [change_request] to see if it may work as an option (Inspiration from: https://www.servicenow.com/community/now-platform-articles/how-to-create-scripted-relationships-or-d...), but am missing something.

Is there a way to identify those that have NOT been used?

Thank you in advance!

2 REPLIES 2

Uncle Rob
Kilo Patron

No need to create new relationships.  There are two features that can help you here.
1)  Standard Changes are really just fancy Record Producers, and every record produced by a record producer has a record logged in sc_item_produced_record

UncleRob_0-1733233535174.png

2)  List reports allow you to create related list conditions.  So you can literally ask the record producer table to find you items that have no relations (in the item produced records table)

UncleRob_1-1733233797331.png

Make sure on your related list condition you change the amount to NONE (by default its greater >=1)

If you've never seen related record conditions before, here's a video primer.
https://youtu.be/gkzKzSXbwk0

 

 

In under 5 minutes learn how to report in #ServiceNow when the conditions have to do with records *related* to what you're reporting on? For example, how many Incidents have NO Incident_tasks? ▼▼▼ Expand for loads of helpful links ▼▼▼ Get on my mailing list! http://bit.ly/fedoruk Need passionate &

If I am understanding correctly, this would show Standard Templates (sc_cat_item_producer) that have been last submitted as new, modified, or retired more than 12 months ago (sc_item_produced_record).

The relationship I believe I am trying to create would touch on Change Requests as the related list. If my understanding above is correct, I would be looking to have the relationship between either sc_cat_item_producer or std_change_record_producer and change_request.

Is this something doable?