- Timestamp:
- 30 Jun 2015, 21:22:31 (9 years ago)
- Location:
- main/waeup.kofa/trunk/docs/source
- Files:
-
- 1 added
- 3 edited
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.kofa/trunk/docs/source/developerdocs/index.rst
r12863 r13120 1 .. _developer_handbook: 2 1 3 Developer Handbook 2 4 ****************** -
main/waeup.kofa/trunk/docs/source/userdocs/configuration.rst
r13118 r13120 1 Configuration and Customization2 *******************************3 4 1 .. _configuration: 5 2 6 3 Portal Configuration 7 ==================== 4 ******************** 8 5 9 6 There are many places in Kofa where portal parameters can be set or 10 7 page descriptions can be added. These parameters are attributes of 11 8 either dedicated configuration objects or of containers in the 12 academics and applicants section. The latter have been described13 elsewehere. Here we explain the interfaces of the configuration 14 section.9 academics, applicants or data center sections. The latter have been 10 described elsewehere. Here we explain the interfaces of the 11 configuration section. 15 12 16 13 Technically speaking, the portal configuration section is a 17 14 container of type `ConfigurationContainer` with id ``configuration`` 18 which contains session configuration sub containers::15 which contains session configuration subobjects:: 19 16 20 17 … … 28 25 29 26 Site Settings 30 ------------- 27 ============= 31 28 32 The site setting parameters are the attributes of the configuration 33 container to be set via the `ConfigurationContainerManageFormPage`. 34 The pageopens, if an officer with29 Site parameters are the attributes of the configuration container to 30 be set via the `ConfigurationContainerManageFormPage`. The page 31 opens, if an officer with 35 32 :py:class:`ManagePortalConfiguration<waeup.kofa.permissions.ManagePortalConfiguration>` 36 33 permission clicks the 'Portal Configuration' link in the side box. 34 35 The `ConfigurationContainer` class implements exactly one interface: 36 37 37 38 38 .. literalinclude:: ../../../src/waeup/kofa/interfaces.py 39 39 :pyobject: IConfigurationContainer 40 40 41 The page alows furthermore to add or access the containing session42 configuration objects.41 The page furthermore lists containing session configuration objects 42 and allows to add them. 43 43 44 44 Session Settings 45 ---------------- 45 ================ 46 46 47 Session parameters are the attributes of session configuration 48 objects. These parameters may vary between academic sessions. 49 Particularly student fees, which often vary from one session to the 50 next, can be configured here, if the portal has been customized 51 accordingly, see :ref:`customization` below. The session 52 configuration objects also serve to: 47 53 54 - disable student payments for certain payment categories and 55 subgroups of students 56 57 See also `Disable Payment Groups 58 <https://kofa-demo.waeup.org/sources#collapseDisablePaymentGroups>`_ 59 in the base package. 60 61 - disable clearance by clearance officers for the selected session 62 63 If clearance is disabled, students can still fill and submit the 64 clearance form, but clearance officers can't process the clearance 65 requests afterwards. They can neither clear these students nor 66 reject their clearance request. 67 68 - set the course registration deadline 69 70 If the course registration deadline is set, student can't register 71 courses unless they pay the late registration fee. 72 73 Session configuration objects implement the following interface: 48 74 49 75 .. literalinclude:: ../../../src/waeup/kofa/interfaces.py 50 76 :pyobject: ISessionConfiguration 51 52 53 54 55 .. _customization:56 57 Portal Customization58 ==================== -
main/waeup.kofa/trunk/docs/source/userdocs/index.rst
r13084 r13120 17 17 users 18 18 reports 19 mandates 19 20 configuration 20 mandates21 customization 21 22 testing 22 23 buildingdocs
Note: See TracChangeset for help on using the changeset viewer.