Skip to main content

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings

Idea pipeline (top 25)

  • Completed

375 Ideas

Freddy
FreddyThinkwise Local Partner Brasil

Model actionbar elementsCompleted

Especially with the introduction of the actionbar component, where you can freely position the actionbar it has become more a necessity to model the action groups of the actionbar. I see the taskbar has the following main groups: Filter Pre-filter Tasks Reports CRUD actions (incl. import/export) Refresh It's not uncommon that you have a grid, form and for example a preview/cube/ or other element not being a reference.. If you put them all on a separate tab all the component gets all the action bar items. Functionally and personally this is unwanted. the filter, pre-filter and mass update for example do not make sense on a form level (exceptions are there of course) because you are looking at a single entity. In the U-GUI we use the previewer to load external apps.. Basically you don't want to have search, filter, CRUD actions there (again exceptions are possible) It would be really great if the option to hide action bar could be extended by modelling at screentype level which action-bar items you would like to see. Example: If you put a form on a separate tab, the search /filters are most likely unwanted because it will most like likely changes your context if you (accidentally) fill something in the searchbar or activate a pre-filter. If you have, like we external components that base themselves like a form on a single entity you have the same situation.. you probably only want to see tasks/reports and a refresh button here.. Especially when you are not familiar with the concept of Thinkwise it's odd to see have search / CRUD actions here. @tiago @Yara