- Timestamp:
- 29 Jan 2015, 10:22:32 (10 years ago)
- Location:
- main/waeup.ikoba/trunk
- Files:
-
- 3 edited
-
README.txt (modified) (6 diffs)
-
src/waeup/ikoba/browser/interfaces.py (modified) (1 diff)
-
src/waeup/ikoba/browser/templates/changepw.pt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
main/waeup.ikoba/trunk/README.txt
r12432 r12520 37 37 ------- 38 38 39 The main web application and container class is called 'Company' which corresponds to the University container in Kofa. 39 The main web application and container class is called 'Company' which corresponds to the university container in Kofa. The company container contains sub-containers for products, public documents, customers and officers (regular users). 40 40 41 41 42 Products 42 43 -------- 43 44 44 Among others, a company includes a 'products' container which contains the products offered by the company. A product could be a license, a visa or any purchasable merchandise/article. In the base package a product has eight attributes: 45 46 - unique product id, 47 - title 48 - contract title 49 - contract_category 50 - options (set of product options) 51 - valid from 52 - valid to 53 - terms and conditions 45 A company offers products usually for sale. A product could be a license, a visa or any purchasable merchandise/article. In the base package a product has eight attributes, unique product id, title, contract title, contract_category, options (set of product options), valid from, valid to, terms and conditions 54 46 55 47 Products don't have a workflow. 48 56 49 57 50 Public Documents 58 51 ---------------- 59 52 60 Public documents , which are likewise put up in a 'documents' container,are meant for publishing content on the portal. There are three types of public documents:53 Public documents are meant for publishing content on the portal. There are three types of public documents: 61 54 62 55 - PDF documents … … 64 57 - REST documents 65 58 66 The first can be used to provide pdf files for download. The second and third can be used to create multilingual static html pages on the portal. HTML documents expect html coded text as input, REST documents expect reRtructuredText which is transformed into html. Public documents have a publication workflow with two states: created and published. Only published documents can be seen by anonymous users. 59 The first can be used to provide pdf files for download. The second and third can be used to create multilingual static html pages on the portal. HTML documents expect html coded text as input, REST documents expect reStructuredText which is transformed into html. Public documents have a publication workflow with two states: created and published. Only published documents can be seen by anonymous users. 60 61 62 Officers 63 -------- 64 65 Officers are regular users or principals of the system with a set of global and local roles which allows them to view or manage the various sections in Ikoba. In contrast to classical content management systems, officers do not manage their own space where they can add and edit own content. Ikoba officers can just access those parts of the portal which their roles or sets of permissions allow them to access. 66 67 An officer has eight attributes: unique login name, title (fullname), public name, description, email address, phone number, set of roles, encrypted password 68 69 Officers can't register themselves. They have to be added by the initial system administrator or by officers who have the permission to manage user data. 70 71 Officers don't have a workflow. 72 67 73 68 74 Customers 69 75 --------- 70 76 71 The company container also contains a 'customers' container which again contains all customers of the company. A customer object itself is also a container, containing all the documents and contracts owned by the customer. Beyond that, a customer is also an authenticated user of the system with a user account adapted to each customer object.77 The term 'customer' has two different meanings in Ikoba. On the one hand a customer is a container object which contains all the documents and contracts owned by a prospective or registered client or contractor of the company. On the other hand a customer is an authenticated users or principal of the system with a user account adapted to each customer container object. 72 78 73 The attributes of a customer in the base package are: customer id, firstname, middlename, lastname, sex, email, phone and a unique registration number which can be set by the company.79 The attributes of a customer in the base package are: customer id, firstname, middlename, lastname, sex, email, phone, an encrypted password and a unique registration number which can be set by the company. 74 80 75 81 Customers have a registration workflow with four states: created, started, requested and approved. … … 78 84 79 85 Only approved customers can conclude contracts (see below). 86 87 Customers can register themselves. They need a valid email address fo self-registration. 88 80 89 81 90 Customer Documents … … 88 97 Various document classes can be implemented and selected by the customer to make customization as flexible as possible. 89 98 90 Verified documents cannot be edited or manipulated. The md5 checksum proves the genuineness of the uploaded file. 99 Once a document has been submitted, it can no longer be edited by customers. Verified documents can neither be edited by customers nor by officers. 100 101 The md5 checksum proves the genuineness of the uploaded file. 91 102 92 103 A pdf document slip can be downloaded. The slip is composed of a covering page and the scanned document badged by a watermark. 104 93 105 94 106 Contracts … … 105 117 7. submitting the contract form for approval. 106 118 107 Company officers verify the documents and finally approve the contract which means that the contract is concluded. The contract can also be rejected or expire. 119 A customer has to register first but must not wait for approval before s/he can add contracts. Only after registration the customer can proceed to the contracts section and add, pay and submit contracts. If documents have to be uploaded and attached to the contract, these documents must be at least submitted for verification. Otherwise they cannot be attached. This ensures that documents can't be modified after application (= submission of contracts). Thus, a new customer can register, add and submit documents and then add, pay and submit contracts in just one single session. 120 121 Company officers approve the customer registration request first, then verify the customer's documents and finally approve the contracts submitted by the customer. Approving a contract means that the contract is concluded. Contracts can also be rejected or expire. 108 122 109 123 Each contract class belongs to a contract category. The contract category defines the subset of products which can be selected when configuring the contract (see Products section above). … … 111 125 A contract in the base package has a title, a unique contract id, one document reference, one product reference and list of product options. A customized contract can have several document references, but it can only refer to a single product offered by the company. The product options determine the fees to be paid before a contract can be concluded. 112 126 113 A contract can only be submitted if all documents attached to the contract have been at least submitted for verification. 127 A contract can only be submitted if all documents attached to the contract have been at least submitted for verification. Contracts can only be approved if the customer registration request has been approved and then all attached documents have been verified by an officer. 114 128 115 129 The contract workflow has the following states: created, submitted, approved, rejected and expired. -
main/waeup.ikoba/trunk/src/waeup/ikoba/browser/interfaces.py
r11958 r12520 173 173 title = _(u'Unique Identifier'), 174 174 description = _( 175 u'User Name, Customer Id ,or '175 u'User Name, Customer Id or ' 176 176 u'Registration Number'), 177 177 required = True, -
main/waeup.ikoba/trunk/src/waeup/ikoba/browser/templates/changepw.pt
r11949 r12520 16 16 </tbody> 17 17 </table> 18 18 <br /> 19 19 <p i18n:translate="email_address_problem"> 20 20 Enter the email address stored in Ikoba.
Note: See TracChangeset for help on using the changeset viewer.
