Deletion-Box with item

If you need any help in filling out this wiki page, please visit our ILIAS Community FAQ. And please complete the metadata information in the right column after having created the page.

1 Initial Problem

Currently there are different message boxes in ILIAS, which are integrated in different processes.
These are

• Faiure
• Success
• Info
• Confirmation

During a deletion process, a form of the Confirmation box appears.
In our opinion, this type of message is not sufficient to indicate the importance of the process. Especially since a higher damage can occur if the process is not carried out carefully.

2 Conceptual Summary

A change to the Failure color "Red" would be confusing, therefore we consider an extension of the existing message as reasonable.

We recommend a visual demarcation or clarification of the deletion process with an appropriate icon.

This method has also proven itself in other systems and should symbolically indicate the importance of the next step.

This new message box could be added as a "deletion box" in the existing list below the confirmation message box. 

3 User Interface Modifications

Inclusion of an existing file (attention.png) or creation of a new icon.

Variation 1: attention.png

Variation 2: new icon

3.1 List of Affected Views

• deletion-form / interruptive modal

3.2 User Interface Details

{ For each of these views please list all user interface elements that should be modified, added or removed. Please provide the textual appearance of the UI elements and their interactive behaviour. }

3.3 New User Interface Concepts

{ If the proposal introduces any completely new user interface elements, you might consult UI Kitchen Sink in order to find the necessary information to propose new UI-Concepts. Note that any maintainer might gladly assist you with this. }

3.4 Accessibility Implications

{ If the proposal contains potential accessibility issues that are neither covered by existing UI components nor clarified by guidelines, please list them here. For every potential issue please either propose a solution or write down a short risk assessment about potential fallout if there would be no solution for the issue. }

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 Privacy

{ Please list all personal data that will need to be stored or processed to implement this feature. For each date give a short explanation why it is necessary to use that date. }

6 Security

{ Does the feature include any special security relevant changes, e.g. the introducion of new endpoints or other new possible attack vectors. If yes, please explain these implications and include a commitment to deliver a written security concept as part of the feature development. This concept will need an additional approvement by the JourFixe. }

7 Contact

• Author of the Request: Detemple, Konstanze [kdetemple]
• 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.}

8 Funding

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

• …

9 Discussion

Diskutiert am 08.05.2023 mit S. Kergomard, Y. Seiler und O. Samoila. Fazit war, dass die aktuellen Message Boxes systematischer angegangen werden müssen und ein Icon nicht die Hilfe verschafft, die man sich mit diesem Request verspricht. Die Idee geht perspektivisch in eine "undo"-Richtung. 

10 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}

Privacy

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

Approval

Approved at {date} by {user}.