Prompt for the CompanyApp

Please create a React-JS application for the CompanyModule. The application  has to offer the following views for the user interface: 
    1. CompanyView 
    2. ContentDealView 
    3. PersonRoleView 
    4. PoliticalActionCommitteeView 
    5. RegulatoryEventView 
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 CompanyView must contain the following fields: 
    - name: CountryOfOrigin   type: STRING 
    - name: FoundedDate   type: DATE 
    - name: HeadquartersCity   type: STRING 
    - name: HeadquartersCountry   type: STRING 
    - name: HeadquartersRegion   type: STRING 
    - name: Industry   type: STRING 
    - name: LegalName   type: STRING 
    - name: Name   type: STRING 
    - name: Website   type: STRING 
An existing Company entity should be loaded from the relative URL: 
    "/CompanyService/company/{id}"   (HTTP-GET) 
If a new Company entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/company"   (HTTP-POST) 
If an existing Company entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/company/{id}"   (HTTP-PUT) 
If an existing Company entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/company/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following Headquarters columns: 
    - column: Country 
    - column: Region 
    - column: AddressLine 
    - column: City 
    - column: Company 
    - column: EndDate 
    - column: StartDate 
The table should have the title "Headquarterss" und the data must be loaded from the server with the following relative URL: 
    "/CountryService/headquarters/company/{id}" 
Add a HTML table to the view with the following LawsuitParty columns: 
    - column: Lawsuit 
    - column: Company 
    - column: Role 
The table should have the title "LawsuitPartys" und the data must be loaded from the server with the following relative URL: 
    "/ContentTypeService/lawsuitparty/company/{id}" 
Add a HTML table to the view with the following ServiceSupply columns: 
    - column: Url 
    - column: Company 
    - column: LaunchDate 
    - column: Description 
    - column: Type 
    - column: Name 
    - column: Status 
The table should have the title "ServiceSupplys" und the data must be loaded from the server with the following relative URL: 
    "/ServiceSupplyService/servicesupply/company/{id}" 
Add a HTML table to the view with the following ContentDeal columns: 
    - column: DealType 
    - column: Currency 
    - column: ProductionCompany 
    - column: Name 
    - column: Notes 
    - column: EndDate 
    - column: Company 
    - column: StartDate 
    - column: ValueAmount 
The table should have the title "ContentDeals" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/contentdeal/company/{id}" 
Add a HTML table to the view with the following PersonRole columns: 
    - column: EndDate 
    - column: Person 
    - column: StartDate 
    - column: Company 
    - column: RoleName 
The table should have the title "PersonRoles" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/personrole/company/{id}" 
Add a HTML table to the view with the following RecommendationAlgorithm columns: 
    - column: Description 
    - column: Name 
    - column: RetiredDate 
    - column: Company 
    - column: IntroducedDate 
The table should have the title "RecommendationAlgorithms" und the data must be loaded from the server with the following relative URL: 
    "/RecommendationAlgorithmService/recommendationalgorithm/company/{id}" 
Add a HTML table to the view with the following RegulatoryEvent columns: 
    - column: Company 
    - column: Name 
    - column: Description 
    - column: EventDate 
    - column: Country 
The table should have the title "RegulatoryEvents" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/regulatoryevent/company/{id}" 
Add a HTML table to the view with the following Subsidiary columns: 
    - column: ParentCompany 
    - column: EndDate 
    - column: Name 
    - column: Description 
    - column: Company 
    - column: StartDate 
The table should have the title "Subsidiarys" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionPlanService/subsidiary/parentcompany/{id}" 
Add a HTML table to the view with the following Subsidiary columns: 
    - column: ParentCompany 
    - column: EndDate 
    - column: Name 
    - column: Description 
    - column: Company 
    - column: StartDate 
The table should have the title "Subsidiarys" und the data must be loaded from the server with the following relative URL: 
    "/SubscriptionPlanService/subsidiary/company/{id}" 
Add a HTML table to the view with the following PoliticalActionCommittee columns: 
    - column: Purpose 
    - column: Name 
    - column: Company 
    - column: FormationDate 
    - column: Acronym 
The table should have the title "PoliticalActionCommittees" und the data must be loaded from the server with the following relative URL: 
    "/CompanyService/politicalactioncommittee/company/{id}" 
