Prompt for the AdvertisementApp

Please create a React-JS application for the AdvertisementModule. The application  has to offer the following views for the user interface: 
    1. AdImpressionView 
    2. AdvertisementView 
    3. SubscriptionPlanView 
    4. TimeZoneView 
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 AdImpressionView must contain the following fields: 
    - name: Advertisement   type: Advertisement 
    - name: Clicked   type: BOOL 
    - name: RevenueShare   type: DOUBLE 
    - name: ShownAtUtc   type: DATE 
    - name: UserAccount   type: UserAccount 
The data source for the [Advertisement] select control should be loaded from the relative URL: 
    "/AdvertisementService/advertisement"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing AdImpression entity should be loaded from the relative URL: 
    "/AdvertisementService/adimpression/{id}"   (HTTP-GET) 
If a new AdImpression entity has been created, the new entity should be posted to the relative URL: 
    "/AdvertisementService/adimpression"   (HTTP-POST) 
If an existing AdImpression entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdvertisementService/adimpression/{id}"   (HTTP-PUT) 
If an existing AdImpression entity has to be deleted, the following relative URL should be called: 
    "/AdvertisementService/adimpression/{id}"   (HTTP-DELETE)

2. The AdvertisementView must contain the following fields: 
    - name: Active   type: BOOL 
    - name: CampaignName   type: STRING 
    - name: EndDateUtc   type: DATE 
    - name: ProviderName   type: STRING 
    - name: StartDateUtc   type: DATE 
    - name: TargetingJson   type: STRING 
An existing Advertisement entity should be loaded from the relative URL: 
    "/AdvertisementService/advertisement/{id}"   (HTTP-GET) 
If a new Advertisement entity has been created, the new entity should be posted to the relative URL: 
    "/AdvertisementService/advertisement"   (HTTP-POST) 
If an existing Advertisement entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdvertisementService/advertisement/{id}"   (HTTP-PUT) 
If an existing Advertisement entity has to be deleted, the following relative URL should be called: 
    "/AdvertisementService/advertisement/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AdImpression columns: 
    - column: RevenueShare 
    - column: Advertisement 
    - column: Clicked 
    - column: UserAccount 
    - column: ShownAtUtc 
The table should have the title "AdImpressions" und the data must be loaded from the server with the following relative URL: 
    "/AdvertisementService/adimpression/advertisement/{id}"

3. The SubscriptionPlanView must contain the following fields: 
    - name: HasAlerts   type: BOOL 
    - name: HasHistoricalData   type: BOOL 
    - name: HasNoAds   type: BOOL 
    - name: HasWeatherLayers   type: BOOL 
    - name: MaxDevices   type: INT 
    - name: Name   type: STRING 
    - name: PriceMonthly   type: DOUBLE 
    - name: PriceYearly   type: DOUBLE 
An existing SubscriptionPlan entity should be loaded from the relative URL: 
    "/AdvertisementService/subscriptionplan/{id}"   (HTTP-GET) 
If a new SubscriptionPlan entity has been created, the new entity should be posted to the relative URL: 
    "/AdvertisementService/subscriptionplan"   (HTTP-POST) 
If an existing SubscriptionPlan entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdvertisementService/subscriptionplan/{id}"   (HTTP-PUT) 
If an existing SubscriptionPlan entity has to be deleted, the following relative URL should be called: 
    "/AdvertisementService/subscriptionplan/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserSubscription columns: 
    - column: EndDateUtc 
    - column: SubscriptionPlan 
    - column: AutoRenew 
    - column: Status 
    - column: UserAccount 
    - column: StartDateUtc 
The table should have the title "UserSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/usersubscription/subscriptionplan/{id}"

4. The TimeZoneView must contain the following fields: 
    - name: DisplayName   type: STRING 
    - name: Identifier   type: STRING 
    - name: UtcOffsetMinutes   type: INT 
An existing TimeZone entity should be loaded from the relative URL: 
    "/AdvertisementService/timezone/{id}"   (HTTP-GET) 
If a new TimeZone entity has been created, the new entity should be posted to the relative URL: 
    "/AdvertisementService/timezone"   (HTTP-POST) 
If an existing TimeZone entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdvertisementService/timezone/{id}"   (HTTP-PUT) 
If an existing TimeZone entity has to be deleted, the following relative URL should be called: 
    "/AdvertisementService/timezone/{id}"   (HTTP-DELETE)