- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Hello,
After upgrading the Now Assist for IT Service Management(ITSM) to the latest version (13.0.10 when this post was written) we started to get this error message on every RITM and Catalog task forms
Function print is not allowed in scope sn_uxc_gen_ai. Use gs.debug() or gs.info() instead
I've cheked all business rules, script includes related to this table and haven't found anything... please help
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Issue has been fixed, we upgraded to 13.0.11 and message is gone. So basically it was just outdated plugin.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago
Excellent @GM5 thansk for sharing the resolution!
Answers generated by GlideFather. Check for accuracy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago - last edited 3 weeks ago
Hi @GM5
Either use Use gs.debug(), gs.info(), gs.warn(), and gs.error(), as these are available in both scoped applications and global scope.
OR
As per KB article : KB0788208 Why doesn't gs.log work?
Can you try with
Solution: Use ms.log() instead. The log entries will be found in the Agent Log of the MID Server.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
Sorry the issue is not about we coding, no code has been involved here everything started to happen After a plug in was installed as mentioned on initial post, our instance is very vanilla very low customization and coding. Thanks for your suggestion but this is not our case.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 weeks ago - last edited 2 weeks ago
Hi @GM5 ,
Great to know that issue has been fixed.
My bad - it seems Other post's answer mistakenly ,I added here. Kind of a wrong window.🙄
