Recurrence Form to Kitchensink

1 Initial Problem

Creating recurring appointments uses unique interface elements. The current implementation cannot be merely be implemented using KS-Forms. The current form needs some re-arranging to fit the KS-Elements available in 10.  

2 Conceptual Summary

Adding recurring appointments is moved to KS by splitting the form.

1. The first form captures input on title, date, notification etc.  When the form is saved, the specific date is known. 
2. The second form is only shown, if said date was set to have a recurrence. Since the date is known (weekday, week in month and so forth), the options can be very specific based on this information.  

3 User Interface Modifications

3.1 List of Affected Views

• Personal Workspace > Calendar > Agenda > Create Appointment 

3.2 User Interface Details

3.3 New User Interface Concepts

No new elements just forms, modals. 

3.4 Accessibility Implications

No issues forseeable. 

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

No issues forseeable. 

7 Contact

• Author of the Request: Tödt, Alexandra [atoedt]
• Maintainer: Meyer, Stefan [smeyer]
• 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

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