Prompt for the RegulatorApp

Please create a React-JS application for the RegulatorModule. The application  has to offer the following views for the user interface: 
    1. LegalActionView 
    2. MarketMakerView 
    3. RegulatorView 
    4. SecurityView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 4 views are defined below.

1. The LegalActionView must contain the following fields: 
    - name: ActionDate   type: DATE 
    - name: ActionType   type: STRING 
    - name: Description   type: STRING 
    - name: Exchange   type: Exchange 
    - name: Regulator   type: Regulator 
The data source for the [Exchange] select control should be loaded from the relative URL: 
    "/ExchangeService/exchange"   (HTTP-GET) 
The data source for the [Regulator] select control should be loaded from the relative URL: 
    "/RegulatorService/regulator"   (HTTP-GET) 
An existing LegalAction entity should be loaded from the relative URL: 
    "/RegulatorService/legalaction/{id}"   (HTTP-GET) 
If a new LegalAction entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatorService/legalaction"   (HTTP-POST) 
If an existing LegalAction entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatorService/legalaction/{id}"   (HTTP-PUT) 
If an existing LegalAction entity has to be deleted, the following relative URL should be called: 
    "/RegulatorService/legalaction/{id}"   (HTTP-DELETE)

2. The MarketMakerView must contain the following fields: 
    - name: Country   type: Country 
    - name: IsNasdaqMember   type: BOOL 
    - name: Name   type: STRING 
    - name: Regulator   type: Regulator 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/ExchangeService/country"   (HTTP-GET) 
The data source for the [Regulator] select control should be loaded from the relative URL: 
    "/RegulatorService/regulator"   (HTTP-GET) 
An existing MarketMaker entity should be loaded from the relative URL: 
    "/RegulatorService/marketmaker/{id}"   (HTTP-GET) 
If a new MarketMaker entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatorService/marketmaker"   (HTTP-POST) 
If an existing MarketMaker entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatorService/marketmaker/{id}"   (HTTP-PUT) 
If an existing MarketMaker entity has to be deleted, the following relative URL should be called: 
    "/RegulatorService/marketmaker/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following MarketMakerQuotePermission columns: 
    - column: MarketMaker 
    - column: EffectiveTo 
    - column: EffectiveFrom 
    - column: Exchange 
    - column: QuoteLevel 
The table should have the title "MarketMakerQuotePermissions" und the data must be loaded from the server with the following relative URL: 
    "/QuoteLevelService/marketmakerquotepermission/marketmaker/{id}"

3. The RegulatorView must contain the following fields: 
    - name: Country   type: Country 
    - name: Name   type: STRING 
    - name: Type   type: STRING 
    - name: Website   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/ExchangeService/country"   (HTTP-GET) 
An existing Regulator entity should be loaded from the relative URL: 
    "/RegulatorService/regulator/{id}"   (HTTP-GET) 
If a new Regulator entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatorService/regulator"   (HTTP-POST) 
If an existing Regulator entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatorService/regulator/{id}"   (HTTP-PUT) 
If an existing Regulator entity has to be deleted, the following relative URL should be called: 
    "/RegulatorService/regulator/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following LegalAction columns: 
    - column: Exchange 
    - column: ActionDate 
    - column: ActionType 
    - column: Description 
    - column: Regulator 
The table should have the title "LegalActions" und the data must be loaded from the server with the following relative URL: 
    "/RegulatorService/legalaction/regulator/{id}" 
Add a HTML table to the view with the following MarketMaker columns: 
    - column: Regulator 
    - column: Name 
    - column: IsNasdaqMember 
    - column: Country 
The table should have the title "MarketMakers" und the data must be loaded from the server with the following relative URL: 
    "/RegulatorService/marketmaker/regulator/{id}" 
Add a HTML table to the view with the following Inspection columns: 
    - column: InspectionDate 
    - column: IsAntitrustRelated 
    - column: Description 
    - column: Regulator 
    - column: Exchange 
The table should have the title "Inspections" und the data must be loaded from the server with the following relative URL: 
    "/ExchangeService/inspection/regulator/{id}"

4. The SecurityView must contain the following fields: 
    - name: Currency   type: STRING 
    - name: IsActive   type: BOOL 
    - name: Listing   type: Listing 
    - name: SecurityType   type: STRING 
The data source for the [Listing] select control should be loaded from the relative URL: 
    "/ListingService/listing"   (HTTP-GET) 
An existing Security entity should be loaded from the relative URL: 
    "/RegulatorService/security/{id}"   (HTTP-GET) 
If a new Security entity has been created, the new entity should be posted to the relative URL: 
    "/RegulatorService/security"   (HTTP-POST) 
If an existing Security entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegulatorService/security/{id}"   (HTTP-PUT) 
If an existing Security entity has to be deleted, the following relative URL should be called: 
    "/RegulatorService/security/{id}"   (HTTP-DELETE)