> I think the right approach would be to keep the items selected from > previous pages. A bulk deletion with just one (or two including the > confirmation) click(s) will be much better user experience than doing it > page wise. Also if we are going to clear the selection of one page once > s/he moves into other, we might have to give a warning that their selection > is going to be cleared. However Gayan's concern is a valid one, and a > suggestion came up that whenever performing a bulk action, we should list > down the usernames of the user accounts which are going to be affected in > the action confirmation dialog. IMO that's an acceptable approach. >
+1. I also believe this should be the correct approach for any bulk operation rather than clearing the selections when navigating between pages. > The number of total records for the table and the offset (the staring > point of search) would be given by the admin from UI (the UI part not > implemented yet). The number of records per page can be selected from the > UI (default will be 10) as well and pagination is done according to that. > So initially the requested number of records will be deployed in the table > and it will be a front end pagination (there will be no backend calls with > each page request). IMO there's no point of retrieving data from back end > each time when a page is requested if we cannot do that for the complete > user list in the user store. At the moment, we cannot facilitate to provide > pagination for the total user store user list. The main challenge is that > we do not have an API implemented to get the total user count from LDAP > user store. Without the total count we cannot decide the number of pages. > How will the pagination work if the total record count set in admin portal is less than the total number of users in the identity store ? > >>>> I am planning to add an admin profile in profile-mapping.yaml file >>>> where an admin can define what user attributes to be shown in the list. >>>> >>>> According to the wireframe ([1]), we have to give the flexibility to >>>> show Groups and Roles of the users. ATM we do not have claim definitions >>>> for Groups and Roles. Therefore we won't be able to handle them with an >>>> attribute profile. As per the offline chat with Johann we might define >>>> Claim URIs for Groups and Roles in future since there will be other use >>>> cases where we need to treat them as user attributes (eg. SAML attribute >>>> profile). Also loading all the Roles and Groups for each user in the list >>>> will highly effect the initial loading time. May be we can filter out to >>>> maximum number (say 3) of records and request all if one wants to see more >>>> roles/groups. >>>> >>>> However for the immediate release (m5) I guess it is ok not to have >>>> Roles and Groups in the User List view. We did not have that in IS 5.3.0 as >>>> well so I hope this is not a critical requirement. We will keep the >>>> wireframe as it is since we are planning to improve things in the future. >>>> >>>> [1] https://github.com/wso2-dev-ux/product-is/blob/master/Wi >>>> reframes/admin-portal/v3/3.19%20User%20Listing.png >>>> >>>> thanks >>>> Nuwandi >>>> -- >>>> >>>> Best Regards, >>>> >>>> Nuwandi Wickramasinghe >>>> >>>> Software Engineer >>>> >>>> WSO2 Inc. >>>> >>>> Web : http://wso2.com >>>> >>>> Mobile : 0719214873 >>>> >>>> _______________________________________________ >>>> Architecture mailing list >>>> [email protected] >>>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>>> >>>> >>> >>> Regards, >>> Omindu. >>> >>> -- >>> Omindu Rathnaweera >>> Software Engineer, WSO2 Inc. >>> Mobile: +94 771 197 211 <+94%2077%20119%207211> >>> >>> _______________________________________________ >>> Architecture mailing list >>> [email protected] >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >>> >>> >> >> >> -- >> Gayan Gunawardana >> Software Engineer; WSO2 Inc.; http://wso2.com/ >> Email: [email protected] >> Mobile: +94 (71) 8020933 >> > > > > -- > > Best Regards, > > Nuwandi Wickramasinghe > > Software Engineer > > WSO2 Inc. > > Web : http://wso2.com > > Mobile : 0719214873 > Regards, -- Omindu Rathnaweera Software Engineer, WSO2 Inc. Mobile: +94 771 197 211
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
