Overview
Summary
Contact
Donate
Imprint
Prompt for the
SubscriptionPlanApp
Please create a React-JS application for the SubscriptionPlanModule. The application has to offer the following views for the user interface: 1. MembershipView 2. SubscriptionPlanView 3. SubsidiaryView 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 MembershipView must contain the following fields: - name: EndDate type: DATE - name: StartDate type: DATE - name: Status type: STRING - name: SubscriptionPlan type: SubscriptionPlan - name: UserAccount type: UserAccount The data source for the [SubscriptionPlan] select control should be loaded from the relative URL: "/SubscriptionPlanService/subscriptionplan" (HTTP-GET) The data source for the [UserAccount] select control should be loaded from the relative URL: "/UserProfileService/useraccount" (HTTP-GET) An existing Membership entity should be loaded from the relative URL: "/SubscriptionPlanService/membership/{id}" (HTTP-GET) If a new Membership entity has been created, the new entity should be posted to the relative URL: "/SubscriptionPlanService/membership" (HTTP-POST) If an existing Membership entity has been updated, the modified entity should be sent to the relative URL: "/SubscriptionPlanService/membership/{id}" (HTTP-PUT) If an existing Membership entity has to be deleted, the following relative URL should be called: "/SubscriptionPlanService/membership/{id}" (HTTP-DELETE) 2. The SubscriptionPlanView must contain the following fields: - name: Description type: STRING - name: EndDate type: DATE - name: MonthlyPrice type: STRING - name: Name type: STRING - name: PlanType type: STRING - name: ServiceSupply type: ServiceSupply - name: StartDate type: DATE The data source for the [ServiceSupply] select control should be loaded from the relative URL: "/ServiceSupplyService/servicesupply" (HTTP-GET) An existing SubscriptionPlan entity should be loaded from the relative URL: "/SubscriptionPlanService/subscriptionplan/{id}" (HTTP-GET) If a new SubscriptionPlan entity has been created, the new entity should be posted to the relative URL: "/SubscriptionPlanService/subscriptionplan" (HTTP-POST) If an existing SubscriptionPlan entity has been updated, the modified entity should be sent to the relative URL: "/SubscriptionPlanService/subscriptionplan/{id}" (HTTP-PUT) If an existing SubscriptionPlan entity has to be deleted, the following relative URL should be called: "/SubscriptionPlanService/subscriptionplan/{id}" (HTTP-DELETE) Add a HTML table to the view with the following Membership columns: - column: StartDate - column: SubscriptionPlan - column: EndDate - column: UserAccount - column: Status The table should have the title "Memberships" und the data must be loaded from the server with the following relative URL: "/SubscriptionPlanService/membership/subscriptionplan/{id}" 3. The SubsidiaryView must contain the following fields: - name: Company type: Company - name: Description type: STRING - name: EndDate type: DATE - name: Name type: STRING - name: ParentCompany type: Company - name: StartDate type: DATE The data source for the [ParentCompany] select control should be loaded from the relative URL: "/CompanyService/company" (HTTP-GET) The data source for the [Company] select control should be loaded from the relative URL: "/CompanyService/company" (HTTP-GET) An existing Subsidiary entity should be loaded from the relative URL: "/SubscriptionPlanService/subsidiary/{id}" (HTTP-GET) If a new Subsidiary entity has been created, the new entity should be posted to the relative URL: "/SubscriptionPlanService/subsidiary" (HTTP-POST) If an existing Subsidiary entity has been updated, the modified entity should be sent to the relative URL: "/SubscriptionPlanService/subsidiary/{id}" (HTTP-PUT) If an existing Subsidiary entity has to be deleted, the following relative URL should be called: "/SubscriptionPlanService/subsidiary/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint