Prompt for the UserAccountApp

Please create a React-JS application for the UserAccountModule. The application  has to offer the following views for the user interface: 
    1. CampaignView 
    2. CampaignTypeView 
    3. RegionView 
    4. UserAccountView 
    5. UserCampaignStatView 
    6. UserSubscriptionView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 6 views are defined below.

1. The CampaignView must contain the following fields: 
    - name: CampaignType   type: CampaignType 
    - name: IsGlobal   type: BOOL 
    - name: Name   type: STRING 
    - name: PeriodEnd   type: DATE 
    - name: PeriodStart   type: DATE 
The data source for the [CampaignType] select control should be loaded from the relative URL: 
    "/UserAccountService/campaigntype"   (HTTP-GET) 
An existing Campaign entity should be loaded from the relative URL: 
    "/UserAccountService/campaign/{id}"   (HTTP-GET) 
If a new Campaign entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/campaign"   (HTTP-POST) 
If an existing Campaign entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/campaign/{id}"   (HTTP-PUT) 
If an existing Campaign entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/campaign/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserCampaignStat columns: 
    - column: TopArtist 
    - column: TopTrack 
    - column: Campaign 
    - column: UserAccount 
    - column: TotalMinutes 
    - column: GeneratedAt 
The table should have the title "UserCampaignStats" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/usercampaignstat/campaign/{id}"

2. The CampaignTypeView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing CampaignType entity should be loaded from the relative URL: 
    "/UserAccountService/campaigntype/{id}"   (HTTP-GET) 
If a new CampaignType entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/campaigntype"   (HTTP-POST) 
If an existing CampaignType entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/campaigntype/{id}"   (HTTP-PUT) 
If an existing CampaignType entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/campaigntype/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Campaign columns: 
    - column: PeriodStart 
    - column: IsGlobal 
    - column: Name 
    - column: CampaignType 
    - column: PeriodEnd 
The table should have the title "Campaigns" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/campaign/campaigntype/{id}"

3. The RegionView must contain the following fields: 
    - name: Description   type: STRING 
    - name: Name   type: STRING 
An existing Region entity should be loaded from the relative URL: 
    "/UserAccountService/region/{id}"   (HTTP-GET) 
If a new Region entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/region"   (HTTP-POST) 
If an existing Region entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/region/{id}"   (HTTP-PUT) 
If an existing Region entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/region/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserAccount columns: 
    - column: BirthDate 
    - column: Email 
    - column: DisplayName 
    - column: IsPremium 
    - column: CreatedAt 
    - column: Region 
    - column: IsFamilyManager 
    - column: IsStudent 
    - column: Country 
The table should have the title "UserAccounts" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/useraccount/region/{id}"

4. The UserAccountView must contain the following fields: 
    - name: BirthDate   type: DATE 
    - name: Country   type: Country 
    - name: CreatedAt   type: DATE 
    - name: DisplayName   type: STRING 
    - name: Email   type: STRING 
    - name: IsFamilyManager   type: BOOL 
    - name: IsPremium   type: BOOL 
    - name: IsStudent   type: BOOL 
    - name: Region   type: Region 
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: 
    "/UserAccountService/region"   (HTTP-GET) 
An existing UserAccount entity should be loaded from the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-GET) 
If a new UserAccount entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-POST) 
If an existing UserAccount entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/useraccount/{id}"   (HTTP-PUT) 
If an existing UserAccount entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/useraccount/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserCampaignStat columns: 
    - column: TopArtist 
    - column: TopTrack 
    - column: Campaign 
    - column: UserAccount 
    - column: TotalMinutes 
    - column: GeneratedAt 
The table should have the title "UserCampaignStats" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/usercampaignstat/useraccount/{id}" 
Add a HTML table to the view with the following Device columns: 
    - column: IsSpotifyConnectCapable 
    - column: ModelName 
    - column: PlatformApp 
    - column: DeviceType 
    - column: UserAccount 
    - column: RegisteredAt 
The table should have the title "Devices" und the data must be loaded from the server with the following relative URL: 
    "/DeviceService/device/useraccount/{id}" 
Add a HTML table to the view with the following StreamEvent columns: 
    - column: Track 
    - column: PodcastEpisode 
    - column: SubscriptionPlan 
    - column: StartedAt 
    - column: Country 
    - column: IsCountedForRoyalty 
    - column: UserAccount 
    - column: DurationSeconds 
The table should have the title "StreamEvents" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/streamevent/useraccount/{id}" 
Add a HTML table to the view with the following CreatorToolUsage columns: 
    - column: Podcast 
    - column: Artist 
    - column: UserAccount 
    - column: StartedAt 
    - column: CreatorTool 
The table should have the title "CreatorToolUsages" und the data must be loaded from the server with the following relative URL: 
    "/TrackService/creatortoolusage/useraccount/{id}" 
Add a HTML table to the view with the following UserSubscription columns: 
    - column: HouseholdAddress 
    - column: IsPrimaryHolder 
    - column: SubscriptionPlan 
    - column: StartedAt 
    - column: UserAccount 
    - column: EndedAt 
    - column: IsAutoRenew 
The table should have the title "UserSubscriptions" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/usersubscription/useraccount/{id}"

5. The UserCampaignStatView must contain the following fields: 
    - name: Campaign   type: Campaign 
    - name: GeneratedAt   type: DATE 
    - name: TopArtist   type: LONG 
    - name: TopTrack   type: LONG 
    - name: TotalMinutes   type: LONG 
    - name: UserAccount   type: UserAccount 
The data source for the [Campaign] select control should be loaded from the relative URL: 
    "/UserAccountService/campaign"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserCampaignStat entity should be loaded from the relative URL: 
    "/UserAccountService/usercampaignstat/{id}"   (HTTP-GET) 
If a new UserCampaignStat entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/usercampaignstat"   (HTTP-POST) 
If an existing UserCampaignStat entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/usercampaignstat/{id}"   (HTTP-PUT) 
If an existing UserCampaignStat entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/usercampaignstat/{id}"   (HTTP-DELETE)

6. The UserSubscriptionView must contain the following fields: 
    - name: EndedAt   type: DATE 
    - name: HouseholdAddress   type: STRING 
    - name: IsAutoRenew   type: BOOL 
    - name: IsPrimaryHolder   type: BOOL 
    - name: StartedAt   type: DATE 
    - name: SubscriptionPlan   type: SubscriptionPlan 
    - name: UserAccount   type: UserAccount 
The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: 
    "/SubscriptionPlanService/subscriptionplan"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserSubscription entity should be loaded from the relative URL: 
    "/UserAccountService/usersubscription/{id}"   (HTTP-GET) 
If a new UserSubscription entity has been created, the new entity should be posted to the relative URL: 
    "/UserAccountService/usersubscription"   (HTTP-POST) 
If an existing UserSubscription entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserAccountService/usersubscription/{id}"   (HTTP-PUT) 
If an existing UserSubscription entity has to be deleted, the following relative URL should be called: 
    "/UserAccountService/usersubscription/{id}"   (HTTP-DELETE)