Overview
Summary
Contact
Donate
Imprint
Prompt for the
DeviceApp
Please create a React-JS application for the DeviceModule. The application has to offer the following views for the user interface: 1. ContentDistributionView 2. DeviceView 3. DeviceIntegrationView 4. PlaybackSessionView 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 ContentDistributionView must contain the following fields: - name: ContentTitle type: ContentTitle - name: DistributionType type: STRING - name: EndDate type: DATE - name: Notes 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) The data source for the [ContentTitle] select control should be loaded from the relative URL: "/ContentTitleService/contenttitle" (HTTP-GET) An existing ContentDistribution entity should be loaded from the relative URL: "/DeviceService/contentdistribution/{id}" (HTTP-GET) If a new ContentDistribution entity has been created, the new entity should be posted to the relative URL: "/DeviceService/contentdistribution" (HTTP-POST) If an existing ContentDistribution entity has been updated, the modified entity should be sent to the relative URL: "/DeviceService/contentdistribution/{id}" (HTTP-PUT) If an existing ContentDistribution entity has to be deleted, the following relative URL should be called: "/DeviceService/contentdistribution/{id}" (HTTP-DELETE) 2. The DeviceView must contain the following fields: - name: Category type: STRING - name: Manufacturer type: STRING - name: Name type: STRING An existing Device entity should be loaded from the relative URL: "/DeviceService/device/{id}" (HTTP-GET) If a new Device entity has been created, the new entity should be posted to the relative URL: "/DeviceService/device" (HTTP-POST) If an existing Device entity has been updated, the modified entity should be sent to the relative URL: "/DeviceService/device/{id}" (HTTP-PUT) If an existing Device entity has to be deleted, the following relative URL should be called: "/DeviceService/device/{id}" (HTTP-DELETE) Add a HTML table to the view with the following DeviceIntegration columns: - column: Notes - column: EndDate - column: ServiceSupply - column: Device - column: StartDate - column: IntegrationType The table should have the title "DeviceIntegrations" und the data must be loaded from the server with the following relative URL: "/DeviceService/deviceintegration/device/{id}" Add a HTML table to the view with the following PlaybackSession columns: - column: EndedAt - column: DurationSeconds - column: UserProfile - column: ContentTitle - column: StartedAt - column: Device - column: WasCompleted The table should have the title "PlaybackSessions" und the data must be loaded from the server with the following relative URL: "/DeviceService/playbacksession/device/{id}" 3. The DeviceIntegrationView must contain the following fields: - name: Device type: Device - name: EndDate type: DATE - name: IntegrationType type: STRING - name: Notes 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) The data source for the [Device] select control should be loaded from the relative URL: "/DeviceService/device" (HTTP-GET) An existing DeviceIntegration entity should be loaded from the relative URL: "/DeviceService/deviceintegration/{id}" (HTTP-GET) If a new DeviceIntegration entity has been created, the new entity should be posted to the relative URL: "/DeviceService/deviceintegration" (HTTP-POST) If an existing DeviceIntegration entity has been updated, the modified entity should be sent to the relative URL: "/DeviceService/deviceintegration/{id}" (HTTP-PUT) If an existing DeviceIntegration entity has to be deleted, the following relative URL should be called: "/DeviceService/deviceintegration/{id}" (HTTP-DELETE) 4. The PlaybackSessionView must contain the following fields: - name: ContentTitle type: ContentTitle - name: Device type: Device - name: DurationSeconds type: LONG - name: EndedAt type: DATE - name: StartedAt type: DATE - name: UserProfile type: UserProfile - name: WasCompleted type: BOOL The data source for the [UserProfile] select control should be loaded from the relative URL: "/UserProfileService/userprofile" (HTTP-GET) The data source for the [Device] select control should be loaded from the relative URL: "/DeviceService/device" (HTTP-GET) The data source for the [ContentTitle] select control should be loaded from the relative URL: "/ContentTitleService/contenttitle" (HTTP-GET) An existing PlaybackSession entity should be loaded from the relative URL: "/DeviceService/playbacksession/{id}" (HTTP-GET) If a new PlaybackSession entity has been created, the new entity should be posted to the relative URL: "/DeviceService/playbacksession" (HTTP-POST) If an existing PlaybackSession entity has been updated, the modified entity should be sent to the relative URL: "/DeviceService/playbacksession/{id}" (HTTP-PUT) If an existing PlaybackSession entity has to be deleted, the following relative URL should be called: "/DeviceService/playbacksession/{id}" (HTTP-DELETE)
Copy prompt
Overview
Summary
Contact
Donate
Imprint