Getting Notified of Completed Study Programme

1 Initial Problem

Users must participate in study programmes.
However, in various scenarios they are not "live" at the point of time when their duties are resolved:

• Their assignment is accredited.
• In linked courses they achieve the learning progress status "Completed" when the manual assessment of a test or exercise takes place.

So in these two cases, users are not told that they are "off the hook" unless they log in and check the study programme.

• Assignments are already completed from the beginning because courses that users have already been completed were acknowledged when they were created.
  In this case, users are startled by an e-mail regarding an assignment and only find out in the system that there is nothing more to do.
  (Unfortunately, we are not able to determine whether the study programme has been completed at the time of the e-mail's dispatch, e.g. in order to integrate information into the same e-mail via mustache sections that only such users have in their e-mail).

2 Conceptual Summary

Users are notified by e-mail that the requirements for them in a study programme have been fulfilled.
This is conducted by an additional cron-job.
The mail dispatch can be boolean-configured in the SP's settings.

In the event of completion upon assignment (third abovementioned scenario), they will at least receive a second email indicating that the requirement no longer exists.

3 User Interface Modifications

3.1 List of Affected Views

• Administration > Cron-Jobs
• Study Programme > Settings

3.2 User Interface Details

• Cron-Jobs: "Edit" action opening a form to choose an interval
• SP's settings: Checkbox "" without sub-options in section "Configuration Automatic Mails"

3.3 New User Interface Concepts

(none)

3.4 Accessibility Implications

(none)

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

(none)

7 Contact

• Author of the Request: Suittenpointner, Florian [suittenpointner]
• Maintainer: Klees, Richard [rklees]
• Implementation of the feature is done by: Klees, Richard [rklees]

8 Funding

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

• CaT Concepts and Training GmbH

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