Presentation Video Moodle Moot 2022 | Slides
This plugin provides a modular framework, similar to a workflow engine, which allows the to execute recurring tasks within moodle associated with courses. Possible use cases are (not limited to):
- Deleting courses at end of life (including asking teachers for permission).
- Doing a rollover at the end of a semester.
- Automatically setting an end date for courses.
To be adaptable to the needs of different institutions the plugin provides two subplugin types:
Trigger: These subplugins control the conditions a course must meet so that a specific process is started.
Step: These subplugins represent atomic, reusable tasks that should be executed for a specific course.
Requirements that are specific to your institution can be added through additional subplugins. A list of all subplugins and more information can be found in the Wiki (subpluginslist). It provides instructions for administrators as well as for developers to implement their own requirements into subplugins.
This is an admin plugin and should go into admin/tool/lifecycle.
In the current Lifecycle version 4.5.5 (v4.5-r6), it may be necessary to delete the old directory admin/tool/lifecycle and clone the new version with Git. This should be possible without any issues, as no user data is stored in that directory. ==> But be aware: If you are using the customfieldsemester trigger or other special triggers and steps, or if you have made local changes to the included triggers or steps you would need to save them before installation and copy them into the new directory afterwards.
Obtain this plugin from https://moodle.org/plugins/view/tool_lifecycle.
The plugin is continuously tested with all moodle versions, which are security supported by the moodle headquarter.
![@github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=64&v=4){kind=small}