Feature Wiki

Information about planned and released features

Tabs

Revision and Enhancement of the ‘Personal Default Settings‘

Page Overview

[Hide]

This is the Proposal to reverse the existing Decision of Test: Abandon Personal Default settings and keep the Feature in an extended and therefore usable way.

1 Initial Problem

Due to the lack of clarity about the need for the feature, we actually wanted to discontinue it. Based on feedback from the community, we are now taking the initiative to upgrade and improve the ‘Personal Test Settings’ feature.

It is quite an old feature that still uses many old UI elements. The changeover to new UI elements is unavoidable as part of the reorganisation.

The feature does not show which settings are stored in its save points.
In addition to the lack of clarity as to what is actually stored in the template, it is not possible to recognise which possible default values have been added with a new ILIAS version. The ILIAS version in which the template was created is also not recognisable.

Additionally from a technical point of view: the information is stored in a serialized format in the database which leads to difficult to solve issues on every change of the settings.

2 Conceptual Summary

  • Rename Subtab 'Personal Test Settings Templates' instead 'Personal Default Settings'.
  • Toolbar:
    • Instead of a 'Microform' in the Toolbar an explicit Button "Add New Setting Template" is used. A Modal to set a Title is shown.
      • Modal Header: Add New Setting Template
      • Modal Body:
        • Message Box with short Explanation the actual Test Settings are used to define the Settings Template.
        • Form:
          • "Title" (Text Input)
          • "Author" (Text Input – prefilled with First Name and Last Name like Question Author)
      • Modal Footer: Buttons: "Save new Setting Template" and "Cancel"
    • An new Button "Import Settings Template" is placed in Toolbar. A Modal to Upload a Import File is shown.
      • Modal Header: Import Setting Template
      • Modal Body:
        • Message Box with short Explanation that the Import of Templates is only possible within the same Major Release.
        • Form:
          • Import File (KS File Upload)
      • Modal Footer: Buttons: "Import Setting Template" and "Cancel"
  • Table Header is changed to 'Test Setting Templates' instead 'Available test defaults'.
  • Table is revised into new UI Data Table
  • Table-Content:
    • Column 1: Selection Column
    • Column 2: Template Title (Set by Creator, not changable) (sortable Column)
    • Column 3: Creation in ILIAS Version (Set to "ILIAS x.y"; Major- and Minor-Version) (sortable Column)
    • Column 4: Creation Date (sortable Column – default sortation)
    • Column 5: Created by (sortable Column)
    • Column 6: Action-Menu
      • Action 1: Show Template Details
      • Action 2: Apply Settings Template (We should show a confirmation modal here to communicate appling cannot be undone by a click.)
      • Action 3: Export Settings Template
      • Action 4: Delete
    • Table gets only a Bulk Action "Delete".
    • Table gets no Filters and no Option to show and hide Columns
  • Informations of "Template Details"
    • Adaption of Content of "Additional Information" of "History"-Tab of Tests
    • Using a Modal within a "Descriptive Listing" of Kitchen Sink to show all Settings a Settings Template is using or affect if applied.
    • If a setting is added as part of a major (or minor) release, it has a default value. This default value is also displayed in the settings template and is supplemented by the information ‘Default value of a newer ILIAS version (ILIAS x.y)’.

Ergänzung des Requests: Ein wichtiger Effekt ist: Im Create-Prozess können diese Einstellungen nicht mehr ausgwählt werden. Trennung von Didaktischen Vorlagen und Einstellungen.  & Limitierung Export / Import gleiches ILIAS Release!

3 User Interface Modifications

3.1 List of Affected Views

  • Subtab 'Test Settings Templates' (fka. 'Personal Default Settings')

3.2 User Interface Details

Details above in Chapter 2.

We want to use UI Framework Components where possible. E.g. UI Data Table and Modal with Descrptive Listing. There is still no alternative for the button in the toolbar.

Ergänzung des Requests: ggf. Mockup Ansicht Modal Inhalt?

3.3 New User Interface Concepts

None.

3.4 Accessibility Implications

Improvements by using UI KitchenSink.

4 Additional Information

4.1 Involved Authorities

If this request is related to multiple components, please list both authorities for all related components.

4.2 Technical Aspects

{ Necessary technical information have to be provided here, e.g. dependencies on other ILIAS components, necessary modifications in general services/architecture, potential security or performance issues. }

@Thomas: Please add the information discussed here.

4.3 Privacy

Personal data get stored, if we decide to make the Templates exportable and importable to show the creator. There is shown {First Name} and {Last Name} by default.

4.4 Security

No specific changes.

4.5 Contact

Person to be contacted in case of questions about the feature or for funding offers: Samoila, Oliver [oliver.samoila]

4.6 Funding

Funding status and funding parties are listed in the block 'Status of Feature' in the right column of this page.

If you are interested to give funding for this feature, please get into contact with the person mentioned above as 'Contact'.

5 Discussion

6 Implementation

Feature has been implemented by {Please add related profile link of this person}

6.1 Description and Screenshots

{ Description of the final implementation and screenshots if possible. }

6.2 Test Cases

Test cases completed at {date} by {user}

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

6.3 Privacy

Information in privacy.md of component: updated at {date} by {user} | no change required

6.4 Approval

Approved at {date} by {user}.

Last edited: 3. Apr 2025, 15:07, Strassner, Denis [dstrassner]