Object classes
In the current version, the workflow functionality can only be used for the purpose of maintaining a project base.
The main element of the organization of the workflow is the definition of object classes.
The distinction of object classes is made in terms of the differential handling of given project types by the various units involved in the development of descriptions. It is necessary to define such object classes in order to enable the appropriate treatment of a given type of projects at the various stages of development at the service points that are involved in the data entry process at a given stage. The number of object classes usually corresponds to the number of units involved in the data entry process of a given object type (in this case, projects).
In the example solution (experimentally used at the Warsaw University of Technology), it was assumed that contractual two "units" would be involved in the process of entering project data:
central university unit responsible for handling projects (Project Service Center, shorter PSC)
Project managers (at departmental level)
For the purpose of project processing definitions, object classes have been defined in the system as seen in the figure below.
Classes including project applications and projects:
Project applications managed by PSC (projectapplication:maincentral)
Projects managed by the PSC (maincentral)
Projects managed by departments (mainlocal)
Only one class is provided for project applications, as it was assumed that applications would be entered into the database only by the central unit. Users at the departmental level do not have an option in the menu to enter project applications.
Classes including auxiliary data used in the sPSCe of project object classes:
Types of projects/programs managed by PSC (mainpptcentral)
Types of projects/programs managed by departments (mainpptlocal)
Institutions and institutional authors (main)
Dictionary data managed by PSC (mainddcentral)
In each class, you define restrictions on the fields and tabs in the form to which access is implemented.