Documentation for Developers

The plugin follows the idea that there are two different kinds of tasks to be done, for successfully implementing any kind of custom workflow. The first tasks is the identification, 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 task, which has to be done during the whole process following the definition of the workflow. In case of a workflow that should delete courses at the end of their lifecycle relevant tasks could be: create a backup, hide the course and eventually delete the course. 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 custom workflow, both subplugin types specify an API, which can be used. This way, new subplugins should integrate smoothly into the existing lifecycle plugin.

Writing your own Trigger Subplugin

Writing your own Step Subplugin