https://cs.uwaterloo.ca/~cs-oat/devdoc/subsystems/forms/index.html The forms subsystem is in a bit of a mess because we started an ambitious project to add coop stream sequence forms, which requires a degree of workflow management. Unfortunately, it didn’t get completed before the co-op student working on it left – and I haven’t had time to work on it since. There are two documents here that document what we were trying to do that may be helpful: Hugo en-us https://cs.uwaterloo.ca/~cs-oat/devdoc/subsystems/forms/form_defs/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://cs.uwaterloo.ca/~cs-oat/devdoc/subsystems/forms/form_defs/index.html Forms are defined with JSON (but see issue 2282). Typically they are collected in the oat-forms project in git. Form Sections: The top-level sections of a form definition are name, theme, useif, formElements, restrictions, and reportExpr. Name The name of the form, as it appears in a list of forms to advisors or students. Theme: The name of a CSS file that allows different units/faculties to have a consistent colour scheme, for example. The most common value is themeCS.css. It’s generated from _wapp/app/assets/stylesheets/themeCS.less. Two other themes exist as of 2025-07-28: themeCourseOverride.less and themeMath.less. https://cs.uwaterloo.ca/~cs-oat/devdoc/subsystems/forms/w20_initial_thoughts/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://cs.uwaterloo.ca/~cs-oat/devdoc/subsystems/forms/w20_initial_thoughts/index.html We’re working on redesigning/upgrading the Forms, primarily to accommodate co-op sequence change forms. (Unfortunately, this work did not get completed before the coop student moved on. As a result, the forms subsystem is in a poor state of repair.) Forms are already being used in other settings, primarily for faculty transfer processes. Whatever we do here needs to preserve functionality for those other processes. We’d like the functionality to be general enough to support lots of processes. https://cs.uwaterloo.ca/~cs-oat/devdoc/subsystems/forms/w20_design/index.html Mon, 01 Jan 0001 00:00:00 +0000 https://cs.uwaterloo.ca/~cs-oat/devdoc/subsystems/forms/w20_design/index.html High-Level Process A form will have zero or more “advisors” who need to make a decision about the form. In the coop context, there might be a plan-level advisor, a faculty-advisor, perhaps an option-advisor, etc. In addition, there might be an Records “advisor” or “coordinator” in Coop (or, for other processes, in the Registrar’s Office or an undergrad office). They give the final decision and then record the result in WaterlooWorks (or Quest).