Move Confirmation Screen for Block and Unblock Role to Modal

1 Initial Problem

Blocking and unblocking a role in tab Permission currently triggers a confirmation screen on a new page. This is outdated behaviour and ignores Kitchen Sink rules: „All actions where data is deleted from the system are considered to be critical situations and SHOULD be implemented as an Interruptive modal.“

2 Conceptual Summary

Instead of reloading the entire page for the confirmation workflow, a KS Interruptive Modal with KS Key-Value Interruptive Items are used. Start and endpoint of action is tab 'Permission Settings'. Content of existing screen is re-used.

3 User Interface Modifications

3.1 List of Affected Views

• {Repository Object} » Permissions » Permission Settings

3.2 User Interface Details

Interruptive Modal consists of:

• Title: rbac#:#role_block_role# | new lang var rbac#:#role_block_role# with content ‘Unblock Role‘
• Info Message: rbac#:#role_confirm_block_role_info# | rbac#:#role_confirm_unblock_role_info#
• Confirmation Message: rbac#:#role_confirm_block_role_header#
• Key-value Interruptive Items for all affected roles: {Role Title}: rbac#:#role_blocked# | rbac#:#role_unblocked#
• Primary button: rbac#:#role_confirm_block_role#

3.3 New User Interface Concepts

No new concepts.

3.4 Accessibility Implications

None known.

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

None

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: Kunkel, Matthias [mkunkel]
• Maintainer:
• 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.

• ILIAS-Verein

9 Discussion

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