Feature Wiki

Information about planned and released features

Tabs

Enhance Sorting and Filtering in Permission Tables

1 Initial Problem

By now (v5.3.x), the tables in "Permissions" tabs of objects hardly be adjusted to the beholders needs. This is a problem particularly when there are a lot of roles of the same type (global or local ones):

  • The table then becomes very wide and cannot be overlooked conveniently.
  • The sort order of roles (from left to right) is only controlled by the roles' obj_ids (that is, put differently, the creation date) which do not offer a meaningful order to the beholder in many cases.

2 Conceptual Summary

There are two aspects in which this problem can be tackled:

  • Like in "Administration > Roles", the "Permissions" tab of objects offers a filter field "Title".
  • The sort order of roles (from left to right) can be selected by the user, according to the following criteria:
    • Alphabetical
    • Creation date (like now)

Anyway, the familiar splitting into global roles (at the left beginning of the table) and local roles (to the right) has to be preserved.

3 User Interface Modifications

3.1 List of Affected Views

*/perm_settings/permission_settings

3.2 User Interface Details

  • The existing select menu "Role" is renamed to "Role Type". A new "Title" filter field is displayed next to it.
  • A "Column Sorting" menu is displayed on top of the table, allowing to choose from the options "Creation Date" and "Alphabetical".

3.3 New User Interface Concepts

A completely new user interface aspect related to this feature request is sorting tables horizontally.

4 Technical Information

{The maintainer has to provide necessary technical information, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues.}

5 Contact

  • Author of the Request: 
  • Maintainer: {Please add your name before applying for an initial workshop or a Jour Fixe meeting.}
  • Implementation of the feature is done by: {The maintainer must add the name of the implementing developer.}

6 Funding

If you are interest in funding this feature, please add your name and institution to this list.

7 Discussion

8 Implementation

{The maintainer has to give a description of the final implementation and add screenshots if possible.}

Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.

Last edited: 3. Jul 2018, 14:43, Suittenpointner, Florian [suittenpointner]