Hi Udara, As discussed offline we need to have following as well.
- A name for each view so that if a user could see both views he/she should be able switch. - A default view should not be existing, and that should be associated with roles selection option when the 'role based view' option is selected in the left pane. - As Dakshika mentioned, the view tab settings will be required to edit/update as well. - During the personalization of dashboard mode, we shouldn't show the options of editing the roles, etc for a view table, and only show the view names in the tabs. Hence the user can't actually do any changes to the view or anything, but he/she can add or delete gadgets, change layout, etc according to their personal interest. Thanks, Sinthuja. On Tue, May 31, 2016 at 2:33 PM, Udara Rathnayake <uda...@wso2.com> wrote: > Hi, > > Came up with following modifications to the existing dashboard designer UI > to cater the $Subject. > > Designer can select and enable page view based on role(s) from the > settings. > > > > Once this is enabled, we can update the dashboard designer with a drop > down where dashboard designer can select a role and create the particular > view. When the dashboard designer browse gadgets/widgets section from this > particular view(role based), we should only list down gadgets enabled for > the selected role(have to come up with a gadget level config for this). > > > > > This role list can be a simple drop down (if we support one role per page) > or can be a list with check-boxes, so we can support multiple roles per > page view. (gadget listing for particular view should be the union of > selected roles) > > > > Designer UI after adding a role based page view, > > > > > Appreciate your feedback on this. > > > -- > Regards, > UdaraR > -- *Sinthuja Rajendran* Associate Technical Lead WSO2, Inc.:http://wso2.com Blog: http://sinthu-rajan.blogspot.com/ Mobile: +94774273955
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
