Documentation for Developers

The plugin follows the idea that there are two different kinds of tasks to be done, for successfully implementing a custom workflow for deleting courses. The first tasks is identifying, which courses have to be considered for deletion in the first place. The second task is much more generic and can be any kind of small work, which has to be done during the whole cleanup process (create backup, hide course, delete course, etc.). Since we didn't want to restrict any user to a small amount of possibilities we created a plugin, which knows two kinds of subplugins.

• Trigger subplugins specify how to test a course, if it should be considered for deletion.
• Step subplugins can specify, what should be done during the cleanup process.

To be able to develop new subplugins, which bring in the functionality you need in your cleanup process, both subplugin types specify an API, which can be used. This way, new subplugins should integrate smoothly into the existing cleanupcourses plugin.

Wrtiting your own Trigger Subplugin

Wrtiting your own Step Subplugin