GlideSystem (gs) functions like gs.info(), gs.log(), gs.debug() in a business rule script not working when called by a filterIssue Note: For the latest information on this topic, see Script sandbox property. GlideSystem (gs) functions like gs.info(), gs.log(), gs.debug() present in a script do not work when its called by a filter/dynamic filter.CauseThis is because of the script sandboxing feature of High Security Settings plugin. Any script executed from a filter is sandboxed for security purposes.Only a small subset of GlideSystem (gs) methods are available in this context. The GlideSystem sandbox does not have access to the following methods: - gs.info- gs.debug- gs.addInfoMessage- gs.addErrorMessageThe following three methods do exist in the GlideSystem sandbox but are disabled/blocked by default. - gs.logError- gs.logWarning- gs.logResolutionTo enable/unblock the below methods in the GlideSystem sandbox, the value of system property "glide.security.sandbox_no_logging" can be updated to "false". - gs.logError- gs.logWarning- gs.log