What is the proposed idea/solution?
Providing Interface designers with the ability to allow/disallow the visibility of the field "i" tooltip inside Interfaces.
How does is solve the user problems?
Currently, we are using text blocks in the UI to explain certain field purposes or possible pitfalls of user selections. You can really clean up an interface and reduce user support questions by providing them with the ability to get further information before making a choice at the exact moment in their workflow that it is appropriate. Blocks of text mean to help a user perform functions really make the entire interface too cluttered to use for experienced users. Some users don't use the system very often so they usually completely forget and need this help but. Maintaining two interfaces with different levels of "Info Help" is not a viable option.
From an administration standpoint, this allows for already existing documentation to now serve both database designers and end users at the same time. Future leaning thinking also implies that there could be two fields for "Description" - each with a different set of permissions so that admins can leave themselves complex backend notes for themselves and their teams yet provide more simple descriptions for interface front end users.
How was this validated?
N/A
Who is the target audience?
Anyone designing interfaces for themselves or others
