- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-12-2017 06:08 AM
Good Morning!
We host an instance of Service Now and all of our UI Actions for every table have gone MIA. This includes UI Actions on lists and forms, out-of-the-box and custom, links, buttons, hamburger/context menu selection, etc. We can only make changes to records by hitting the back button and pressing the save button in the prompt. This issue exists within our Development and Test instances but not in Production. Aside from local updates, one difference between Production and the rest is that Production is on Istanbul Patch 5, and the Development and Test instances are on Patch 6. Some steps we've done to solve this:
1. Making some of the UI Macros uncoditionally true
2. Checking HTML source to see if UI Macros are just hidden
3. Checking the system logs, we are getting a likely relevant warning:
java.lang.NullPointerException
Caused by error in Phase 2 Jelly:plugin://com.glide.list_v2/ui.jtemplates/list2.xml.2 at line 1
com.glide.script.GlideRecord.addQuery(GlideRecord.java:2368)
com.glide.ui.action.ActionManager.loadActionRoles(ActionManager.java.295)
com.glide.ui.action.ActionManager.createActions(ActionManager.java:258)
........
Any thoughts?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2017 04:43 AM
Well this turned out to be an issue with the way that we were upgrading. Upgrades require that some values be updated within the application itself prior to running the update executable.
Lessons Learned
1. Follow the instructions
2. Follow the instructions
3. Follow the instructions
Thanks to everyone that looked into the issue. A big thanks to strohm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-07-2017 04:43 AM
Well this turned out to be an issue with the way that we were upgrading. Upgrades require that some values be updated within the application itself prior to running the update executable.
Lessons Learned
1. Follow the instructions
2. Follow the instructions
3. Follow the instructions
Thanks to everyone that looked into the issue. A big thanks to strohm
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-23-2018 08:46 AM
We are having the exact same issue, which part of the instructions mention the actual values that need to be updated within the application itself before upgrading?