Prompt for the App

Please create a React-JS application for the Module. The application  has to offer the following views for the user interface: 
    1. MarketPresenceView 
    2. RegulatoryRestrictionView 
    3. ServiceOutageView 
    4. ServiceSupplyView 
    5. TrafficStatisticView 
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 MarketPresenceView must contain the following fields: 
    - name: Country   type: Country 
    - name: ExitDate   type: DATE 
    - name: LaunchDate   type: DATE 
    - name: Notes   type: STRING 
    - name: ServiceSupply   type: ServiceSupply 
    - name: Status   type: STRING 
The data source for the [ServiceSupply] select control should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-GET) 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing MarketPresence entity should be loaded from the relative URL: 
    "/ServiceSupplyService/marketpresence/{id}"   (HTTP-GET) 
If a new MarketPresence entity has been created, the new entity should be posted to the relative URL: 
    "/ServiceSupplyService/marketpresence"   (HTTP-POST) 
If an existing MarketPresence entity has been updated, the modified entity should be sent to the relative URL: 
    "/ServiceSupplyService/marketpresence/{id}"   (HTTP-PUT) 
If an existing MarketPresence entity has to be deleted, the following relative URL should be called: 
    "/ServiceSupplyService/marketpresence/{id}"   (HTTP-DELETE)

2. The RegulatoryRestrictionView must contain the following fields: 
    - name: Country   type: Country 
    - name: EndDate   type: DATE 
    - name: Reason   type: STRING 
    - name: RestrictionType   type: STRING 
    - name: ServiceSupply   type: ServiceSupply 
    - name: StartDate   type: DATE 
The data source for the [ServiceSupply] select control should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-GET) 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing RegulatoryRestriction entity should be loaded from the relative URL: 
    "/ServiceSupplyService/regulatoryrestriction/{id}"   (HTTP-GET) 
If a new RegulatoryRestriction entity has been created, the new entity should be posted to the relative URL: 
    "/ServiceSupplyService/regulatoryrestriction"   (HTTP-POST) 
If an existing RegulatoryRestriction entity has been updated, the modified entity should be sent to the relative URL: 
    "/ServiceSupplyService/regulatoryrestriction/{id}"   (HTTP-PUT) 
If an existing RegulatoryRestriction entity has to be deleted, the following relative URL should be called: 
    "/ServiceSupplyService/regulatoryrestriction/{id}"   (HTTP-DELETE)

3. The ServiceOutageView must contain the following fields: 
    - name: Description   type: STRING 
    - name: EndDate   type: DATE 
    - name: ImpactDescription   type: STRING 
    - name: ServiceSupply   type: ServiceSupply 
    - name: StartDate   type: DATE 
The data source for the [ServiceSupply] select control should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-GET) 
An existing ServiceOutage entity should be loaded from the relative URL: 
    "/ServiceSupplyService/serviceoutage/{id}"   (HTTP-GET) 
If a new ServiceOutage entity has been created, the new entity should be posted to the relative URL: 
    "/ServiceSupplyService/serviceoutage"   (HTTP-POST) 
If an existing ServiceOutage entity has been updated, the modified entity should be sent to the relative URL: 
    "/ServiceSupplyService/serviceoutage/{id}"   (HTTP-PUT) 
If an existing ServiceOutage entity has to be deleted, the following relative URL should be called: 
    "/ServiceSupplyService/serviceoutage/{id}"   (HTTP-DELETE)

4. The ServiceSupplyView must contain the following fields: 
    - name: Company   type: Company 
    - name: Description   type: STRING 
    - name: LaunchDate   type: DATE 
    - name: Name   type: STRING 
    - name: Status   type: STRING 
    - name: Type   type: STRING 
    - name: Url   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing ServiceSupply entity should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply/{id}"   (HTTP-GET) 
If a new ServiceSupply entity has been created, the new entity should be posted to the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-POST) 
If an existing ServiceSupply entity has been updated, the modified entity should be sent to the relative URL: 
    "/ServiceSupplyService/servicesupply/{id}"   (HTTP-PUT) 
If an existing ServiceSupply entity has to be deleted, the following relative URL should be called: 
    "/ServiceSupplyService/servicesupply/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ServiceOutage columns: 
    - column: EndDate 
    - column: ServiceSupply 
    - column: Description 
    - column: ImpactDescription 
    - column: StartDate 
The table should have the title "ServiceOutages" und the data must be loaded from the server with the following relative URL: 
    "/ServiceSupplyService/serviceoutage/servicesupply/{id}" 
Add a HTML table to the view with the following RegulatoryRestriction columns: 
    - column: Reason 
    - column: StartDate 
    - column: EndDate 
    - column: RestrictionType 
    - column: ServiceSupply 
    - column: Country 
