Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum
Prompt for the
RechnungApp
Please create a React-JS application for the RechnungModule. The application has to offer the following views for the user interface: 1. DatenschutzMerkmalView 2. RechnungView 3. RechnungspositionView 4. UmweltstudieView 5. ZahlungView The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below. 1. The DatenschutzMerkmalView must contain the following fields: - name: Anonymisierung type: BOOL - name: Aufbewahrungstage type: LONG - name: Beschreibung type: STRING - name: CarsharingOrganisation type: CarsharingOrganisation - name: Standortdaten type: BOOL The data source for the [CarsharingOrganisation] select control should be loaded from the relative URL: "/CarsharingOrganisationService/carsharingorganisation" (HTTP-GET) An existing DatenschutzMerkmal entity should be loaded from the relative URL: "/RechnungService/datenschutzmerkmal/{id}" (HTTP-GET) If a new DatenschutzMerkmal entity has been created, the new entity should be posted to the relative URL: "/RechnungService/datenschutzmerkmal" (HTTP-POST) If an existing DatenschutzMerkmal entity has been updated, the modified entity should be sent to the relative URL: "/RechnungService/datenschutzmerkmal/{id}" (HTTP-PUT) If an existing DatenschutzMerkmal entity has to be deleted, the following relative URL should be called: "/RechnungService/datenschutzmerkmal/{id}" (HTTP-DELETE) 2. The RechnungView must contain the following fields: - name: AusgestelltAm type: DATE - name: CarsharingOrganisation type: CarsharingOrganisation - name: Gesamtbetrag type: STRING - name: Nutzer type: Nutzer - name: Rechnungsnummer type: STRING - name: Status type: STRING - name: ZeitraumEnde type: DATE - name: ZeitraumStart type: DATE The data source for the [CarsharingOrganisation] select control should be loaded from the relative URL: "/CarsharingOrganisationService/carsharingorganisation" (HTTP-GET) The data source for the [Nutzer] select control should be loaded from the relative URL: "/LandService/nutzer" (HTTP-GET) An existing Rechnung entity should be loaded from the relative URL: "/RechnungService/rechnung/{id}" (HTTP-GET) If a new Rechnung entity has been created, the new entity should be posted to the relative URL: "/RechnungService/rechnung" (HTTP-POST) If an existing Rechnung entity has been updated, the modified entity should be sent to the relative URL: "/RechnungService/rechnung/{id}" (HTTP-PUT) If an existing Rechnung entity has to be deleted, the following relative URL should be called: "/RechnungService/rechnung/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Rechnungsposition columns: - column: Rechnung - column: Beschreibung - column: Positionstyp - column: Referenztyp - column: Einzelpreis - column: Menge - column: Referenz - column: Gesamtbetrag The table should have the title "Rechnungspositions" und the data must be loaded from the server with the following relative URL: "/RechnungService/rechnungsposition/rechnung/{id}" Add a HTML table to the view with the following Zahlung columns: - column: BezahltAm - column: Transaktionsreferenz - column: Betrag - column: Zahlungsmethode - column: Rechnung - column: Status The table should have the title "Zahlungs" und the data must be loaded from the server with the following relative URL: "/RechnungService/zahlung/rechnung/{id}" 3. The RechnungspositionView must contain the following fields: - name: Beschreibung type: STRING - name: Einzelpreis type: STRING - name: Gesamtbetrag type: STRING - name: Menge type: STRING - name: Positionstyp type: STRING - name: Rechnung type: Rechnung - name: Referenz type: LONG - name: Referenztyp type: STRING The data source for the [Rechnung] select control should be loaded from the relative URL: "/RechnungService/rechnung" (HTTP-GET) An existing Rechnungsposition entity should be loaded from the relative URL: "/RechnungService/rechnungsposition/{id}" (HTTP-GET) If a new Rechnungsposition entity has been created, the new entity should be posted to the relative URL: "/RechnungService/rechnungsposition" (HTTP-POST) If an existing Rechnungsposition entity has been updated, the modified entity should be sent to the relative URL: "/RechnungService/rechnungsposition/{id}" (HTTP-PUT) If an existing Rechnungsposition entity has to be deleted, the following relative URL should be called: "/RechnungService/rechnungsposition/{id}" (HTTP-DELETE) 4. The UmweltstudieView must contain the following fields: - name: Anbieter type: STRING - name: Co2ProKm type: STRING - name: ErsetzteFahrzeuge type: STRING - name: Jahr type: LONG - name: Notizen type: STRING - name: PrivatCo2ProKm type: STRING - name: Stadt type: Stadt The data source for the [Stadt] select control should be loaded from the relative URL: "/CarsharingOrganisationService/stadt" (HTTP-GET) An existing Umweltstudie entity should be loaded from the relative URL: "/RechnungService/umweltstudie/{id}" (HTTP-GET) If a new Umweltstudie entity has been created, the new entity should be posted to the relative URL: "/RechnungService/umweltstudie" (HTTP-POST) If an existing Umweltstudie entity has been updated, the modified entity should be sent to the relative URL: "/RechnungService/umweltstudie/{id}" (HTTP-PUT) If an existing Umweltstudie entity has to be deleted, the following relative URL should be called: "/RechnungService/umweltstudie/{id}" (HTTP-DELETE) 5. The ZahlungView must contain the following fields: - name: Betrag type: STRING - name: BezahltAm type: DATE - name: Rechnung type: Rechnung - name: Status type: STRING - name: Transaktionsreferenz type: STRING - name: Zahlungsmethode type: Zahlungsmethode The data source for the [Zahlungsmethode] select control should be loaded from the relative URL: "/LandService/zahlungsmethode" (HTTP-GET) The data source for the [Rechnung] select control should be loaded from the relative URL: "/RechnungService/rechnung" (HTTP-GET) An existing Zahlung entity should be loaded from the relative URL: "/RechnungService/zahlung/{id}" (HTTP-GET) If a new Zahlung entity has been created, the new entity should be posted to the relative URL: "/RechnungService/zahlung" (HTTP-POST) If an existing Zahlung entity has been updated, the modified entity should be sent to the relative URL: "/RechnungService/zahlung/{id}" (HTTP-PUT) If an existing Zahlung entity has to be deleted, the following relative URL should be called: "/RechnungService/zahlung/{id}" (HTTP-DELETE)
Copy prompt
Overview
My API
System Designs
Dienstleistungen
Kontakt
Energieausgleich
Ansprechpartner
Impressum