Ignore:
Timestamp:
24 Apr 2015, 10:07:26 (10 years ago)
Author:
Henrik Bettermann
Message:

More docs.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • main/waeup.kofa/trunk/docs/source/userdocs/datacenter/import_processors.rst

    r12872 r12882  
    8383.. autoclass:: waeup.kofa.students.batching.StudentStudyLevelProcessor()
    8484  :noindex:
     85
     86.. note::
     87
     88  The student data processors described so far are mainly intended for restoring data. If the portal is operated correctly and without interruption and students follow the workflow from their first to the final study year, there is no need to use the above batch processors to maintain the data. The processors are not part of the student registration management. The following processors can or sometimes even must be integrated into the regular management of student data. Scores have to be imported, new payment tickets have to created, the verdicts have to be set or workflow transitions have to be triggered.
     89
     90Course Ticket Processor
     91-----------------------
     92
     93.. autoclass:: waeup.kofa.students.batching.CourseTicketProcessor()
     94  :noindex:
     95
     96Student Online Payment Processor
     97--------------------------------
     98
     99.. autoclass:: waeup.kofa.students.batching.StudentOnlinePaymentProcessor()
     100  :noindex:
     101
     102Verdict Processor
     103-----------------
     104
     105.. autoclass:: waeup.kofa.students.batching.StudentVerdictProcessor()
     106  :noindex:
Note: See TracChangeset for help on using the changeset viewer.