Prompt for the RegionApp

Please create a React-JS application for the RegionModule. The application  has to offer the following views for the user interface: 
    1. ExchangeRateView 
    2. RegionView 
    3. RegulatoryLicenseView 
    4. SecurityIncidentView 
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 ExchangeRateView must contain the following fields: 
    - name: EffectiveFrom   type: DATE 
    - name: EffectiveTo   type: DATE 
    - name: Rate   type: DOUBLE 
    - name: SourceCurrency   type: LONG 
    - name: TargetCurrency   type: LONG 
An existing ExchangeRate entity should be loaded from the relative URL: 
    "/RegionService/exchangerate/{id}"   (HTTP-GET) 
If a new ExchangeRate entity has been created, the new entity should be posted to the relative URL: 
    "/RegionService/exchangerate"   (HTTP-POST) 
If an existing ExchangeRate entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegionService/exchangerate/{id}"   (HTTP-PUT) 
If an existing ExchangeRate entity has to be deleted, the following relative URL should be called: 
    "/RegionService/exchangerate/{id}"   (HTTP-DELETE)

2. The RegionView must contain the following fields: 
    - name: Code   type: STRING 
    - name: Name   type: STRING 
An existing Region entity should be loaded from the relative URL: 
    "/RegionService/region/{id}"   (HTTP-GET) 
If a new Region entity has been created, the new entity should be posted to the relative URL: 
    "/RegionService/region"   (HTTP-POST) 
If an existing Region entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegionService/region/{id}"   (HTTP-PUT) 
If an existing Region entity has to be deleted, the following relative URL should be called: 
    "/RegionService/region/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following RegulatoryLicense columns: 
    - column: AuthorityName 
    - column: Region 
    - column: Status 
    - column: LicenseType 
    - column: IssuedAt 
    - column: Country 
    - column: LicenseNumber 
    - column: ExpiresAt 
The table should have the title "RegulatoryLicenses" und the data must be loaded from the server with the following relative URL: 
    "/RegionService/regulatorylicense/region/{id}" 
Add a HTML table to the view with the following Country columns: 
    - column: Name 
    - column: IsoCode3 
    - column: IsoCode2 
    - column: Region 
The table should have the title "Countrys" und the data must be loaded from the server with the following relative URL: 
    "/CountryService/country/region/{id}"

3. The RegulatoryLicenseView must contain the following fields: 
    - name: AuthorityName   type: STRING 
    - name: Country   type: Country 
    - name: ExpiresAt   type: DATE 
    - name: IssuedAt   type: DATE 
    - name: LicenseNumber   type: STRING 
    - name: LicenseType   type: STRING 
    - name: Region   type: Region 
    - name: Status   type: STRING 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
The data source for the [Region] select control should be loaded from the relative URL: 
    "/RegionService/region"   (HTTP-GET) 
An existing RegulatoryLicense entity should be loaded from the relative URL: 
    "/RegionService/regulatorylicense/{id}"   (HTTP-GET) 
If a new RegulatoryLicense entity has been created, the new entity should be posted to the relative URL: 
    "/RegionService/regulatorylicense"   (HTTP-POST) 
If an existing RegulatoryLicense entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegionService/regulatorylicense/{id}"   (HTTP-PUT) 
If an existing RegulatoryLicense entity has to be deleted, the following relative URL should be called: 
    "/RegionService/regulatorylicense/{id}"   (HTTP-DELETE)

4. The SecurityIncidentView must contain the following fields: 
    - name: Description   type: STRING 
    - name: DetectedAt   type: DATE 
    - name: Merchant   type: Merchant 
    - name: ResolvedAt   type: DATE 
    - name: Severity   type: STRING 
    - name: Type   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [Merchant] select control should be loaded from the relative URL: 
    "/MerchantService/merchant"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing SecurityIncident entity should be loaded from the relative URL: 
    "/RegionService/securityincident/{id}"   (HTTP-GET) 
If a new SecurityIncident entity has been created, the new entity should be posted to the relative URL: 
    "/RegionService/securityincident"   (HTTP-POST) 
If an existing SecurityIncident entity has been updated, the modified entity should be sent to the relative URL: 
    "/RegionService/securityincident/{id}"   (HTTP-PUT) 
If an existing SecurityIncident entity has to be deleted, the following relative URL should be called: 
    "/RegionService/securityincident/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following SupportCase columns: 
    - column: Description 
    - column: Status 
    - column: Subject 
    - column: Channel 
    - column: Dispute 
    - column: UserAccount 
    - column: ClosedAt 
    - column: Transaction 
    - column: OpenedAt 
    - column: SecurityIncident 
The table should have the title "SupportCases" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/supportcase/securityincident/{id}"