Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
StudentApp
Please create a React-JS application for the StudentModule. The application has to offer the following views for the user interface: 1. AccidentView 2. AdministrativeOfficeView 3. BreakPlanEntryView 4. ConferenceAttendeeView 5. ConsumableMaterialView 6. ContributionView 7. CourseGroupMemberView 8. EventTaskView 9. EventTaskDependencyView 10. GenderView 11. MigrationBackgroundView 12. NurseryView 13. OfficeAgentView 14. ProjectView 15. ProjectAppointmentView 16. ProjectAttendeeView 17. ProjectOrganizerView 18. ReligionView 19. ReportTypeView 20. SchoolBreakView 21. SchoolEventView 22. SchoolEventAttendeeView 23. SchoolEventTypeView 24. StudentView 25. StudentMaterialView 26. StudentRepresentationView 27. StudentTransportView 28. SwimmingInsigniaView 29. TeacherView 30. TeacherBoardMemberView 31. TestResultView 32. VitaEntryView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 32 views are defined below. 1. The AccidentView must contain the following fields: - name: Description type: STRING - name: Student type: Student - name: AccidentDate type: DATE The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing Accident entity should be loaded from the relative URL: "/StudentService/accident/{id}" (HTTP-GET) If a new Accident entity has been created, the new entity should be posted to the relative URL: "/StudentService/accident" (HTTP-POST) If an existing Accident entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/accident/{id}" (HTTP-PUT) If an existing Accident entity has to be deleted, the following relative URL should be called: "/StudentService/accident/{id}" (HTTP-DELETE) 2. The AdministrativeOfficeView must contain the following fields: - name: OfficeName type: STRING - name: Description type: STRING An existing AdministrativeOffice entity should be loaded from the relative URL: "/StudentService/administrativeoffice/{id}" (HTTP-GET) If a new AdministrativeOffice entity has been created, the new entity should be posted to the relative URL: "/StudentService/administrativeoffice" (HTTP-POST) If an existing AdministrativeOffice entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/administrativeoffice/{id}" (HTTP-PUT) If an existing AdministrativeOffice entity has to be deleted, the following relative URL should be called: "/StudentService/administrativeoffice/{id}" (HTTP-DELETE) Add a HTML table to the view with the following OfficeAgent columns: - column: Teacher - column: AdministrativeOffice The table should have the title "OfficeAgents" und the data must be loaded from the server with the following relative URL: "/StudentService/officeagent/administrativeoffice/{id}" 3. The BreakPlanEntryView must contain the following fields: - name: EntryDate type: DATE - name: SchoolBreak type: SchoolBreak - name: Teacher type: Teacher - name: BreakPlan type: BreakPlan The data source for the [BreakPlan] select control should be loaded from the relative URL: "/SchoolYearService/breakplan" (HTTP-GET) The data source for the [Teacher] select control should be loaded from the relative URL: "/StudentService/teacher" (HTTP-GET) The data source for the [SchoolBreak] select control should be loaded from the relative URL: "/StudentService/schoolbreak" (HTTP-GET) An existing BreakPlanEntry entity should be loaded from the relative URL: "/StudentService/breakplanentry/{id}" (HTTP-GET) If a new BreakPlanEntry entity has been created, the new entity should be posted to the relative URL: "/StudentService/breakplanentry" (HTTP-POST) If an existing BreakPlanEntry entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/breakplanentry/{id}" (HTTP-PUT) If an existing BreakPlanEntry entity has to be deleted, the following relative URL should be called: "/StudentService/breakplanentry/{id}" (HTTP-DELETE) 4. The ConferenceAttendeeView must contain the following fields: - name: ExternalPerson type: ExternalPerson - name: Conference type: Conference - name: Teacher type: Teacher - name: Student type: Student The data source for the [ExternalPerson] select control should be loaded from the relative URL: "/ExternalPersonService/externalperson" (HTTP-GET) The data source for the [Teacher] select control should be loaded from the relative URL: "/StudentService/teacher" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) The data source for the [Conference] select control should be loaded from the relative URL: "/ConferenceService/conference" (HTTP-GET) An existing ConferenceAttendee entity should be loaded from the relative URL: "/StudentService/conferenceattendee/{id}" (HTTP-GET) If a new ConferenceAttendee entity has been created, the new entity should be posted to the relative URL: "/StudentService/conferenceattendee" (HTTP-POST) If an existing ConferenceAttendee entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/conferenceattendee/{id}" (HTTP-PUT) If an existing ConferenceAttendee entity has to be deleted, the following relative URL should be called: "/StudentService/conferenceattendee/{id}" (HTTP-DELETE) 5. The ConsumableMaterialView must contain the following fields: - name: Description type: STRING - name: MaterialName type: STRING An existing ConsumableMaterial entity should be loaded from the relative URL: "/StudentService/consumablematerial/{id}" (HTTP-GET) If a new ConsumableMaterial entity has been created, the new entity should be posted to the relative URL: "/StudentService/consumablematerial" (HTTP-POST) If an existing ConsumableMaterial entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/consumablematerial/{id}" (HTTP-PUT) If an existing ConsumableMaterial entity has to be deleted, the following relative URL should be called: "/StudentService/consumablematerial/{id}" (HTTP-DELETE) Add a HTML table to the view with the following StudentMaterial columns: - column: Comments - column: Amount - column: ConsumableMaterial - column: DesignatedUse - column: Costs - column: Student - column: Paid The table should have the title "StudentMaterials" und the data must be loaded from the server with the following relative URL: "/StudentService/studentmaterial/consumablematerial/{id}" 6. The ContributionView must contain the following fields: - name: Amount type: DOUBLE - name: Student type: Student - name: SchoolTrip type: SchoolTrip - name: SchoolEvent type: SchoolEvent - name: PaymentDetails type: STRING The data source for the [SchoolTrip] select control should be loaded from the relative URL: "/SchoolClassStudentService/schooltrip" (HTTP-GET) The data source for the [SchoolEvent] select control should be loaded from the relative URL: "/StudentService/schoolevent" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing Contribution entity should be loaded from the relative URL: "/StudentService/contribution/{id}" (HTTP-GET) If a new Contribution entity has been created, the new entity should be posted to the relative URL: "/StudentService/contribution" (HTTP-POST) If an existing Contribution entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/contribution/{id}" (HTTP-PUT) If an existing Contribution entity has to be deleted, the following relative URL should be called: "/StudentService/contribution/{id}" (HTTP-DELETE) 7. The CourseGroupMemberView must contain the following fields: - name: CourseGroup type: CourseGroup - name: Student type: Student The data source for the [CourseGroup] select control should be loaded from the relative URL: "/SchoolSubjectService/coursegroup" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing CourseGroupMember entity should be loaded from the relative URL: "/StudentService/coursegroupmember/{id}" (HTTP-GET) If a new CourseGroupMember entity has been created, the new entity should be posted to the relative URL: "/StudentService/coursegroupmember" (HTTP-POST) If an existing CourseGroupMember entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/coursegroupmember/{id}" (HTTP-PUT) If an existing CourseGroupMember entity has to be deleted, the following relative URL should be called: "/StudentService/coursegroupmember/{id}" (HTTP-DELETE) 8. The EventTaskView must contain the following fields: - name: Details type: STRING - name: ExternalPerson type: ExternalPerson - name: SchoolEvent type: SchoolEvent - name: Student type: Student - name: TaskTitle type: STRING - name: Teacher type: Teacher The data source for the [ExternalPerson] select control should be loaded from the relative URL: "/ExternalPersonService/externalperson" (HTTP-GET) The data source for the [SchoolEvent] select control should be loaded from the relative URL: "/StudentService/schoolevent" (HTTP-GET) The data source for the [Teacher] select control should be loaded from the relative URL: "/StudentService/teacher" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing EventTask entity should be loaded from the relative URL: "/StudentService/eventtask/{id}" (HTTP-GET) If a new EventTask entity has been created, the new entity should be posted to the relative URL: "/StudentService/eventtask" (HTTP-POST) If an existing EventTask entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/eventtask/{id}" (HTTP-PUT) If an existing EventTask entity has to be deleted, the following relative URL should be called: "/StudentService/eventtask/{id}" (HTTP-DELETE) Add a HTML table to the view with the following EventTaskDependency columns: - column: Source - column: Destination The table should have the title "EventTaskDependencys" und the data must be loaded from the server with the following relative URL: "/StudentService/eventtaskdependency/destination/{id}" Add a HTML table to the view with the following EventTaskDependency columns: - column: Source - column: Destination The table should have the title "EventTaskDependencys" und the data must be loaded from the server with the following relative URL: "/StudentService/eventtaskdependency/source/{id}" 9. The EventTaskDependencyView must contain the following fields: - name: Source type: EventTask - name: Destination type: EventTask The data source for the [Destination] select control should be loaded from the relative URL: "/StudentService/eventtask" (HTTP-GET) The data source for the [Source] select control should be loaded from the relative URL: "/StudentService/eventtask" (HTTP-GET) An existing EventTaskDependency entity should be loaded from the relative URL: "/StudentService/eventtaskdependency/{id}" (HTTP-GET) If a new EventTaskDependency entity has been created, the new entity should be posted to the relative URL: "/StudentService/eventtaskdependency" (HTTP-POST) If an existing EventTaskDependency entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/eventtaskdependency/{id}" (HTTP-PUT) If an existing EventTaskDependency entity has to be deleted, the following relative URL should be called: "/StudentService/eventtaskdependency/{id}" (HTTP-DELETE) 10. The GenderView must contain the following fields: - name: GenderName type: STRING An existing Gender entity should be loaded from the relative URL: "/StudentService/gender/{id}" (HTTP-GET) If a new Gender entity has been created, the new entity should be posted to the relative URL: "/StudentService/gender" (HTTP-POST) If an existing Gender entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/gender/{id}" (HTTP-PUT) If an existing Gender entity has to be deleted, the following relative URL should be called: "/StudentService/gender/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Student columns: - column: Gender - column: DateOfBirth - column: FirstName - column: City - column: ChosenSchoolType - column: Religion - column: PostalCode - column: CellPhoneNo - column: RecommendedSchoolType - column: ReadWriteAtony - column: CityOfBirth - column: ReligionTeaching - column: HealthInsurance - column: Email - column: Street - column: StudentInfo - column: LastName - column: SwimmingInsignia - column: PhoneNo The table should have the title "Students" und the data must be loaded from the server with the following relative URL: "/StudentService/student/gender/{id}" 11. The MigrationBackgroundView must contain the following fields: - name: History type: STRING - name: ShortText type: STRING - name: Student type: Student The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing MigrationBackground entity should be loaded from the relative URL: "/StudentService/migrationbackground/{id}" (HTTP-GET) If a new MigrationBackground entity has been created, the new entity should be posted to the relative URL: "/StudentService/migrationbackground" (HTTP-POST) If an existing MigrationBackground entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/migrationbackground/{id}" (HTTP-PUT) If an existing MigrationBackground entity has to be deleted, the following relative URL should be called: "/StudentService/migrationbackground/{id}" (HTTP-DELETE) 12. The NurseryView must contain the following fields: - name: Email type: STRING - name: NurseryInfo type: STRING - name: NurseryName type: STRING - name: PostalCode type: STRING - name: City type: STRING - name: Street type: STRING - name: PhoneNo type: STRING An existing Nursery entity should be loaded from the relative URL: "/StudentService/nursery/{id}" (HTTP-GET) If a new Nursery entity has been created, the new entity should be posted to the relative URL: "/StudentService/nursery" (HTTP-POST) If an existing Nursery entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/nursery/{id}" (HTTP-PUT) If an existing Nursery entity has to be deleted, the following relative URL should be called: "/StudentService/nursery/{id}" (HTTP-DELETE) Add a HTML table to the view with the following VitaEntry columns: - column: School - column: Student - column: Nursery - column: Company - column: FromDate - column: ToDate - column: Details The table should have the title "VitaEntrys" und the data must be loaded from the server with the following relative URL: "/StudentService/vitaentry/nursery/{id}" 13. The OfficeAgentView must contain the following fields: - name: AdministrativeOffice type: AdministrativeOffice - name: Teacher type: Teacher The data source for the [Teacher] select control should be loaded from the relative URL: "/StudentService/teacher" (HTTP-GET) The data source for the [AdministrativeOffice] select control should be loaded from the relative URL: "/StudentService/administrativeoffice" (HTTP-GET) An existing OfficeAgent entity should be loaded from the relative URL: "/StudentService/officeagent/{id}" (HTTP-GET) If a new OfficeAgent entity has been created, the new entity should be posted to the relative URL: "/StudentService/officeagent" (HTTP-POST) If an existing OfficeAgent entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/officeagent/{id}" (HTTP-PUT) If an existing OfficeAgent entity has to be deleted, the following relative URL should be called: "/StudentService/officeagent/{id}" (HTTP-DELETE) 14. The ProjectView must contain the following fields: - name: ProjectDescription type: STRING - name: ProjectTitle type: STRING - name: ProjectWeek type: ProjectWeek The data source for the [ProjectWeek] select control should be loaded from the relative URL: "/SchoolService/projectweek" (HTTP-GET) An existing Project entity should be loaded from the relative URL: "/StudentService/project/{id}" (HTTP-GET) If a new Project entity has been created, the new entity should be posted to the relative URL: "/StudentService/project" (HTTP-POST) If an existing Project entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/project/{id}" (HTTP-PUT) If an existing Project entity has to be deleted, the following relative URL should be called: "/StudentService/project/{id}" (HTTP-DELETE) Add a HTML table to the view with the following ProjectAppointment columns: - column: Content - column: ToDate - column: Room - column: FromDate - column: Project - column: Description - column: ProjectOrganizer The table should have the title "ProjectAppointments" und the data must be loaded from the server with the following relative URL: "/StudentService/projectappointment/project/{id}" Add a HTML table to the view with the following ProjectAttendee columns: - column: Project - column: Student The table should have the title "ProjectAttendees" und the data must be loaded from the server with the following relative URL: "/StudentService/projectattendee/project/{id}" Add a HTML table to the view with the following ProjectOrganizer columns: - column: ExternalPerson - column: Teacher - column: Project The table should have the title "ProjectOrganizers" und the data must be loaded from the server with the following relative URL: "/StudentService/projectorganizer/project/{id}" 15. The ProjectAppointmentView must contain the following fields: - name: FromDate type: DATE - name: Description type: STRING - name: ToDate type: DATE - name: Content type: STRING - name: ProjectOrganizer type: ProjectOrganizer - name: Project type: Project - name: Room type: Room The data source for the [Project] select control should be loaded from the relative URL: "/StudentService/project" (HTTP-GET) The data source for the [ProjectOrganizer] select control should be loaded from the relative URL: "/StudentService/projectorganizer" (HTTP-GET) The data source for the [Room] select control should be loaded from the relative URL: "/RoomService/room" (HTTP-GET) An existing ProjectAppointment entity should be loaded from the relative URL: "/StudentService/projectappointment/{id}" (HTTP-GET) If a new ProjectAppointment entity has been created, the new entity should be posted to the relative URL: "/StudentService/projectappointment" (HTTP-POST) If an existing ProjectAppointment entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/projectappointment/{id}" (HTTP-PUT) If an existing ProjectAppointment entity has to be deleted, the following relative URL should be called: "/StudentService/projectappointment/{id}" (HTTP-DELETE) 16. The ProjectAttendeeView must contain the following fields: - name: Project type: Project - name: Student type: Student The data source for the [Project] select control should be loaded from the relative URL: "/StudentService/project" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing ProjectAttendee entity should be loaded from the relative URL: "/StudentService/projectattendee/{id}" (HTTP-GET) If a new ProjectAttendee entity has been created, the new entity should be posted to the relative URL: "/StudentService/projectattendee" (HTTP-POST) If an existing ProjectAttendee entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/projectattendee/{id}" (HTTP-PUT) If an existing ProjectAttendee entity has to be deleted, the following relative URL should be called: "/StudentService/projectattendee/{id}" (HTTP-DELETE) 17. The ProjectOrganizerView must contain the following fields: - name: ExternalPerson type: ExternalPerson - name: Teacher type: Teacher - name: Project type: Project The data source for the [Project] select control should be loaded from the relative URL: "/StudentService/project" (HTTP-GET) The data source for the [ExternalPerson] select control should be loaded from the relative URL: "/ExternalPersonService/externalperson" (HTTP-GET) The data source for the [Teacher] select control should be loaded from the relative URL: "/StudentService/teacher" (HTTP-GET) An existing ProjectOrganizer entity should be loaded from the relative URL: "/StudentService/projectorganizer/{id}" (HTTP-GET) If a new ProjectOrganizer entity has been created, the new entity should be posted to the relative URL: "/StudentService/projectorganizer" (HTTP-POST) If an existing ProjectOrganizer entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/projectorganizer/{id}" (HTTP-PUT) If an existing ProjectOrganizer entity has to be deleted, the following relative URL should be called: "/StudentService/projectorganizer/{id}" (HTTP-DELETE) Add a HTML table to the view with the following ProjectAppointment columns: - column: Content - column: ToDate - column: Room - column: FromDate - column: Project - column: Description - column: ProjectOrganizer The table should have the title "ProjectAppointments" und the data must be loaded from the server with the following relative URL: "/StudentService/projectappointment/projectorganizer/{id}" 18. The ReligionView must contain the following fields: - name: ReligionName type: STRING An existing Religion entity should be loaded from the relative URL: "/StudentService/religion/{id}" (HTTP-GET) If a new Religion entity has been created, the new entity should be posted to the relative URL: "/StudentService/religion" (HTTP-POST) If an existing Religion entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/religion/{id}" (HTTP-PUT) If an existing Religion entity has to be deleted, the following relative URL should be called: "/StudentService/religion/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Student columns: - column: Gender - column: DateOfBirth - column: FirstName - column: City - column: ChosenSchoolType - column: Religion - column: PostalCode - column: CellPhoneNo - column: RecommendedSchoolType - column: ReadWriteAtony - column: CityOfBirth - column: ReligionTeaching - column: HealthInsurance - column: Email - column: Street - column: StudentInfo - column: LastName - column: SwimmingInsignia - column: PhoneNo The table should have the title "Students" und the data must be loaded from the server with the following relative URL: "/StudentService/student/religionteaching/{id}" Add a HTML table to the view with the following Student columns: - column: Gender - column: DateOfBirth - column: FirstName - column: City - column: ChosenSchoolType - column: Religion - column: PostalCode - column: CellPhoneNo - column: RecommendedSchoolType - column: ReadWriteAtony - column: CityOfBirth - column: ReligionTeaching - column: HealthInsurance - column: Email - column: Street - column: StudentInfo - column: LastName - column: SwimmingInsignia - column: PhoneNo The table should have the title "Students" und the data must be loaded from the server with the following relative URL: "/StudentService/student/religion/{id}" 19. The ReportTypeView must contain the following fields: - name: Description type: STRING - name: TypeName type: STRING An existing ReportType entity should be loaded from the relative URL: "/StudentService/reporttype/{id}" (HTTP-GET) If a new ReportType entity has been created, the new entity should be posted to the relative URL: "/StudentService/reporttype" (HTTP-POST) If an existing ReportType entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/reporttype/{id}" (HTTP-PUT) If an existing ReportType entity has to be deleted, the following relative URL should be called: "/StudentService/reporttype/{id}" (HTTP-DELETE) Add a HTML table to the view with the following SchoolEvent columns: - column: FromDate - column: SchoolEventType - column: ToDate - column: Description - column: ReportType - column: ShortTitle The table should have the title "SchoolEvents" und the data must be loaded from the server with the following relative URL: "/StudentService/schoolevent/reporttype/{id}" 20. The SchoolBreakView must contain the following fields: - name: BreakName type: STRING - name: ToTime type: DATE - name: FromTime type: DATE An existing SchoolBreak entity should be loaded from the relative URL: "/StudentService/schoolbreak/{id}" (HTTP-GET) If a new SchoolBreak entity has been created, the new entity should be posted to the relative URL: "/StudentService/schoolbreak" (HTTP-POST) If an existing SchoolBreak entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/schoolbreak/{id}" (HTTP-PUT) If an existing SchoolBreak entity has to be deleted, the following relative URL should be called: "/StudentService/schoolbreak/{id}" (HTTP-DELETE) Add a HTML table to the view with the following BreakPlanEntry columns: - column: EntryDate - column: Teacher - column: BreakPlan - column: SchoolBreak The table should have the title "BreakPlanEntrys" und the data must be loaded from the server with the following relative URL: "/StudentService/breakplanentry/schoolbreak/{id}" 21. The SchoolEventView must contain the following fields: - name: FromDate type: DATE - name: ReportType type: ReportType - name: Description type: STRING - name: ToDate type: DATE - name: ShortTitle type: STRING - name: SchoolEventType type: SchoolEventType The data source for the [SchoolEventType] select control should be loaded from the relative URL: "/StudentService/schooleventtype" (HTTP-GET) The data source for the [ReportType] select control should be loaded from the relative URL: "/StudentService/reporttype" (HTTP-GET) An existing SchoolEvent entity should be loaded from the relative URL: "/StudentService/schoolevent/{id}" (HTTP-GET) If a new SchoolEvent entity has been created, the new entity should be posted to the relative URL: "/StudentService/schoolevent" (HTTP-POST) If an existing SchoolEvent entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/schoolevent/{id}" (HTTP-PUT) If an existing SchoolEvent entity has to be deleted, the following relative URL should be called: "/StudentService/schoolevent/{id}" (HTTP-DELETE) Add a HTML table to the view with the following SchoolEventAttendee columns: - column: Teacher - column: ExternalPerson - column: InvitationShipped - column: Student - column: SchoolEvent - column: Invitation The table should have the title "SchoolEventAttendees" und the data must be loaded from the server with the following relative URL: "/StudentService/schooleventattendee/schoolevent/{id}" Add a HTML table to the view with the following Contribution columns: - column: Student - column: PaymentDetails - column: Amount - column: SchoolEvent - column: SchoolTrip The table should have the title "Contributions" und the data must be loaded from the server with the following relative URL: "/StudentService/contribution/schoolevent/{id}" Add a HTML table to the view with the following EventTask columns: - column: TaskTitle - column: ExternalPerson - column: Teacher - column: Details - column: SchoolEvent - column: Student The table should have the title "EventTasks" und the data must be loaded from the server with the following relative URL: "/StudentService/eventtask/schoolevent/{id}" 22. The SchoolEventAttendeeView must contain the following fields: - name: Invitation type: BOOL - name: InvitationShipped type: BOOL - name: ExternalPerson type: ExternalPerson - name: Teacher type: Teacher - name: SchoolEvent type: SchoolEvent - name: Student type: Student The data source for the [ExternalPerson] select control should be loaded from the relative URL: "/ExternalPersonService/externalperson" (HTTP-GET) The data source for the [Teacher] select control should be loaded from the relative URL: "/StudentService/teacher" (HTTP-GET) The data source for the [SchoolEvent] select control should be loaded from the relative URL: "/StudentService/schoolevent" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing SchoolEventAttendee entity should be loaded from the relative URL: "/StudentService/schooleventattendee/{id}" (HTTP-GET) If a new SchoolEventAttendee entity has been created, the new entity should be posted to the relative URL: "/StudentService/schooleventattendee" (HTTP-POST) If an existing SchoolEventAttendee entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/schooleventattendee/{id}" (HTTP-PUT) If an existing SchoolEventAttendee entity has to be deleted, the following relative URL should be called: "/StudentService/schooleventattendee/{id}" (HTTP-DELETE) 23. The SchoolEventTypeView must contain the following fields: - name: EventTypeName type: STRING An existing SchoolEventType entity should be loaded from the relative URL: "/StudentService/schooleventtype/{id}" (HTTP-GET) If a new SchoolEventType entity has been created, the new entity should be posted to the relative URL: "/StudentService/schooleventtype" (HTTP-POST) If an existing SchoolEventType entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/schooleventtype/{id}" (HTTP-PUT) If an existing SchoolEventType entity has to be deleted, the following relative URL should be called: "/StudentService/schooleventtype/{id}" (HTTP-DELETE) Add a HTML table to the view with the following SchoolEvent columns: - column: FromDate - column: SchoolEventType - column: ToDate - column: Description - column: ReportType - column: ShortTitle The table should have the title "SchoolEvents" und the data must be loaded from the server with the following relative URL: "/StudentService/schoolevent/schooleventtype/{id}" 24. The StudentView must contain the following fields: - name: Email type: STRING - name: RecommendedSchoolType type: SchoolType - name: CityOfBirth type: STRING - name: DateOfBirth type: DATE - name: Gender type: Gender - name: ChosenSchoolType type: SchoolType - name: StudentInfo type: STRING - name: HealthInsurance type: HealthInsurance - name: ReadWriteAtony type: BOOL - name: CellPhoneNo type: STRING - name: LastName type: STRING - name: PostalCode type: STRING - name: ReligionTeaching type: Religion - name: Religion type: Religion - name: SwimmingInsignia type: SwimmingInsignia - name: City type: STRING - name: Street type: STRING - name: PhoneNo type: STRING - name: FirstName type: STRING The data source for the [RecommendedSchoolType] select control should be loaded from the relative URL: "/SchoolService/schooltype" (HTTP-GET) The data source for the [Religion] select control should be loaded from the relative URL: "/StudentService/religion" (HTTP-GET) The data source for the [ChosenSchoolType] select control should be loaded from the relative URL: "/SchoolService/schooltype" (HTTP-GET) The data source for the [Gender] select control should be loaded from the relative URL: "/StudentService/gender" (HTTP-GET) The data source for the [SwimmingInsignia] select control should be loaded from the relative URL: "/StudentService/swimminginsignia" (HTTP-GET) The data source for the [HealthInsurance] select control should be loaded from the relative URL: "/CompanyService/healthinsurance" (HTTP-GET) The data source for the [ReligionTeaching] select control should be loaded from the relative URL: "/StudentService/religion" (HTTP-GET) An existing Student entity should be loaded from the relative URL: "/StudentService/student/{id}" (HTTP-GET) If a new Student entity has been created, the new entity should be posted to the relative URL: "/StudentService/student" (HTTP-POST) If an existing Student entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/student/{id}" (HTTP-PUT) If an existing Student entity has to be deleted, the following relative URL should be called: "/StudentService/student/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Accident columns: - column: Description - column: AccidentDate - column: Student The table should have the title "Accidents" und the data must be loaded from the server with the following relative URL: "/StudentService/accident/student/{id}" Add a HTML table to the view with the following EducationCoupon columns: - column: ToDate - column: Amount - column: FromDate - column: Student The table should have the title "EducationCoupons" und the data must be loaded from the server with the following relative URL: "/EducationCouponService/educationcoupon/student/{id}" Add a HTML table to the view with the following HomeWork columns: - column: Schoolsubject - column: WorkDate - column: Description - column: DeadLine - column: Grade - column: SchoolClass - column: Done - column: Subject - column: Student The table should have the title "HomeWorks" und the data must be loaded from the server with the following relative URL: "/SchoolSubjectService/homework/student/{id}" Add a HTML table to the view with the following TestResult columns: - column: Test - column: Grade - column: Student The table should have the title "TestResults" und the data must be loaded from the server with the following relative URL: "/StudentService/testresult/student/{id}" Add a HTML table to the view with the following StudentContact columns: - column: ExternalPerson - column: Student The table should have the title "StudentContacts" und the data must be loaded from the server with the following relative URL: "/ExternalPersonService/studentcontact/student/{id}" Add a HTML table to the view with the following MigrationBackground columns: - column: History - column: Student - column: ShortText The table should have the title "MigrationBackgrounds" und the data must be loaded from the server with the following relative URL: "/StudentService/migrationbackground/student/{id}" Add a HTML table to the view with the following VitaEntry columns: - column: School - column: Student - column: Nursery - column: Company - column: FromDate - column: ToDate - column: Details The table should have the title "VitaEntrys" und the data must be loaded from the server with the following relative URL: "/StudentService/vitaentry/student/{id}" Add a HTML table to the view with the following StudentMaterial columns: - column: Comments - column: Amount - column: ConsumableMaterial - column: DesignatedUse - column: Costs - column: Student - column: Paid The table should have the title "StudentMaterials" und the data must be loaded from the server with the following relative URL: "/StudentService/studentmaterial/student/{id}" Add a HTML table to the view with the following EventTask columns: - column: TaskTitle - column: ExternalPerson - column: Teacher - column: Details - column: SchoolEvent - column: Student The table should have the title "EventTasks" und the data must be loaded from the server with the following relative URL: "/StudentService/eventtask/student/{id}" Add a HTML table to the view with the following StudentTransport columns: - column: Transport - column: Details - column: Student The table should have the title "StudentTransports" und the data must be loaded from the server with the following relative URL: "/StudentService/studenttransport/student/{id}" Add a HTML table to the view with the following SchoolEventAttendee columns: - column: Teacher - column: ExternalPerson - column: InvitationShipped - column: Student - column: SchoolEvent - column: Invitation The table should have the title "SchoolEventAttendees" und the data must be loaded from the server with the following relative URL: "/StudentService/schooleventattendee/student/{id}" Add a HTML table to the view with the following Nationality columns: - column: Country - column: Student The table should have the title "Nationalitys" und the data must be loaded from the server with the following relative URL: "/CountryService/nationality/student/{id}" Add a HTML table to the view with the following ConferenceAttendee columns: - column: Teacher - column: ExternalPerson - column: Conference - column: Student The table should have the title "ConferenceAttendees" und the data must be loaded from the server with the following relative URL: "/StudentService/conferenceattendee/student/{id}" Add a HTML table to the view with the following CourseGroupMember columns: - column: Student - column: CourseGroup The table should have the title "CourseGroupMembers" und the data must be loaded from the server with the following relative URL: "/StudentService/coursegroupmember/student/{id}" Add a HTML table to the view with the following Contribution columns: - column: Student - column: PaymentDetails - column: Amount - column: SchoolEvent - column: SchoolTrip The table should have the title "Contributions" und the data must be loaded from the server with the following relative URL: "/StudentService/contribution/student/{id}" Add a HTML table to the view with the following BookRental columns: - column: Student - column: Library - column: FromDate - column: Teacher - column: ReservationDate - column: Book - column: ToDate The table should have the title "BookRentals" und the data must be loaded from the server with the following relative URL: "/LibraryService/bookrental/student/{id}" Add a HTML table to the view with the following SchoolClassStudent columns: - column: Student - column: SchoolClass The table should have the title "SchoolClassStudents" und the data must be loaded from the server with the following relative URL: "/SchoolClassStudentService/schoolclassstudent/student/{id}" Add a HTML table to the view with the following ProjectAttendee columns: - column: Project - column: Student The table should have the title "ProjectAttendees" und the data must be loaded from the server with the following relative URL: "/StudentService/projectattendee/student/{id}" Add a HTML table to the view with the following StudentRepresentation columns: - column: Student - column: School - column: SchoolClass The table should have the title "StudentRepresentations" und the data must be loaded from the server with the following relative URL: "/StudentService/studentrepresentation/student/{id}" Add a HTML table to the view with the following FoodOrder columns: - column: FoodOrderDate - column: Teacher - column: Food - column: ExternalPerson - column: Student The table should have the title "FoodOrders" und the data must be loaded from the server with the following relative URL: "/FoodService/foodorder/student/{id}" 25. The StudentMaterialView must contain the following fields: - name: Paid type: BOOL - name: Comments type: STRING - name: Costs type: DOUBLE - name: Amount type: DOUBLE - name: Student type: Student - name: ConsumableMaterial type: ConsumableMaterial - name: DesignatedUse type: STRING The data source for the [ConsumableMaterial] select control should be loaded from the relative URL: "/StudentService/consumablematerial" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing StudentMaterial entity should be loaded from the relative URL: "/StudentService/studentmaterial/{id}" (HTTP-GET) If a new StudentMaterial entity has been created, the new entity should be posted to the relative URL: "/StudentService/studentmaterial" (HTTP-POST) If an existing StudentMaterial entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/studentmaterial/{id}" (HTTP-PUT) If an existing StudentMaterial entity has to be deleted, the following relative URL should be called: "/StudentService/studentmaterial/{id}" (HTTP-DELETE) 26. The StudentRepresentationView must contain the following fields: - name: SchoolClass type: SchoolClass - name: School type: School - name: Student type: Student The data source for the [School] select control should be loaded from the relative URL: "/SchoolService/school" (HTTP-GET) The data source for the [SchoolClass] select control should be loaded from the relative URL: "/SchoolYearService/schoolclass" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing StudentRepresentation entity should be loaded from the relative URL: "/StudentService/studentrepresentation/{id}" (HTTP-GET) If a new StudentRepresentation entity has been created, the new entity should be posted to the relative URL: "/StudentService/studentrepresentation" (HTTP-POST) If an existing StudentRepresentation entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/studentrepresentation/{id}" (HTTP-PUT) If an existing StudentRepresentation entity has to be deleted, the following relative URL should be called: "/StudentService/studentrepresentation/{id}" (HTTP-DELETE) 27. The StudentTransportView must contain the following fields: - name: Transport type: STRING - name: Details type: STRING - name: Student type: Student The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing StudentTransport entity should be loaded from the relative URL: "/StudentService/studenttransport/{id}" (HTTP-GET) If a new StudentTransport entity has been created, the new entity should be posted to the relative URL: "/StudentService/studenttransport" (HTTP-POST) If an existing StudentTransport entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/studenttransport/{id}" (HTTP-PUT) If an existing StudentTransport entity has to be deleted, the following relative URL should be called: "/StudentService/studenttransport/{id}" (HTTP-DELETE) 28. The SwimmingInsigniaView must contain the following fields: - name: InsigniaName type: STRING - name: Description type: STRING An existing SwimmingInsignia entity should be loaded from the relative URL: "/StudentService/swimminginsignia/{id}" (HTTP-GET) If a new SwimmingInsignia entity has been created, the new entity should be posted to the relative URL: "/StudentService/swimminginsignia" (HTTP-POST) If an existing SwimmingInsignia entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/swimminginsignia/{id}" (HTTP-PUT) If an existing SwimmingInsignia entity has to be deleted, the following relative URL should be called: "/StudentService/swimminginsignia/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Student columns: - column: Gender - column: DateOfBirth - column: FirstName - column: City - column: ChosenSchoolType - column: Religion - column: PostalCode - column: CellPhoneNo - column: RecommendedSchoolType - column: ReadWriteAtony - column: CityOfBirth - column: ReligionTeaching - column: HealthInsurance - column: Email - column: Street - column: StudentInfo - column: LastName - column: SwimmingInsignia - column: PhoneNo The table should have the title "Students" und the data must be loaded from the server with the following relative URL: "/StudentService/student/swimminginsignia/{id}" 29. The TeacherView must contain the following fields: - name: Email type: STRING - name: FaxNo type: STRING - name: TeacherInfo type: STRING - name: CellPhoneNo type: STRING - name: LastName type: STRING - name: PostalCode type: STRING - name: City type: STRING - name: Street type: STRING - name: PhoneNo type: STRING - name: FirstName type: STRING An existing Teacher entity should be loaded from the relative URL: "/StudentService/teacher/{id}" (HTTP-GET) If a new Teacher entity has been created, the new entity should be posted to the relative URL: "/StudentService/teacher" (HTTP-POST) If an existing Teacher entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/teacher/{id}" (HTTP-PUT) If an existing Teacher entity has to be deleted, the following relative URL should be called: "/StudentService/teacher/{id}" (HTTP-DELETE) Add a HTML table to the view with the following TeacherBoardMember columns: - column: Teacher - column: TeacherBoard The table should have the title "TeacherBoardMembers" und the data must be loaded from the server with the following relative URL: "/StudentService/teacherboardmember/teacher/{id}" Add a HTML table to the view with the following EventTask columns: - column: TaskTitle - column: ExternalPerson - column: Teacher - column: Details - column: SchoolEvent - column: Student The table should have the title "EventTasks" und the data must be loaded from the server with the following relative URL: "/StudentService/eventtask/teacher/{id}" Add a HTML table to the view with the following TeachingUnit columns: - column: RowIndex - column: SchoolSubject - column: Room - column: SchoolYear - column: CourseGroup - column: SchoolClass - column: ColumnIndex - column: Teacher The table should have the title "TeachingUnits" und the data must be loaded from the server with the following relative URL: "/SchoolYearService/teachingunit/teacher/{id}" Add a HTML table to the view with the following SchoolEventAttendee columns: - column: Teacher - column: ExternalPerson - column: InvitationShipped - column: Student - column: SchoolEvent - column: Invitation The table should have the title "SchoolEventAttendees" und the data must be loaded from the server with the following relative URL: "/StudentService/schooleventattendee/teacher/{id}" Add a HTML table to the view with the following ConferenceAttendee columns: - column: Teacher - column: ExternalPerson - column: Conference - column: Student The table should have the title "ConferenceAttendees" und the data must be loaded from the server with the following relative URL: "/StudentService/conferenceattendee/teacher/{id}" Add a HTML table to the view with the following TeacherLesson columns: - column: SchoolYear - column: LessonCount - column: Teacher The table should have the title "TeacherLessons" und the data must be loaded from the server with the following relative URL: "/SchoolYearService/teacherlesson/teacher/{id}" Add a HTML table to the view with the following OfficeAgent columns: - column: Teacher - column: AdministrativeOffice The table should have the title "OfficeAgents" und the data must be loaded from the server with the following relative URL: "/StudentService/officeagent/teacher/{id}" Add a HTML table to the view with the following PurchaseList columns: - column: PurchaseDate - column: Buyer - column: Distributor - column: BuyingTeacher The table should have the title "PurchaseLists" und the data must be loaded from the server with the following relative URL: "/PurchaseListService/purchaselist/buyingteacher/{id}" Add a HTML table to the view with the following BudgetPosition columns: - column: PositionAgent - column: Budget - column: ShortName - column: Target - column: PositionID The table should have the title "BudgetPositions" und the data must be loaded from the server with the following relative URL: "/ProductService/budgetposition/positionagent/{id}" Add a HTML table to the view with the following Lesson columns: - column: Teacher - column: SchoolSubject - column: LessonContent - column: SchoolClass - column: LessonDate The table should have the title "Lessons" und the data must be loaded from the server with the following relative URL: "/LessonService/lesson/teacher/{id}" Add a HTML table to the view with the following BookRental columns: - column: Student - column: Library - column: FromDate - column: Teacher - column: ReservationDate - column: Book - column: ToDate The table should have the title "BookRentals" und the data must be loaded from the server with the following relative URL: "/LibraryService/bookrental/teacher/{id}" Add a HTML table to the view with the following ProjectOrganizer columns: - column: ExternalPerson - column: Teacher - column: Project The table should have the title "ProjectOrganizers" und the data must be loaded from the server with the following relative URL: "/StudentService/projectorganizer/teacher/{id}" Add a HTML table to the view with the following SchoolClass columns: - column: Teacher - column: AgeGroup - column: Room - column: SchoolYear - column: ClassName - column: School The table should have the title "SchoolClasss" und the data must be loaded from the server with the following relative URL: "/SchoolYearService/schoolclass/teacher/{id}" Add a HTML table to the view with the following FoodOrder columns: - column: FoodOrderDate - column: Teacher - column: Food - column: ExternalPerson - column: Student The table should have the title "FoodOrders" und the data must be loaded from the server with the following relative URL: "/FoodService/foodorder/teacher/{id}" Add a HTML table to the view with the following BreakPlanEntry columns: - column: EntryDate - column: Teacher - column: BreakPlan - column: SchoolBreak The table should have the title "BreakPlanEntrys" und the data must be loaded from the server with the following relative URL: "/StudentService/breakplanentry/teacher/{id}" 30. The TeacherBoardMemberView must contain the following fields: - name: Teacher type: Teacher - name: TeacherBoard type: TeacherBoard The data source for the [Teacher] select control should be loaded from the relative URL: "/StudentService/teacher" (HTTP-GET) The data source for the [TeacherBoard] select control should be loaded from the relative URL: "/SchoolYearService/teacherboard" (HTTP-GET) An existing TeacherBoardMember entity should be loaded from the relative URL: "/StudentService/teacherboardmember/{id}" (HTTP-GET) If a new TeacherBoardMember entity has been created, the new entity should be posted to the relative URL: "/StudentService/teacherboardmember" (HTTP-POST) If an existing TeacherBoardMember entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/teacherboardmember/{id}" (HTTP-PUT) If an existing TeacherBoardMember entity has to be deleted, the following relative URL should be called: "/StudentService/teacherboardmember/{id}" (HTTP-DELETE) 31. The TestResultView must contain the following fields: - name: Grade type: INT - name: Student type: Student - name: Test type: Test The data source for the [Test] select control should be loaded from the relative URL: "/SchoolSubjectClassService/test" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) An existing TestResult entity should be loaded from the relative URL: "/StudentService/testresult/{id}" (HTTP-GET) If a new TestResult entity has been created, the new entity should be posted to the relative URL: "/StudentService/testresult" (HTTP-POST) If an existing TestResult entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/testresult/{id}" (HTTP-PUT) If an existing TestResult entity has to be deleted, the following relative URL should be called: "/StudentService/testresult/{id}" (HTTP-DELETE) 32. The VitaEntryView must contain the following fields: - name: School type: School - name: ToDate type: DATE - name: Details type: STRING - name: Company type: Company - name: Nursery type: Nursery - name: Student type: Student - name: FromDate type: DATE The data source for the [School] select control should be loaded from the relative URL: "/SchoolService/school" (HTTP-GET) The data source for the [Company] select control should be loaded from the relative URL: "/CompanyService/company" (HTTP-GET) The data source for the [Student] select control should be loaded from the relative URL: "/StudentService/student" (HTTP-GET) The data source for the [Nursery] select control should be loaded from the relative URL: "/StudentService/nursery" (HTTP-GET) An existing VitaEntry entity should be loaded from the relative URL: "/StudentService/vitaentry/{id}" (HTTP-GET) If a new VitaEntry entity has been created, the new entity should be posted to the relative URL: "/StudentService/vitaentry" (HTTP-POST) If an existing VitaEntry entity has been updated, the modified entity should be sent to the relative URL: "/StudentService/vitaentry/{id}" (HTTP-PUT) If an existing VitaEntry entity has to be deleted, the following relative URL should be called: "/StudentService/vitaentry/{id}" (HTTP-DELETE)
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum