RFC Start Date
2025-03-05
Target Plan Accepted Date
2025-03-19
Target Transition Unblocked Date
2025-07-23
Earliest Breaking Changes Unblocked Date
2024-08-04
Ulmo - 2025-10
Rationale
Transition Steps
Please note: Some of these breaking changes will be implemented by 2U and others will be implemented by Axim through an FC. Please see "Tasks" for division of labor.
BREAKING CHANGE:: The option to create_zendesk_tickets for suspicious Proctored exam attemps will be removed from all courses.
BREAKING CHANGE: Previously, Studio required authors to provide an escalation email for proctored exams using the Proctortrack backend. Now, rather than validation this for Proctortrack exams in particular, Studio will now enforce it for any proctored exam whose backend is configured with requires_escalation_email: True. In order to retain the validation behavior for Proctortrack exams, operators will need to provide this configuration value in their Proctortrack backend, like this:
PROCTORING_BACKENDS = {
"proctortrack": {
"base_url": "<redacted>",
...,
"requires_escalation_email": True, # <-- New setting! Defaults to False.
},
...,
}
BREAKING CHANGE: Previously, Studio would show a "Review Rules" field a part of proctoring configuration for all providers except Proctotrack; for Proctotrack in particular, it would show the Review Rules field iff the studio.show_review_rules CourseWaffleFlag was set to True. In order to remove Proctortrack-specific logic from the platform, we will remove the studio.show_review_rules Waffle flag, and add a new show_review_rules option to provider configuration dictionary. This will default to True, which will be a no-op for most providers. However, for users of Proctortrack, they will want to ensure that the show_review_rules option is set correctly. Pleasenote: this removes the ability to toggle review rules on a per-course basis.
PROCTORING_BACKENDS = {
"proctortrack": {
"base_url": "<redacted>",
...,
"show_review_rules": False, # <-- New setting! Default to True.
},
...,
}
BREAKING CHANGE: edx-proctoring-proctortrack will be removed from github.in and thus removed from edx-platform's base requirements. Operators using Proctortrack should pip-install this package into their instance as an extra.
BREAKING CHANGE: edx-proctoring-proctortrack will be removed from package.json. Operators using Proctortrack should npm-install this package into their instance as an extra.
Replacement
The edx-proctoring-proctortrack plugin package continues to be maintained by 2U, but operators must install it separately rather than counting on it as a core requirement.
We may transfer this package into the openedx organization if 2U is willing to contribute and maintain it.
Existing technical discovery
2U did a discovery spike a few months ago when we first opened this ticket, which contains a lot of helpful information: https://docs.google.com/document/d/17-J1Nc15MkLLvv5sG6QIoQgj_Z1Lml2YHOiQIZI8XPQ/edit?tab=t.0#heading=h.gpsdcgbix0sd
Please note that the tasks and division of labor in that document are out-of-date. This ticket contains the most up-to-date plan.
Task List
2U Tasks
Axim FC Tasks
PRs
RFC Start Date
2025-03-05
Target Plan Accepted Date
2025-03-19
Target Transition Unblocked Date
2025-07-23
Earliest Breaking Changes Unblocked Date
2024-08-04
Ulmo - 2025-10
Rationale
uv.Transition Steps
Please note: Some of these breaking changes will be implemented by 2U and others will be implemented by Axim through an FC. Please see "Tasks" for division of labor.
BREAKING CHANGE:: The option to
create_zendesk_ticketsfor suspicious Proctored exam attemps will be removed from all courses.BREAKING CHANGE: Previously, Studio required authors to provide an escalation email for proctored exams using the Proctortrack backend. Now, rather than validation this for Proctortrack exams in particular, Studio will now enforce it for any proctored exam whose backend is configured with
requires_escalation_email: True. In order to retain the validation behavior for Proctortrack exams, operators will need to provide this configuration value in their Proctortrack backend, like this:BREAKING CHANGE: Previously, Studio would show a "Review Rules" field a part of proctoring configuration for all providers except Proctotrack; for Proctotrack in particular, it would show the Review Rules field iff the
studio.show_review_rulesCourseWaffleFlag was set to True. In order to remove Proctortrack-specific logic from the platform, we will remove thestudio.show_review_rulesWaffle flag, and add a newshow_review_rulesoption to provider configuration dictionary. This will default to True, which will be a no-op for most providers. However, for users of Proctortrack, they will want to ensure that the show_review_rules option is set correctly. Pleasenote: this removes the ability to toggle review rules on a per-course basis.BREAKING CHANGE: edx-proctoring-proctortrack will be removed from github.in and thus removed from edx-platform's base requirements. Operators using Proctortrack should pip-install this package into their instance as an extra.
BREAKING CHANGE: edx-proctoring-proctortrack will be removed from package.json. Operators using Proctortrack should npm-install this package into their instance as an extra.
Replacement
The edx-proctoring-proctortrack plugin package continues to be maintained by 2U, but operators must install it separately rather than counting on it as a core requirement.
We may transfer this package into the openedx organization if 2U is willing to contribute and maintain it.
Existing technical discovery
2U did a discovery spike a few months ago when we first opened this ticket, which contains a lot of helpful information: https://docs.google.com/document/d/17-J1Nc15MkLLvv5sG6QIoQgj_Z1Lml2YHOiQIZI8XPQ/edit?tab=t.0#heading=h.gpsdcgbix0sd
Please note that the tasks and division of labor in that document are out-of-date. This ticket contains the most up-to-date plan.
Task List
2U Tasks
create_zendesk_ticketsand related logic and dependencies.Axim FC Tasks
requires_escalation_emailoption to the backends within the PROCTORING_BACKENDS Django setting, defaulting to False. Wherever Proctortrack is referenced in order to decide whether an escalation email is required, checkrequires_escalation_emailinstead. Update tests and documentation as appropriate.show_review_rulesoption to the backends within the PROCTORING_BACKENDS Django setting, defaulting to True. Wherever Proctortrack and/or the SHOW_REVIEW_RULES_FLAG Waffle flag is referenced in order to decide whether to show the Review Rules proctoring form field, checkshow_review_rulesinstead. Remove the existing SHOW_REVIEW_RULES_FLAG Waffle flag. Update tests and documentation as appropriate.PRs