Prompt for the ReelApp

Please create a React-JS application for the ReelModule. The application  has to offer the following views for the user interface: 
    1. AdCampaignView 
    2. NotificationView 
    3. ReelView 
    4. ReelViewView 
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 AdCampaignView must contain the following fields: 
    - name: AdvertiserName   type: STRING 
    - name: Budget   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: EndDate   type: DATE 
    - name: Name   type: STRING 
    - name: Objective   type: STRING 
    - name: StartDate   type: DATE 
An existing AdCampaign entity should be loaded from the relative URL: 
    "/ReelService/adcampaign/{id}"   (HTTP-GET) 
If a new AdCampaign entity has been created, the new entity should be posted to the relative URL: 
    "/ReelService/adcampaign"   (HTTP-POST) 
If an existing AdCampaign entity has been updated, the modified entity should be sent to the relative URL: 
    "/ReelService/adcampaign/{id}"   (HTTP-PUT) 
If an existing AdCampaign entity has to be deleted, the following relative URL should be called: 
    "/ReelService/adcampaign/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AdPlacement columns: 
    - column: Post 
    - column: Clicks 
    - column: Impressions 
    - column: CreatedAt 
    - column: Reel 
    - column: AdCampaign 
    - column: PlacementType 
    - column: Story 
The table should have the title "AdPlacements" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/adplacement/adcampaign/{id}"

2. The NotificationView must contain the following fields: 
    - name: Comment   type: Comment 
    - name: CreatedAt   type: DATE 
    - name: DirectMessage   type: DirectMessage 
    - name: IsRead   type: BOOL 
    - name: Post   type: Post 
    - name: Reel   type: Reel 
    - name: SourceUser   type: UserAccount 
    - name: Story   type: Story 
    - name: Type   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [DirectMessage] select control should be loaded from the relative URL: 
    "/DirectThreadService/directmessage"   (HTTP-GET) 
The data source for the [Comment] select control should be loaded from the relative URL: 
    "/StoryService/comment"   (HTTP-GET) 
The data source for the [SourceUser] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
The data source for the [Post] select control should be loaded from the relative URL: 
    "/UserAccountService/post"   (HTTP-GET) 
The data source for the [Reel] select control should be loaded from the relative URL: 
    "/ReelService/reel"   (HTTP-GET) 
The data source for the [Story] select control should be loaded from the relative URL: 
    "/StoryService/story"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Notification entity should be loaded from the relative URL: 
    "/ReelService/notification/{id}"   (HTTP-GET) 
If a new Notification entity has been created, the new entity should be posted to the relative URL: 
    "/ReelService/notification"   (HTTP-POST) 
If an existing Notification entity has been updated, the modified entity should be sent to the relative URL: 
    "/ReelService/notification/{id}"   (HTTP-PUT) 
If an existing Notification entity has to be deleted, the following relative URL should be called: 
    "/ReelService/notification/{id}"   (HTTP-DELETE)

3. The ReelView must contain the following fields: 
    - name: AudioTrack   type: STRING 
    - name: Caption   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: DurationSeconds   type: LONG 
    - name: IsRemixAllowed   type: BOOL 
    - name: UpdatedAt   type: DATE 
    - name: UserAccount   type: UserAccount 
    - name: Visibility   type: STRING 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing Reel entity should be loaded from the relative URL: 
    "/ReelService/reel/{id}"   (HTTP-GET) 
If a new Reel entity has been created, the new entity should be posted to the relative URL: 
    "/ReelService/reel"   (HTTP-POST) 
If an existing Reel entity has been updated, the modified entity should be sent to the relative URL: 
    "/ReelService/reel/{id}"   (HTTP-PUT) 
If an existing Reel entity has to be deleted, the following relative URL should be called: 
    "/ReelService/reel/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following DirectMessage columns: 
    - column: Reel 
    - column: MediaUrl 
    - column: Post 
    - column: Sender 
    - column: Story 
    - column: ReplyToMessage 
    - column: DirectThread 
    - column: SeenAt 
    - column: CreatedAt 
    - column: Text 
    - column: MessageType 
    - column: IsSeen 
The table should have the title "DirectMessages" und the data must be loaded from the server with the following relative URL: 
    "/DirectThreadService/directmessage/reel/{id}" 
Add a HTML table to the view with the following ReelView columns: 
    - column: ViewDurationSeconds 
    - column: UserAccount 
    - column: ViewedAt 
    - column: Reel 
The table should have the title "ReelViews" und the data must be loaded from the server with the following relative URL: 
    "/ReelService/reelview/reel/{id}" 
Add a HTML table to the view with the following ReelLike columns: 
    - column: UserAccount 
    - column: CreatedAt 
    - column: Reel 
The table should have the title "ReelLikes" und the data must be loaded from the server with the following relative URL: 
    "/UserAccountService/reellike/reel/{id}" 
Add a HTML table to the view with the following Notification columns: 
    - column: Post 
    - column: Story 
    - column: SourceUser 
    - column: Reel 
    - column: Type 
    - column: Comment 
    - column: DirectMessage 
    - column: IsRead 
    - column: CreatedAt 
    - column: UserAccount 
The table should have the title "Notifications" und the data must be loaded from the server with the following relative URL: 
    "/ReelService/notification/reel/{id}" 
Add a HTML table to the view with the following Report columns: 
    - column: ReportedUser 
    - column: Reporter 
    - column: Post 
    - column: CreatedAt 
    - column: Reel 
    - column: Comment 
    - column: Story 
    - column: Status 
    - column: Reason 
    - column: Details 
    - column: UpdatedAt 
The table should have the title "Reports" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/report/reel/{id}" 
Add a HTML table to the view with the following ArchiveItem columns: 
    - column: UserAccount 
    - column: Post 
    - column: ItemType 
    - column: Story 
    - column: ArchivedAt 
    - column: Reel 
The table should have the title "ArchiveItems" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/archiveitem/reel/{id}" 
Add a HTML table to the view with the following AdPlacement columns: 
    - column: Post 
    - column: Clicks 
    - column: Impressions 
    - column: CreatedAt 
    - column: Reel 
    - column: AdCampaign 
    - column: PlacementType 
    - column: Story 
The table should have the title "AdPlacements" und the data must be loaded from the server with the following relative URL: 
    "/StoryService/adplacement/reel/{id}"

4. The ReelViewView must contain the following fields: 
    - name: Reel   type: Reel 
    - name: UserAccount   type: UserAccount 
    - name: ViewDurationSeconds   type: LONG 
    - name: ViewedAt   type: DATE 
The data source for the [Reel] select control should be loaded from the relative URL: 
    "/ReelService/reel"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing ReelView entity should be loaded from the relative URL: 
    "/ReelService/reelview/{id}"   (HTTP-GET) 
If a new ReelView entity has been created, the new entity should be posted to the relative URL: 
    "/ReelService/reelview"   (HTTP-POST) 
If an existing ReelView entity has been updated, the modified entity should be sent to the relative URL: 
    "/ReelService/reelview/{id}"   (HTTP-PUT) 
If an existing ReelView entity has to be deleted, the following relative URL should be called: 
    "/ReelService/reelview/{id}"   (HTTP-DELETE)