Prompt for the RoleApp

Please create a React-JS application for the RoleModule. The application  has to offer the following views for the user interface: 
    1. MarketShareStatView 
    2. RegulatoryActionView 
    3. RoleView 
    4. RoleHistoryView 
    5. StockOwnershipView 
The views have to be reachable for the user via a menu list at the left side of each view. The requirements for the 5 views are defined below.

1. The MarketShareStatView must contain the following fields: 
    - name: Company   type: Company 
    - name: MarketRegion   type: STRING 
    - name: MarketSharePercent   type: DOUBLE 
    - name: PeriodDescription   type: STRING 
    - name: SegmentDescription   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing MarketShareStat entity should be loaded from the relative URL: 
    "/RoleService/marketsharestat/{id}"   (HTTP-GET) 
If a new MarketShareStat entity has been created, the new entity should be posted to the relative URL: 
    "/RoleService/marketsharestat"   (HTTP-POST) 
If an existing MarketShareStat entity has been updated, the modified entity should be sent to the relative URL: 
    "/RoleService/marketsharestat/{id}"   (HTTP-PUT) 
If an existing MarketShareStat entity has to be deleted, the following relative URL should be called: 
    "/RoleService/marketsharestat/{id}"   (HTTP-DELETE)

2. The RegulatoryActionView must contain the following fields: 
    - name: ActionDate   type: DATE 
    - name: ActionType   type: STRING 
    - name: AuthorityName   type: STRING 
    - name: Company   type: Company 
    - name: Country   type: STRING 
    - name: Description   type: STRING 
    - name: PenaltyMillionUsd   type: DOUBLE 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing RegulatoryAction entity should be loaded from the relative URL: 
    "/RoleService/regulatoryaction/{id}"   (HTTP-GET) 
If a new RegulatoryAction entity has been created, the new entity should be posted to the relative URL: 
    "/RoleService/regulatoryaction"   (HTTP-POST) 
If an existing RegulatoryAction entity has been updated, the modified entity should be sent to the relative URL: 
    "/RoleService/regulatoryaction/{id}"   (HTTP-PUT) 
If an existing RegulatoryAction entity has to be deleted, the following relative URL should be called: 
    "/RoleService/regulatoryaction/{id}"   (HTTP-DELETE)

3. The RoleView must contain the following fields: 
    - name: RoleDescription   type: STRING 
    - name: RoleName   type: STRING 
An existing Role entity should be loaded from the relative URL: 
    "/RoleService/role/{id}"   (HTTP-GET) 
If a new Role entity has been created, the new entity should be posted to the relative URL: 
    "/RoleService/role"   (HTTP-POST) 
If an existing Role entity has been updated, the modified entity should be sent to the relative URL: 
    "/RoleService/role/{id}"   (HTTP-PUT) 
If an existing Role entity has to be deleted, the following relative URL should be called: 
    "/RoleService/role/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following RoleHistory columns: 
    - column: EndDate 
    - column: StartDate 
    - column: Role 
    - column: Person 
    - column: Notes 
    - column: OrganizationName 
The table should have the title "RoleHistorys" und the data must be loaded from the server with the following relative URL: 
    "/RoleService/rolehistory/role/{id}" 
Add a HTML table to the view with the following CompanyLeadership columns: 
    - column: Company 
    - column: Role 
    - column: StartDate 
    - column: Person 
    - column: EndDate 
The table should have the title "CompanyLeaderships" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/companyleadership/role/{id}"

4. The RoleHistoryView must contain the following fields: 
    - name: EndDate   type: DATE 
    - name: Notes   type: STRING 
    - name: OrganizationName   type: STRING 
    - name: Person   type: Person 
    - name: Role   type: Role 
    - name: StartDate   type: DATE 
The data source for the [Role] select control should be loaded from the relative URL: 
    "/RoleService/role"   (HTTP-GET) 
The data source for the [Person] select control should be loaded from the relative URL: 
    "/CompanyService/person"   (HTTP-GET) 
An existing RoleHistory entity should be loaded from the relative URL: 
    "/RoleService/rolehistory/{id}"   (HTTP-GET) 
If a new RoleHistory entity has been created, the new entity should be posted to the relative URL: 
    "/RoleService/rolehistory"   (HTTP-POST) 
If an existing RoleHistory entity has been updated, the modified entity should be sent to the relative URL: 
    "/RoleService/rolehistory/{id}"   (HTTP-PUT) 
If an existing RoleHistory entity has to be deleted, the following relative URL should be called: 
    "/RoleService/rolehistory/{id}"   (HTTP-DELETE)

5. The StockOwnershipView must contain the following fields: 
    - name: AsOfDate   type: DATE 
    - name: Company   type: Company 
    - name: Notes   type: STRING 
    - name: OwnershipPercent   type: DOUBLE 
    - name: OwnerType   type: STRING 
    - name: Person   type: Person 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
The data source for the [Person] select control should be loaded from the relative URL: 
    "/CompanyService/person"   (HTTP-GET) 
An existing StockOwnership entity should be loaded from the relative URL: 
    "/RoleService/stockownership/{id}"   (HTTP-GET) 
If a new StockOwnership entity has been created, the new entity should be posted to the relative URL: 
    "/RoleService/stockownership"   (HTTP-POST) 
If an existing StockOwnership entity has been updated, the modified entity should be sent to the relative URL: 
    "/RoleService/stockownership/{id}"   (HTTP-PUT) 
If an existing StockOwnership entity has to be deleted, the following relative URL should be called: 
    "/RoleService/stockownership/{id}"   (HTTP-DELETE)