Add a HTML table to the view with the following Investment columns: 
    - column: Country 
    - column: Company 
    - column: StartDate 
    - column: Amount 
    - column: EndDate 
    - column: Currency 
    - column: Description 
The table should have the title "Investments" und the data must be loaded from the server with the following relative URL: 
    "/CountryService/investment/company/{id}"

2. The ContentDealView must contain the following fields: 
    - name: Company   type: Company 
    - name: Currency   type: STRING 
    - name: DealType   type: STRING 
    - name: EndDate   type: DATE 
    - name: Name   type: STRING 
    - name: Notes   type: STRING 
    - name: ProductionCompany   type: ProductionCompany 
    - name: StartDate   type: DATE 
    - name: ValueAmount   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
The data source for the [ProductionCompany] select control should be loaded from the relative URL: 
    "/CountryService/productioncompany"   (HTTP-GET) 
An existing ContentDeal entity should be loaded from the relative URL: 
    "/CompanyService/contentdeal/{id}"   (HTTP-GET) 
If a new ContentDeal entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/contentdeal"   (HTTP-POST) 
If an existing ContentDeal entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/contentdeal/{id}"   (HTTP-PUT) 
If an existing ContentDeal entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/contentdeal/{id}"   (HTTP-DELETE) 
Add a HTML table to the view with the following ContentDealTitle columns: 
    - column: ContentDeal 
    - column: ContentTitle 
    - column: Notes 
The table should have the title "ContentDealTitles" und the data must be loaded from the server with the following relative URL: 
    "/PersonService/contentdealtitle/contentdeal/{id}"

3. The PersonRoleView must contain the following fields: 
    - name: Company   type: Company 
    - name: EndDate   type: DATE 
    - name: Person   type: Person 
    - name: RoleName   type: STRING 
    - name: StartDate   type: DATE 
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: 
    "/PersonService/person"   (HTTP-GET) 
An existing PersonRole entity should be loaded from the relative URL: 
    "/CompanyService/personrole/{id}"   (HTTP-GET) 
If a new PersonRole entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/personrole"   (HTTP-POST) 
If an existing PersonRole entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/personrole/{id}"   (HTTP-PUT) 
If an existing PersonRole entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/personrole/{id}"   (HTTP-DELETE)

4. The PoliticalActionCommitteeView must contain the following fields: 
    - name: Acronym   type: STRING 
    - name: Company   type: Company 
    - name: FormationDate   type: DATE 
    - name: Name   type: STRING 
    - name: Purpose   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
An existing PoliticalActionCommittee entity should be loaded from the relative URL: 
    "/CompanyService/politicalactioncommittee/{id}"   (HTTP-GET) 
If a new PoliticalActionCommittee entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/politicalactioncommittee"   (HTTP-POST) 
If an existing PoliticalActionCommittee entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/politicalactioncommittee/{id}"   (HTTP-PUT) 
If an existing PoliticalActionCommittee entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/politicalactioncommittee/{id}"   (HTTP-DELETE)

5. The RegulatoryEventView must contain the following fields: 
    - name: Company   type: Company 
    - name: Country   type: Country 
    - name: Description   type: STRING 
    - name: EventDate   type: DATE 
    - name: Name   type: STRING 
The data source for the [Company] select control should be loaded from the relative URL: 
    "/CompanyService/company"   (HTTP-GET) 
The data source for the [Country] select control should be loaded from the relative URL: 
    "/CountryService/country"   (HTTP-GET) 
An existing RegulatoryEvent entity should be loaded from the relative URL: 
    "/CompanyService/regulatoryevent/{id}"   (HTTP-GET) 
If a new RegulatoryEvent entity has been created, the new entity should be posted to the relative URL: 
    "/CompanyService/regulatoryevent"   (HTTP-POST) 
If an existing RegulatoryEvent entity has been updated, the modified entity should be sent to the relative URL: 
    "/CompanyService/regulatoryevent/{id}"   (HTTP-PUT) 
If an existing RegulatoryEvent entity has to be deleted, the following relative URL should be called: 
    "/CompanyService/regulatoryevent/{id}"   (HTTP-DELETE)