Prompt for the VenueAreaApp

Please create a React-JS application for the VenueAreaModule. The application  has to offer the following views for the user interface: 
    1. AccessPointView 
    2. ConferenceRoomView 
    3. EventTicketTypeView 
    4. SeatBlockView 
    5. VenueAreaView 
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 AccessPointView must contain the following fields: 
    - name: AccessCode   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
An existing AccessPoint entity should be loaded from the relative URL: 
    "/VenueAreaService/accesspoint/{id}"   (HTTP-GET) 
If a new AccessPoint entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/accesspoint"   (HTTP-POST) 
If an existing AccessPoint entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/accesspoint/{id}"   (HTTP-PUT) 
If an existing AccessPoint entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/accesspoint/{id}"   (HTTP-DELETE)

2. The ConferenceRoomView must contain the following fields: 
    - name: Capacity   type: LONG 
    - name: Description   type: STRING 
    - name: Floor   type: STRING 
    - name: Name   type: STRING 
    - name: RoomNumber   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
An existing ConferenceRoom entity should be loaded from the relative URL: 
    "/VenueAreaService/conferenceroom/{id}"   (HTTP-GET) 
If a new ConferenceRoom entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/conferenceroom"   (HTTP-POST) 
If an existing ConferenceRoom entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/conferenceroom/{id}"   (HTTP-PUT) 
If an existing ConferenceRoom entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/conferenceroom/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ConferenceRoomEquipment columns: 
    - column: ConferenceRoom 
    - column: ConferenceEquipment 
    - column: Quantity 
The table should have the title "ConferenceRoomEquipments" und the data must be loaded from the server with the following relative URL: 
    "/OrganizerService/conferenceroomequipment/conferenceroom/{id}" 
Add a HTML table to the view with the following ConferenceBooking columns: 
    - column: Status 
    - column: Title 
    - column: StartDateTime 
    - column: ConferenceRoom 
    - column: Description 
    - column: AttendeeCount 
    - column: Customer 
    - column: CreatedAt 
    - column: EndDateTime 
The table should have the title "ConferenceBookings" und the data must be loaded from the server with the following relative URL: 
    "/CustomerService/conferencebooking/conferenceroom/{id}"

3. The EventTicketTypeView must contain the following fields: 
    - name: BasePrice   type: STRING 
    - name: Event   type: Event 
    - name: IsActive   type: BOOL 
    - name: PriceCategory   type: PriceCategory 
    - name: SeatBlock   type: SeatBlock 
    - name: SoldQuantity   type: LONG 
    - name: TicketType   type: TicketType 
    - name: TotalAllocation   type: LONG 
    - name: VenueArea   type: VenueArea 
The data source for the [SeatBlock] select control should be loaded from the relative URL: 
    "/VenueAreaService/seatblock"   (HTTP-GET) 
The data source for the [Event] select control should be loaded from the relative URL: 
    "/EventService/event"   (HTTP-GET) 
The data source for the [PriceCategory] select control should be loaded from the relative URL: 
    "/BookingService/pricecategory"   (HTTP-GET) 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
The data source for the [TicketType] select control should be loaded from the relative URL: 
    "/EventSeriesService/tickettype"   (HTTP-GET) 
An existing EventTicketType entity should be loaded from the relative URL: 
    "/VenueAreaService/eventtickettype/{id}"   (HTTP-GET) 
If a new EventTicketType entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/eventtickettype"   (HTTP-POST) 
If an existing EventTicketType entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/eventtickettype/{id}"   (HTTP-PUT) 
If an existing EventTicketType entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/eventtickettype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following BookingItem columns: 
    - column: Quantity 
    - column: Booking 
    - column: EventTicketType 
    - column: UnitPrice 
    - column: Event 
    - column: Seat 
    - column: TotalPrice 
The table should have the title "BookingItems" und the data must be loaded from the server with the following relative URL: 
    "/SeatService/bookingitem/eventtickettype/{id}"

4. The SeatBlockView must contain the following fields: 
    - name: Capacity   type: LONG 
    - name: Code   type: STRING 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: VenueArea   type: VenueArea 
