Integrated Operation Center - ID Tool - Angular Frontend Java Spring REST Backend Integration Challenge

Welcome to the "Integrated Operation Center - ID Tool - Angular Frontend Java Spring REST Backend Integration Challenge"

Overview

Client of this challenge is looking to revamp their current desktop application into a web application, as a part of this process - we are looking for the topcoder developer community’s help in developing the new, refreshing and modern web based application that will help Site Managers, Operators, Business Analysts and Admins with the ability:
- To view the list of meetings that were conducted/attended
- To view list of action items
- To view the LO/TO (lockout/tagout) of the assets

Challenge Requirements

We’ve run multiple challenges for this project so far to build the REST API and UI Prototype.

The APIs are documented in the following artefacts that are available in our repo.

• Swagger
• REST API Implementation

We’ve also built a UI Prototype using angular and bootstrap which we want to integrate with the provided backend APIs. Details about the prototype are available in the forums.

The final deliverable should be a Spring Boot project which can be run in a server.

The API to prototype mapping should be obvious from the Swagger & prototype pages, but if anything is not clear - please ask in the forums. If we find any discrepancies in the backend/ frontend from a mapping perspective, these will require to be fixed as part of this challenge.

Additional Requirements

Make sure that the following requirements are also covered in the integration.

• Meeting Sign-In 
  • My Meeting – This filter should only show the meetings the Current User Logged in’s meetings were he/she is the leader or the teacher.
  • All Meeting – This filter should show all the meetings (within an asset).
  • My Reports – This filter should show only the meetings that the current user logged in his/her reporting employees attended. 
  • Not Attended – Rename this to “My Attendance”
    • Update the related functionality with this option which more self-explanatory and easier to implement.
    • This filter should show only the meetings that the current user logged in has attended.
• LOTO
  • Filtered look – When in “Group 1” the only displayed items should be “Group Name 1” items. 
  • There will be unfiltered views in addition to the filtered views.
• Grid Sorting - Make sure that this is implemented in server side
• Searching - Make sure that this is implemented in server side
• Pagination - Make sure that this implemented in server side

Coding Standards - Frontend

• There should be no W3C errors or warnings in the frontend code
• All files & methods must be well documented

Coding Standards - Backend

• All files & methods must be well documented

Technology

• Java 8
• Spring REST
• Hibernate
• Spring MVC
• JSON
• SQL Server (v13.0.4451.0)
• Spring Framework 5.x
• Spring Boot 1.5.x
• Log4j
• Angular 5.x
• Bootstrap 4.x

Final Submission Guidelines

• Integrated project with backend API and prototype
• Demo video of how to configure and run your submission
• Configuration & Deployment guide to configure and run your submission
• If updates are made to any backend API which require Swagger changes, you will need to submit the updated swagger as well