- Timestamp:
- 24 Mar 2017, 09:09:17 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk/docs/source/userdocs/students/interfaces.rst
r14574 r14654 288 288 The quite long list of schema fields pretends that form pages may 289 289 provide these fields for editing. This is not the case. Except for 290 `score`, `mandatory` and `outstanding` all other fields are 'for 291 display' only. They can neither be changed through the UI nor by 292 batch processing (import). They are solely meant for backing up the 293 orginal course data. See also :ref:`course_ticket_processor`. 290 `score`, `mandatory`, `outstanding` and `course_category` (not 291 available in base package) all fields are 'for display' only. 292 They cannot be changed through the UI. They are solely meant for 293 backing up the orginal course data. However, some of them can be 294 overwritten by batch processing (import), see 295 :ref:`course_ticket_processor`. 294 296 295 297 .. note:: … … 298 300 example the number of credits was set too high. The course object 299 301 can be corrected, but, course tickets, which refer to this course, 300 can not. They are n either adjusted automatically nor changeable by301 the batch processor. The only solution to 'adjust' course tickets is302 to rep lace them by new tickets.302 can not. They are not adjusted automatically. If you want to correct 303 course tickets you have to replace them by new tickets or 304 to repair the data by batch processing. 303 305 304 306 Student Payment Interfaces
Note: See TracChangeset for help on using the changeset viewer.