My group wants to change the way the mod_assign marking workflow functions, e.g. new/different states, sending emails on different/additional events.
Is there a recommended approach to this?
It might be overkill, but I could imagine a system where - rather than hardcoding states - we create custom workflows as (sub)modules that:
- define each state,
- define which state transitions are allowed for which capabilities,
- use the Events API to emitting entry and exit events on each state transition
- define actions to take on particular state transition events (e.g. enter "Released" = send email to student).