Forcing JSS to re-scan database for /usr/sbin usage?


Hey - so I noticed JSS 9.81 kindly scans your database and informs you of any scripts, policies, etc. that reference the old JAMF binary location - however it seems like any subsequent scripts or policies you create there are not subsequently scanned (?) True or false? If it doesn't can anyone think of a way to kick off such a database scan again? I was hoping to use my test JSS to scan all of my scripts (which I have manually copied from my production server to test) for any red flags that the JSS is able to pick up.

I've tried: re-dploying the webapp, restarting tomcat, restarting MySQL, Running a database integrity check...