Important: The job validation flags follow the persons vocabulary 

Description 

The flags of Configuration/AcademicJobs/Settings.yaml are read by the shared settings classes of academic_base, and mean what they mean in academic_persons:

• Flags are read regardless of case and of spaces around them. A flag written Required made nothing required before and rendered <input type="Required"> . It makes the field required now.
• A flag outside the shared vocabulary is ignored. Before, the new job form rendered the first flag that was not required as the HTML input type, so a typo produced an input such as <input type="disabledd"> .
• readonly , disabled and frontendreadonly take effect. They cancel required in the form and in the check of a submitted job, and the first two lock the field in the backend. The form keeps offering the field.

The shipped settings mark the contact phone with tel since 2.4, see Important: The new job form stores the chosen values. A site package that copied the whole block of an earlier version still names number and has to change it, see Breaking: The job validation settings reach the backend.

A required settings field the job has no property for is left out of the check of a submitted job. Before, it made every submission fail.

Affected installations 

Installations whose site package ships its own settings file with flags not in lower case, with an unknown flag, or with a field the job has no property for.