I'm noticing trying to do gs.<anything> is not working when using them in script includes for use in filter functionality. This is making it so I can't call system properties or do logging or other useful things that GlideSystem allows.
Steps to reproduce:
1.) Create a new script included called testingStuff. Make it Client Callable, in the Global Appication, and accessible from All application scopes.
function testingStuff(){
gs.log('Am I being ran?');
return 'INC0000001';
}
Replace INC0000001 with a real incident from your system to use for testing.
2.) Now create a fix script called "test normal call", have it only Run Once, and just have this as the script:
gs.print(testingStuff());
Run it, and see that it logs fine.
3.) Now go to any incident view, click on the filters and have it be like the following:
That's javascript:testingStuff() in the textbox there.
Run it and see that it runs the part of the code fine that returns the incident number, because now your test incident will show up as your filtered record. However, check the System Logs -> Script Log Statements and see this time that it didn't record any logs. You can also add other GlideSystem functions to your function to see that none of the others will run either, such as gs.getProperty
What is going on here? How can we go about getting GlideSystem functionality to work for filtering?
Best regards,
Brian