The table should have the title "RegulatoryRestrictions" und the data must be loaded from the server with the following relative URL: 
    "/ServiceSupplyService/regulatoryrestriction/servicesupply/{id}" 
Add a HTML table to the view with the following TrafficStatistic columns: 
    - column: ServiceSupply 
    - column: Country 
    - column: RankGlobal 
    - column: Notes 
    - column: Year 
    - column: TrafficSharePercent 
The table should have the title "TrafficStatistics" und the data must be loaded from the server with the following relative URL: 
    "/ServiceSupplyService/trafficstatistic/servicesupply/{id}" 
Add a HTML table to the view with the following ServiceLanguage columns: 
    - column: Language 
    - column: ServiceSupply 
    - column: AvailabilityType 
The table should have the title "ServiceLanguages" und the data must be loaded from the server with the following relative URL: 
    "/LanguageService/servicelanguage/servicesupply/{id}" 
Add a HTML table to the view with the following PeeringAgreement columns: 
    - column: InternetServiceProvider 
    - column: StartDate 
    - column: Notes 
    - column: EndDate 
    - column: ServiceSupply 
The table should have the title "PeeringAgreements" und the data must be loaded from the server with the following relative URL: 
    "/LanguageService/peeringagreement/servicesupply/{id}" 
Add a HTML table to the view with the following MarketPresence columns: 
    - column: ServiceSupply 
    - column: Country 
    - column: Status 
    - column: Notes 
    - column: ExitDate 
    - column: LaunchDate 
The table should have the title "MarketPresences" und the data must be loaded from the server with the following relative URL: 
    "/ServiceSupplyService/marketpresence/servicesupply/{id}" 
Add a HTML table to the view with the following ContentAvailability columns: 
    - column: EndDate 
    - column: Country 
    - column: ServiceSupply 
    - column: StartDate 
    - column: Notes 
    - column: ContentTitle 
The table should have the title "ContentAvailabilitys" und the data must be loaded from the server with the following relative URL: 
    "/ContentTitleService/contentavailability/servicesupply/{id}" 
Add a HTML table to the view with the following DeviceIntegration columns: 
    - column: Notes 
    - column: EndDate 
    - column: ServiceSupply 
    - column: Device 
    - column: StartDate 
    - column: IntegrationType 
The table should have the title "DeviceIntegrations" und the data must be loaded from the server with the following relative URL: 
    "/DeviceService/deviceintegration/servicesupply/{id}" 
Add a HTML table to the view with the following SubscriptionPlan columns: 
    - column: ServiceSupply 
    - column: Description 
    - column: MonthlyPrice 
    - column: Name 
    - column: StartDate 
    - column: EndDate 
    - column: PlanType 
The table should have the title "SubscriptionPlans" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionPlanService/subscriptionplan/servicesupply/{id}" 
Add a HTML table to the view with the following ServiceFeature columns: 
    - column: Description 
    - column: Name 
    - column: LaunchDate 
    - column: ServiceSupply 
The table should have the title "ServiceFeatures" und the data must be loaded from the server with the following relative URL: 
    "/SeasonService/servicefeature/servicesupply/{id}" 
Add a HTML table to the view with the following ContentDistribution columns: 
    - column: StartDate 
    - column: EndDate 
    - column: DistributionType 
    - column: Notes 
    - column: ContentTitle 
    - column: ServiceSupply 
The table should have the title "ContentDistributions" und the data must be loaded from the server with the following relative URL: 
    "/DeviceService/contentdistribution/servicesupply/{id}"

5. The TrafficStatisticView must contain the following fields: 
    - name: Country   type: Country 
    - name: Notes   type: STRING 
    - name: RankGlobal   type: LONG 
    - name: ServiceSupply   type: ServiceSupply 
    - name: TrafficSharePercent   type: STRING 
    - name: Year   type: LONG 
The data source for the [ServiceSupply] select control should be loaded from the relative URL: 
    "/ServiceSupplyService/servicesupply"   (HTTP-GET) 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing TrafficStatistic entity should be loaded from the relative URL: 
    "/ServiceSupplyService/trafficstatistic/{id}"   (HTTP-GET) 
If a new TrafficStatistic entity has been created, the new entity should be posted to the relative URL: 
    "/ServiceSupplyService/trafficstatistic"   (HTTP-POST) 
If an existing TrafficStatistic entity has been updated, the modified entity should be sent to the relative URL: 
    "/ServiceSupplyService/trafficstatistic/{id}"   (HTTP-PUT) 
If an existing TrafficStatistic entity has to be deleted, the following relative URL should be called: 
    "/ServiceSupplyService/trafficstatistic/{id}"   (HTTP-DELETE)