- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 11:41 AM
What scripts generate entries in the Script log? I am aware of Business Rules, Workflow, and Script Includes. Are there any others?
Someone put some sort of test statement in our production environment and it is flooding our script log with static messages. Searching for scripts (business rules, script includes) that have this statement does not seem to isolate it.
To be sure, these script logs seem to happen on a display business rule and nowhere else. Searching said business rules for the text in these logs comes up empty.
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2018 01:34 PM
Figured it out. It was an ACL that was triggering this. I found the ACL and deactivated the test code.
Thanks

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 11:46 AM
Please check useful blog below to find out source of your debug script logs.
https://snprotips.com/blog/2016/1/26/make-your-gslog-entries-easier-to-find
Regards.
Sachin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 11:54 AM
Not quite what I'm looking for. We are aware of the exact event that is triggering these messages, but we don't know what code is triggering it. As mentioned before, this only happened when we display a particular record, so we were thinking a display business rule, but none of them seem to have the text string in question. Searching for gs.log in both script includes and business rules seems to draw a blank.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-24-2018 01:13 PM
I think its time for you to use OOB Code Search Application.
If you are in Global Scope and you dont have at least one scoped app, jump to the comments made by joost
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-26-2018 01:34 PM
Figured it out. It was an ACL that was triggering this. I found the ACL and deactivated the test code.
Thanks