Prompt for the HistorischePersonApp

Please create a React-JS application for the HistorischePersonModule. The application  has to offer the following views for the user interface: 
    1. AblaufSchrittView 
    2. EreignisPersonView 
    3. HistorischePersonView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The AblaufSchrittView must contain the following fields: 
    - name: Behandlung   type: Behandlung 
    - name: Beschreibung   type: STRING 
    - name: Reihenfolge   type: LONG 
The data source for the [Behandlung] select control should be loaded from the relative URL: 
    "/BehandlungService/behandlung"   (HTTP-GET) 
An existing AblaufSchritt entity should be loaded from the relative URL: 
    "/HistorischePersonService/ablaufschritt/{id}"   (HTTP-GET) 
If a new AblaufSchritt entity has been created, the new entity should be posted to the relative URL: 
    "/HistorischePersonService/ablaufschritt"   (HTTP-POST) 
If an existing AblaufSchritt entity has been updated, the modified entity should be sent to the relative URL: 
    "/HistorischePersonService/ablaufschritt/{id}"   (HTTP-PUT) 
If an existing AblaufSchritt entity has to be deleted, the following relative URL should be called: 
    "/HistorischePersonService/ablaufschritt/{id}"   (HTTP-DELETE)

2. The EreignisPersonView must contain the following fields: 
    - name: FussPflegeHistorieEreignis   type: FussPflegeHistorieEreignis 
    - name: HistorischePerson   type: HistorischePerson 
    - name: RollenBeschreibung   type: STRING 
The data source for the [HistorischePerson] select control should be loaded from the relative URL: 
    "/HistorischePersonService/historischeperson"   (HTTP-GET) 
The data source for the [FussPflegeHistorieEreignis] select control should be loaded from the relative URL: 
    "/LiteraturService/fusspflegehistorieereignis"   (HTTP-GET) 
An existing EreignisPerson entity should be loaded from the relative URL: 
    "/HistorischePersonService/ereignisperson/{id}"   (HTTP-GET) 
If a new EreignisPerson entity has been created, the new entity should be posted to the relative URL: 
    "/HistorischePersonService/ereignisperson"   (HTTP-POST) 
If an existing EreignisPerson entity has been updated, the modified entity should be sent to the relative URL: 
    "/HistorischePersonService/ereignisperson/{id}"   (HTTP-PUT) 
If an existing EreignisPerson entity has to be deleted, the following relative URL should be called: 
    "/HistorischePersonService/ereignisperson/{id}"   (HTTP-DELETE)

3. The HistorischePersonView must contain the following fields: 
    - name: Beschreibung   type: STRING 
    - name: GeburtsJahr   type: LONG 
    - name: Name   type: STRING 
    - name: TodesJahr   type: LONG 
An existing HistorischePerson entity should be loaded from the relative URL: 
    "/HistorischePersonService/historischeperson/{id}"   (HTTP-GET) 
If a new HistorischePerson entity has been created, the new entity should be posted to the relative URL: 
    "/HistorischePersonService/historischeperson"   (HTTP-POST) 
If an existing HistorischePerson entity has been updated, the modified entity should be sent to the relative URL: 
    "/HistorischePersonService/historischeperson/{id}"   (HTTP-PUT) 
If an existing HistorischePerson entity has to be deleted, the following relative URL should be called: 
    "/HistorischePersonService/historischeperson/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following EreignisPerson columns: 
    - column: FussPflegeHistorieEreignis 
    - column: HistorischePerson 
    - column: RollenBeschreibung 
The table should have the title "EreignisPersons" und the data must be loaded from the server with the following relative URL: 
    "/HistorischePersonService/ereignisperson/historischeperson/{id}"