Hi Dilan, On Sat, Jun 11, 2016 at 7:09 PM, Dilan Udara Ariyaratne <[email protected]> wrote:
> Hi Megala / Tanya, > > It would be useful if you can also explain the practical use-cases behind > implementing this feature; > so that it validates the real necessity of having such feature available > on the product. > We implemented this feature based on a real use-case which came from a product team. The real use-case for this feature is follow, When a dashboard has certain set of gadgets which uses the data of the currently logged in user and displays some graphs based on that (Ex - Logs/Usages). There may be a situation where we need the same dashboard in all the tenants so that whenever dashboard is used by different tenants, it uses the relevant data from tenant-user. Due to restricting dashboard per tenant, it requires to create same dashboard in all the tenants and it also requires, the tenants to have all the relevant gadgets in relevant gadget stores. But creating a separate dashboard for each tenant and having the same set of gadgets in relevant gadget stores is very heavy for server run-time and it results in lots of duplicates. So in order to avoid that problem we came up with this feature. > IMO, making a dashboard blindly viewable to any user on any other tenant > (who might even not be interested in viewing such dashboard) may not be a > practical use-case. > We are providing a filter option in dashboard-listing page. So that users can select the relevant filters and only view that are specific to him/her. Thanks. Regards, Megala > Please do correct me, if I have misunderstood anything. > > Regards, > Dilan. > > *Dilan U. Ariyaratne* > Senior Software Engineer > WSO2 Inc. <http://wso2.com/> > Mobile: +94766405580 <%2B94766405580> > lean . enterprise . middleware > > > On Fri, Jun 10, 2016 at 9:46 AM, Tanya Madurapperuma <[email protected]> > wrote: > >> Hi Dilini, >> >> On Fri, Jun 10, 2016 at 9:38 AM, Dilini Gunatilake <[email protected]> >> wrote: >> >>> Hi Tanya/Megala, >>> >>> Can't we share the anonymous view with other tenants as a normal view? >>> >> We have only a dashboard sharing option as per now but not view sharing >> option. >> >> >>> In that case if a particular user gets a waning as you said at the time >>> of sharing, the user can create an anonymous view without those restricted >>> gadgets and share the dashboard with other tenants. Then, those tenant >>> users will be able to view the dashboards as explained in the above doc[1]. >>> Just an opinion. >>> >> Also anon view is for any non logged in users and we don't have to >> explicitly share it across tenants. >> >>> >>> Also, I think hiding gadgets won't work because it will introduce >>> unnecessary complications in re-arranging the template. If the restricted >>> gadget is in the middle of the template we can't keep a blank space in the >>> middle rather re-arrange it in a suitable way. >>> >> As I have explained in my previous reply, actual issue here is we are >> not aware of the existing roles in each tenant to hide a gadget based on >> gadget level permissions. >> >> Thanks, >> Tanya >> >>> >>> Regards, >>> Dilini >>> >>> On Thu, Jun 9, 2016 at 10:27 AM, Tanya Madurapperuma <[email protected]> >>> wrote: >>> >>>> To add into what Megala has explained.. >>>> >>>> We decided the above approach due to below reasons. >>>> >>>> 1. In the gadget listing page of the designer mode, we list only >>>> the intersection of the gadget that are authorized for the logged in >>>> user >>>> and restricted viewers of that particular view. So if we warn the >>>> dashboard >>>> creator saying "you have added a restricted gadget, if you share or >>>> planning share this dashboard across tenants, those gadget will be >>>> shown to >>>> the tenant users" at the time of adding a new gadget to the dashboard, >>>> he >>>> will be frustrated if he doesn't want to share this dashboard. So we >>>> skipped that option. >>>> 2. We decided* only to warn* the user at the time of sharing the >>>> dashboard rather than hiding those gadgets in tenants view, because say >>>> a >>>> particular gadget is restricted only for Role1 in super tenant. There >>>> can >>>> be a role with the same name in another tenant which serves a different >>>> purpose. So blindly we can't hide gadgets in tenant mode based on the >>>> role >>>> specified in the gadget. >>>> >>>> Thanks, >>>> Tanya >>>> >>>> On Thu, Jun 9, 2016 at 10:09 AM, Megala Uthayakumar <[email protected]> >>>> wrote: >>>> >>>>> Hi All, >>>>> >>>>> We have created a new feature for DS which allows the dashboard >>>>> created from super-tenant to be shared among all the tenants. For more >>>>> information, please refer to documentation at [1]. With the new release we >>>>> are going to introduce fine-grained permission for gadgets. So that, >>>>> gadgets' access can be restricted using roles. In that case, when we share >>>>> the dashboards across tenants the gadgets with role restriction will not >>>>> be >>>>> shown as roles are limited to each tenant. >>>>> >>>>> But if we think this from the point-of view of the user, who is >>>>> willing to share the dashboard, he/she will expect tenants to have the >>>>> same >>>>> level functionality in the view mode.In order to solve this problem, >>>>> we have come up with following option. >>>>> >>>>> When a super-tenant user tries to share the dashboard, we will give a >>>>> warning saying, this set of gadgets in this dashboard are restricted to >>>>> these roles. If he/she share the dashboard, then it will be shown to all >>>>> other tenant users regardless of role of the user. Then it is user`s >>>>> decision on whether to share/not to share the dashboard. WDYT ? >>>>> >>>>> Any comments on this is highly appreciated. >>>>> >>>>> [1] >>>>> https://docs.google.com/a/wso2.com/document/d/1JjB0Ehf6LzJ13krLwN3vo3fLVU4AHQevBtfzN8XqZ70/edit?usp=sharing >>>>> >>>>> Thanks. >>>>> >>>>> Regards, >>>>> Megala >>>>> -- >>>>> Megala Uthayakumar >>>>> >>>>> Software Engineer >>>>> Mobile : 0779967122 >>>>> >>>> >>>> >>>> >>>> -- >>>> Tanya Madurapperuma >>>> >>>> Senior Software Engineer, >>>> WSO2 Inc. : wso2.com >>>> Mobile : +94718184439 >>>> Blog : http://tanyamadurapperuma.blogspot.com >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> >>> -- >>> >>> *Dilini GunatilakeSoftware Engineer - QA Team* >>> Mobile : +94 (0) 771 162518 >>> [email protected] >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Tanya Madurapperuma >> >> Senior Software Engineer, >> WSO2 Inc. : wso2.com >> Mobile : +94718184439 >> Blog : http://tanyamadurapperuma.blogspot.com >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > -- Megala Uthayakumar Software Engineer Mobile : 0779967122
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
