Prompt for the AdApp

Please create a React-JS application for the AdModule. The application  has to offer the following views for the user interface: 
    1. AdView 
    2. CategoryView 
    3. NotificationView 
    4. VideoAdView 
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 AdView must contain the following fields: 
    - name: AdvertiserName   type: STRING 
    - name: BudgetInfoJson   type: STRING 
    - name: CampaignName   type: STRING 
    - name: CreatedAt   type: DATE 
    - name: Format   type: STRING 
    - name: MediaUrl   type: STRING 
    - name: TargetingJson   type: STRING 
An existing Ad entity should be loaded from the relative URL: 
    "/AdService/ad/{id}"   (HTTP-GET) 
If a new Ad entity has been created, the new entity should be posted to the relative URL: 
    "/AdService/ad"   (HTTP-POST) 
If an existing Ad entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdService/ad/{id}"   (HTTP-PUT) 
If an existing Ad entity has to be deleted, the following relative URL should be called: 
    "/AdService/ad/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following AdImpression columns: 
    - column: Video 
    - column: Ad 
    - column: RevenueMicros 
    - column: ClickedAt 
    - column: User 
    - column: ImpressionAt 
    - column: Device 
The table should have the title "AdImpressions" und the data must be loaded from the server with the following relative URL: 
    "/UserService/adimpression/ad/{id}" 
Add a HTML table to the view with the following VideoAd columns: 
    - column: Video 
    - column: Ad 
    - column: CreatedAt 
    - column: Position 
    - column: InsertTimeSeconds 
The table should have the title "VideoAds" und the data must be loaded from the server with the following relative URL: 
    "/AdService/videoad/ad/{id}"

2. The CategoryView must contain the following fields: 
    - name: Description   type: STRING 
    - name: IsActive   type: BOOL 
    - name: Name   type: STRING 
An existing Category entity should be loaded from the relative URL: 
    "/AdService/category/{id}"   (HTTP-GET) 
If a new Category entity has been created, the new entity should be posted to the relative URL: 
    "/AdService/category"   (HTTP-POST) 
If an existing Category entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdService/category/{id}"   (HTTP-PUT) 
If an existing Category entity has to be deleted, the following relative URL should be called: 
    "/AdService/category/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Video columns: 
    - column: ResolutionHeight 
    - column: VisibilityRegionRestrictionJson 
    - column: DefaultCaptionLanguage 
    - column: PrivacyStatus 
    - column: Language 
    - column: MadeForKids 
    - column: ThumbnailDefault 
    - column: CreatedAt 
    - column: Title 
    - column: FrameRate 
    - column: CommentCountCached 
    - column: Category 
    - column: ResolutionWidth 
    - column: ThumbnailMedium 
    - column: OriginalFileName 
    - column: UpdatedAt 
    - column: LikeCountCached 
    - column: ThumbnailHigh 
    - column: ViewCountCached 
    - column: PublishedAt 
    - column: Channel 
    - column: DurationSeconds 
    - column: Status 
    - column: FilePathOrStorageKey 
    - column: LicenseType 
    - column: Description 
The table should have the title "Videos" und the data must be loaded from the server with the following relative URL: 
    "/VideoService/video/category/{id}"

3. The NotificationView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: IsRead   type: BOOL 
    - name: PayloadJson   type: STRING 
    - name: Type   type: STRING 
    - name: User   type: User 
The data source for the [User] select control should be loaded from the relative URL: 
    "/UserService/user"   (HTTP-GET) 
An existing Notification entity should be loaded from the relative URL: 
    "/AdService/notification/{id}"   (HTTP-GET) 
If a new Notification entity has been created, the new entity should be posted to the relative URL: 
    "/AdService/notification"   (HTTP-POST) 
If an existing Notification entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdService/notification/{id}"   (HTTP-PUT) 
If an existing Notification entity has to be deleted, the following relative URL should be called: 
    "/AdService/notification/{id}"   (HTTP-DELETE)

4. The VideoAdView must contain the following fields: 
    - name: Ad   type: Ad 
    - name: CreatedAt   type: DATE 
    - name: InsertTimeSeconds   type: LONG 
    - name: Position   type: STRING 
    - name: Video   type: Video 
The data source for the [Ad] select control should be loaded from the relative URL: 
    "/AdService/ad"   (HTTP-GET) 
The data source for the [Video] select control should be loaded from the relative URL: 
    "/VideoService/video"   (HTTP-GET) 
An existing VideoAd entity should be loaded from the relative URL: 
    "/AdService/videoad/{id}"   (HTTP-GET) 
If a new VideoAd entity has been created, the new entity should be posted to the relative URL: 
    "/AdService/videoad"   (HTTP-POST) 
If an existing VideoAd entity has been updated, the modified entity should be sent to the relative URL: 
    "/AdService/videoad/{id}"   (HTTP-PUT) 
If an existing VideoAd entity has to be deleted, the following relative URL should be called: 
    "/AdService/videoad/{id}"   (HTTP-DELETE)