Submitting to a Kalvid Assignment does not automatically remove it from your Timeline block on the Dashboard, where it will become marked as "overdue" and be visible for two weeks after the submission due date.
This leads to student confusion about whether their submission has been accepted by the Moodle system.
This will all work as expected if you take the extra step to set a completion condition for the activity using the common functionality provided for that task on all activity plugins.
However in comparable submission-centered activities, like core mod_assign or 3rd party Turnitin, this extra step is not required. They will check the completion_info completionstate (based on e.g. requiring a submission or a grade or the student manually marking as complete) if they are set up, but if not configured they will also check for simple submission by students and remove from timeline in that case, avoiding this issue.
You can compare the functions mod_assign_core_calendar_provide_event_action,
mod_kalvidassign_core_calendar_provide_event_action and mod_turnitintooltwo_core_calendar_provide_event_action in the respective plugins' lib.php to see that they return null (i.e. remove from timeline/calendar) when the completion_info system says the task is complete, but also when the user has a submission in the DB.
I'd suggest it makes sense to add similar code to Kalvid assign for consistency.
Submitting to a Kalvid Assignment does not automatically remove it from your Timeline block on the Dashboard, where it will become marked as "overdue" and be visible for two weeks after the submission due date.
This leads to student confusion about whether their submission has been accepted by the Moodle system.
This will all work as expected if you take the extra step to set a completion condition for the activity using the common functionality provided for that task on all activity plugins.
However in comparable submission-centered activities, like core mod_assign or 3rd party Turnitin, this extra step is not required. They will check the
completion_info completionstate(based on e.g. requiring a submission or a grade or the student manually marking as complete) if they are set up, but if not configured they will also check for simple submission by students and remove from timeline in that case, avoiding this issue.You can compare the functions
mod_assign_core_calendar_provide_event_action,mod_kalvidassign_core_calendar_provide_event_actionandmod_turnitintooltwo_core_calendar_provide_event_actionin the respective plugins'lib.phpto see that they returnnull(i.e. remove from timeline/calendar) when thecompletion_infosystem says the task is complete, but also when the user has a submission in the DB.I'd suggest it makes sense to add similar code to Kalvid assign for consistency.