Prompt for the UserDocumentApp

Please create a React-JS application for the UserDocumentModule. The application  has to offer the following views for the user interface: 
    1. UserDocumentView 
    2. UserKycVerificationView 
    3. UserProfileView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 3 views are defined below.

1. The UserDocumentView must contain the following fields: 
    - name: CreatedAt   type: DATE 
    - name: DocumentNumber   type: STRING 
    - name: DocumentType   type: STRING 
    - name: ExpiresAt   type: DATE 
    - name: IssuedAt   type: DATE 
    - name: IssuedBy   type: STRING 
    - name: Status   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserDocument entity should be loaded from the relative URL: 
    "/UserDocumentService/userdocument/{id}"   (HTTP-GET) 
If a new UserDocument entity has been created, the new entity should be posted to the relative URL: 
    "/UserDocumentService/userdocument"   (HTTP-POST) 
If an existing UserDocument entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserDocumentService/userdocument/{id}"   (HTTP-PUT) 
If an existing UserDocument entity has to be deleted, the following relative URL should be called: 
    "/UserDocumentService/userdocument/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following UserKycVerification columns: 
    - column: RequestedAt 
    - column: Notes 
    - column: UserAccount 
    - column: Reviewer 
    - column: Status 
    - column: VerificationType 
    - column: CompletedAt 
    - column: UserDocument 
The table should have the title "UserKycVerifications" und the data must be loaded from the server with the following relative URL: 
    "/UserDocumentService/userkycverification/userdocument/{id}"

2. The UserKycVerificationView must contain the following fields: 
    - name: CompletedAt   type: DATE 
    - name: Notes   type: STRING 
    - name: RequestedAt   type: DATE 
    - name: Reviewer   type: STRING 
    - name: Status   type: STRING 
    - name: UserAccount   type: UserAccount 
    - name: UserDocument   type: UserDocument 
    - name: VerificationType   type: STRING 
The data source for the [UserDocument] select control should be loaded from the relative URL: 
    "/UserDocumentService/userdocument"   (HTTP-GET) 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserKycVerification entity should be loaded from the relative URL: 
    "/UserDocumentService/userkycverification/{id}"   (HTTP-GET) 
If a new UserKycVerification entity has been created, the new entity should be posted to the relative URL: 
    "/UserDocumentService/userkycverification"   (HTTP-POST) 
If an existing UserKycVerification entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserDocumentService/userkycverification/{id}"   (HTTP-PUT) 
If an existing UserKycVerification entity has to be deleted, the following relative URL should be called: 
    "/UserDocumentService/userkycverification/{id}"   (HTTP-DELETE)

3. The UserProfileView must contain the following fields: 
    - name: DateOfBirth   type: DATE 
    - name: FirstName   type: STRING 
    - name: Language   type: STRING 
    - name: LastName   type: STRING 
    - name: PhoneNumber   type: STRING 
    - name: TimeZone   type: STRING 
    - name: UserAccount   type: UserAccount 
The data source for the [UserAccount] select control should be loaded from the relative URL: 
    "/UserAccountService/useraccount"   (HTTP-GET) 
An existing UserProfile entity should be loaded from the relative URL: 
    "/UserDocumentService/userprofile/{id}"   (HTTP-GET) 
If a new UserProfile entity has been created, the new entity should be posted to the relative URL: 
    "/UserDocumentService/userprofile"   (HTTP-POST) 
If an existing UserProfile entity has been updated, the modified entity should be sent to the relative URL: 
    "/UserDocumentService/userprofile/{id}"   (HTTP-PUT) 
If an existing UserProfile entity has to be deleted, the following relative URL should be called: 
    "/UserDocumentService/userprofile/{id}"   (HTTP-DELETE)