Restricted" or "open-ended" fields are defined in the restrictions file.xml on plugin odf-pilotage.

You can override this file by adding a restrictions file.xml in WEB-INF/param/odf/pilotage/

By default, fields with evolving rights are configured as follows:

 

mention_validated

orgunit_validated

cfvu_validated

cfvu_mcc_validated

PROGRAM

title
domain
rncpCode
rncpLevel
cite97Code
jointOrgUnit
ects
educationKind
formofteachingOrg
distanceLearning
speciality
mention
duration
educationLevel
educationEntryLevel

 

 

 

SUBPROGRAM

 title
domain
rncpCode
rncpLevel
cite97Code
jointOrgUnit
ects
educationKind
formofteachingOrg
distanceLearning
speciality
mention
duration
educationLevel
educationEntryLevel

 

 

 

CONTAINER

catalog
ects
nature
period

 

 

 

COURSELIST

catalog
choiceType
min
max

 

 

 

RACE

title
courseType
ects
level

 

 

isEvaluated
weightModu
mccSession1/natureTeaching
mccSession1/modalite
mccSession1/nature
mccSession1/duree
mccSession1/number
mccSession1/coefficient
mccSession1/marks
mccSession2/natureLearning
mccSession2/modality
mccSession2/nature
mccSession2/duration
mccSession2/number
mccSession2/coefficient
mccSession2/marks

How to interpret the configuration :

  • when a course is upgraded to "Validated for Mention" status, the title, domain, etc. fields are blocked from writing to the course object for all users who do not have the specific "Validated for Mention" post modification right.
  • when a course is upgraded to "Validated for Mention" status, the title, domain, etc. fields are blocked from writing to the course objects for all users who do not have the specific "Validated for Mention" post modification right.
  • when a course is upgraded to "Validated for Mention" status, the catalog, ects, etc. fields are blocked from writing to the course's container objects for all users who do not have the specific "Validated for Mention" post modification right.
  • ...
Back to top