- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-23-2019 11:58 AM
How to remove the save button on a few tables like(idea, cost plan,dmn_requirements,incident, problem,change etc)? in my instance, 2 save buttons are visible on form example one save button from an idea table and other save button from "global " table. how to remove that, I checked this is coming from the "insert and stay" button from UI actions. if I do inactive this then its working fine in idea from, but I checked in other instances it is active but save button is only one. but I remember that I haven't created any new global button.
save button left to submit is from dmn_requirement table
save button right to submit is from global table
Solved! Go to Solution.
- Labels:
-
Project Portfolio Management
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-24-2019 02:38 AM
Hi. We have the same problem on one of our customers' instances.
I managed to narrow it down to being caused by the "glide.ui.advanced" system property. If it's set to "true", some buttons duplicate The buttons in the ITBM module are apparently not implemented in an "advance ui"-compatible way. If you check the UI actions from some of the other modules, they check "isAdvancedUI()". The ITBM buttons do not.
One workaround could be to manually add checks for "isAdvancedUI()" to the UI Action conditions.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-24-2019 02:38 AM
Hi. We have the same problem on one of our customers' instances.
I managed to narrow it down to being caused by the "glide.ui.advanced" system property. If it's set to "true", some buttons duplicate The buttons in the ITBM module are apparently not implemented in an "advance ui"-compatible way. If you check the UI actions from some of the other modules, they check "isAdvancedUI()". The ITBM buttons do not.
One workaround could be to manually add checks for "isAdvancedUI()" to the UI Action conditions.