Claims Management - Admin Screens Part 1

Welcome to Claims Management - Admin Screens Part 1 Contest. This is the second in a series of contests aimed at creating the UI Prototype for a Claims Management application.

 

Contest Details

The requirement is straightforward - create the UI Prototype for the provided designs. Only the following screens are in scope:

• Login

• System Configuration

• Queue Management

• Reference Data

• Project Configuration

 

In the contest forum, we will share with you the designs that you can use to create the UI prototype. Additionally, we will also be sharing the initial code with you that you need to work with. Finally, we will share a document with you that will describe all the pages in scope

 

Kindly note that in addition to creating the screens that match the design, you will also make API calls. There are actions on the pages that will require you to make API calls and in some cases, display the responses from these API calls. We will share with you the mock json server that you can make use of during your development.

 

Points To Note

• Kindly note that we will be running another parallel contest that will be using the same code base. Thus, when making changes relevant to this contest, you are expected to only carry out the changed necessary for this contest and not make changes elsewhere, that may cause undesired conflicts during merge

• It is thus essential that you build the screens component wise and then add the necessary components in your container (page).

• The initial code is using Angular (latest version) and is built using Angular CLI. You need to create the prototype using the same. Additionally, we also have ng-bootstrap which you need to make use of.

• The screens need to work on IE11, latest Edge, Google Chrome and Firefox browsers for desktop. Only Desktop is in scope. No mobile or tab versions exist.

• The width of the pages is fluid. It will expand and contract based on the screen size and occupy full width

• You are expected to follow best practices in Angular development

• Use texts wherever possible. Images are only for icons and logos.

• Ensure your submission has no lint errors

Final Submission Guidelines

Zip your changes and upload it to topcoder. Note that the winner will be asked to assist with the merge of the submissions from the parallel contests once they are in.