- Timestamp:
- 19 Sep 2015, 12:27:24 (9 years ago)
- Location:
- main/waeup.kofa/trunk/docs/source/userdocs
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk/docs/source/userdocs/applicants.rst
r13108 r13273 34 34 in Python docstrings the term 'application' predominates. 35 35 36 Much like students, applicants are also ausers of the portal and36 Much like students, applicants are also users of the portal and 37 37 the applicant object is a user account surrogate, see 38 38 :ref:`Applicants and Students <applicants_and_students>`. In the … … 40 40 about an applicant. 41 41 42 In contrast to student scontainers, applicant containers do not42 In contrast to student containers, applicant containers do not 43 43 contain subcontainers. The only objects they contain are applicant 44 44 payment tickets (i.e. instances of `ApplicantOnlinePayment`). Thus -
main/waeup.kofa/trunk/docs/source/userdocs/applicants/create_students.rst
r13118 r13273 12 12 1. Officers can create student records from single applicant 13 13 records. A link button appears on the display page of each admitted 14 applicant swhich directly triggers the creation process:14 applicant which directly triggers the creation process: 15 15 16 16 |create_student_button| … … 23 23 24 24 Only admitted applicants will be processed. Other selected 25 applicants will be skipped without further notice 25 applicants will be skipped without further notice. 26 26 27 27 3. Last but not least, the portal manager with user id ``admin`` 28 does see a link button s:28 does see a link button: 29 29 30 30 |create_students_button|
Note: See TracChangeset for help on using the changeset viewer.