The data source for the [VenueArea] select control should be loaded from the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-GET) 
An existing SeatBlock entity should be loaded from the relative URL: 
    "/VenueAreaService/seatblock/{id}"   (HTTP-GET) 
If a new SeatBlock entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/seatblock"   (HTTP-POST) 
If an existing SeatBlock entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/seatblock/{id}"   (HTTP-PUT) 
If an existing SeatBlock entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/seatblock/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Seat columns: 
    - column: RowLabel 
    - column: SeatBlock 
    - column: SeatNumber 
    - column: IsStanding 
The table should have the title "Seats" und the data must be loaded from the server with the following relative URL: 
    "/SeatService/seat/seatblock/{id}" 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: Event 
    - column: BasePrice 
    - column: IsActive 
    - column: SoldQuantity 
    - column: VenueArea 
    - column: TicketType 
    - column: TotalAllocation 
    - column: PriceCategory 
    - column: SeatBlock 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/eventtickettype/seatblock/{id}"

5. The VenueAreaView must contain the following fields: 
    - name: Arena   type: Arena 
    - name: Capacity   type: LONG 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
    - name: Type   type: STRING 
The data source for the [Arena] select control should be loaded from the relative URL: 
    "/EventService/arena"   (HTTP-GET) 
An existing VenueArea entity should be loaded from the relative URL: 
    "/VenueAreaService/venuearea/{id}"   (HTTP-GET) 
If a new VenueArea entity has been created, the new entity should be posted to the relative URL: 
    "/VenueAreaService/venuearea"   (HTTP-POST) 
If an existing VenueArea entity has been updated, the modified entity should be sent to the relative URL: 
    "/VenueAreaService/venuearea/{id}"   (HTTP-PUT) 
If an existing VenueArea entity has to be deleted, the following relative URL should be called: 
    "/VenueAreaService/venuearea/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Event columns: 
    - column: ExternalReference 
    - column: Description 
    - column: IsCanceled 
    - column: StartDateTime 
    - column: MinimumAge 
    - column: Arena 
    - column: EventCategory 
    - column: Organizer 
    - column: TicketUrl 
    - column: Name 
    - column: IsPostponed 
    - column: EndDateTime 
    - column: VenueArea 
    - column: EventSeries 
    - column: DoorOpenTime 
    - column: Subtitle 
    - column: Language 
The table should have the title "Events" und the data must be loaded from the server with the following relative URL: 
    "/EventService/event/venuearea/{id}" 
Add a HTML table to the view with the following SeatBlock columns: 
    - column: Name 
    - column: Capacity 
    - column: Code 
    - column: VenueArea 
    - column: Description 
The table should have the title "SeatBlocks" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/seatblock/venuearea/{id}" 
Add a HTML table to the view with the following GastronomyUnit columns: 
    - column: Type 
    - column: OpeningHours 
    - column: VenueArea 
    - column: Description 
    - column: Name 
The table should have the title "GastronomyUnits" und the data must be loaded from the server with the following relative URL: 
    "/GastronomyUnitService/gastronomyunit/venuearea/{id}" 
Add a HTML table to the view with the following AccessPoint columns: 
    - column: Name 
    - column: AccessCode 
    - column: VenueArea 
    - column: Description 
The table should have the title "AccessPoints" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/accesspoint/venuearea/{id}" 
Add a HTML table to the view with the following EventTicketType columns: 
    - column: Event 
    - column: BasePrice 
    - column: IsActive 
    - column: SoldQuantity 
    - column: VenueArea 
    - column: TicketType 
    - column: TotalAllocation 
    - column: PriceCategory 
    - column: SeatBlock 
The table should have the title "EventTicketTypes" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/eventtickettype/venuearea/{id}" 
Add a HTML table to the view with the following ConferenceRoom columns: 
    - column: Description 
    - column: Name 
    - column: Capacity 
    - column: Floor 
    - column: VenueArea 
    - column: RoomNumber 
The table should have the title "ConferenceRooms" und the data must be loaded from the server with the following relative URL: 
    "/VenueAreaService/conferenceroom/venuearea/{id}"