DR 5.2 - Pushing Modals

1 Requirements

Several views and screens in ILIAS could be improved in usability and also simplified when they are migrated to Bootstrap modals, see http://getbootstrap.com/javascript/#modals. Main advantage of using moduls would be that users do not leave the context where they called the modal but can easily return after they executed the related workflow.

A simple example for a modul use case could be the ‘Legal Notice’ link at the footer of ILIAS. The ‘Legal Notice’ is displayed information with a simple process of usage: A user clicks on the link, ILIAS displays the information defined as legal notice and the user can read it. There is no follow-up attached to it. At the time being, a new tab is opened (which is quite unusual for content that is within ILIAS). Migrating the ‘Legal Notice’ to a modal would allow to close the displayed page and to see again the content from where the ‘Legal Notice’ has been called.

A more sophisticated workflow to support is the course and group mail workflow. Start and ending point is the ‘Members’ view in the course or group management. In this use case the modal has to support a multi-step process: selecting the recipients, writing the mail, adding file attachments, sending the mail. But at the end, the user should be back again in the course or in the group where shehe started the workflow.

Having such a closed circle process - no matter if just one page or a multi-step workflow - would be the main requirement when deciding if a modal is appropriate or not.

Collection of Supportable Use Cases

• Legal Notice (presentation view when called from footer)
• Personal Profile (presentation view when called from somewhere in ILIAS)
• Course mail / group mail (called from ‘Members’ tab of course / group)

2 Additional Information

• Idea / concept: Kunkel, Matthias [mkunkel]
• Interest in funding: (please indicate if you are interested/able to fund this feature)
• Maintainer: depends from component where modal should be used
• Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
• Testcases by: Kunkel, Matthias [mkunkel]

3 Discussion

4 Implementation

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