Define Target Timespan for a Scheduled Cronjob

1 Initial Problem

Currently some cronjobs offer the possibility to configure a schedule when they run. Other cronjobs just define their schedule. This allows to say, how often a cronjob should run, but lacks the possibility to define when the cronjob should run.

This is required for some cronjobs implemented by plugins, e.g. when the cronjobs send weakly mails, but should send them on sundays. Setting a targeted period where the cronjob should run would allow to distribute workload to nights or weakends for performance hungry cronjobs.

2 Conceptual Summary

Cronjob with the schedule "daily", "weakly", "monthly", "each quarter" or "yearly" should get an additional configuration that allows to define a target period where the cronjob should run.

3 User Interface Modifications

3.1 List of Affected Views

{Please list all views (screens) of ILIAS that should be modified, newly introduced or removed.}

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

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 Contact

• Author of the Request: {Please add your name.}
• 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.}

6 Funding

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

• …

7 Discussion

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

Approval

Approved at {date} by {user}.