How the heck do we hide native features in a post JavaScript QB?

Question

I have some big problems. I need to hide native buttons on mobile, as well as other QB features, and I don't know how to do it without IOL. This is what we all used it for.

My issue is I have an EOTI role that needs to save using my custom buttons, in order to direct them down the application path. However, despite my role management, form management / rules, etc, QB has seen it fit that the native buttons (and their app pimping) MUST show.

I need to hide this ASAP, as this launch is already late. Help!!!

------------------------------
Meredith Moore
------------------------------

EvanMartinez · Answer

Unfortunately the ability to alter the UI in a number of ways using Javascript is part of what is driving the need to close this loophole so we can assure users a more reliable and safe experience using QB. That does mean the trade off is we do reduce the amount of manipulation available today when it comes to buttons and elements either on desktop or on the mobile app. We are making sure to look critically at requests we are getting around the UI and control during this transition so we can understand the gaps that exist and assess where we could work on alternatives that wouldn't open up the same concerns in the future. That does mean right now there is a limit to the ways the mobile app can be changed to customize the UI.

------------------------------
Evan Martinez
Community Marketing Manager
Quickbase
------------------------------

Sign up

Login to the community