CRM - Search and Validation Angular Application Updates

Welcome to the “CRM - Search and Validation Angular Application Update Challenge”. We are currently building an internal web application for a client. This application is divided into frontend and backend.

 

CONTEXT

PROJECT CONTEXT

The client has requested to build a full stack application that involves both the backend REST API (Nest.JS) and a frontend application (Angular 9). This application will allow users to engage in the search and validation process for new income calls from clients.
 

CHALLENGE CONTEXT

The goal of this challenge is to fix some issues and feedback from client.
 

CHALLENGE DETAILS

Technology and Framework

• Angular 9+
• Typescript
• NodeJs 12.x

Requirements

• Add file origin dropdown:

• Dropdown values (make it configurable as variables in application):
  • Phone
  • Email
  • Letter
  • Fax
  • Web
  • BlueCard
  • Outbound Call
  • Walk In
• Default value for dropdown is Phone
• Add query parameters to the default Angular routing
  • valGuid
  • callerName
  • callbackNumber
• If both callerName and callbackNumber are provided in query parameters, populate the correspondig fields in the header
• If valGuid is provided:
  • call the new backend endpoint "GET /validations/operations/search?valGuid=<valGuid>"
  • The response should be used to populate the dropdown (must be case insensitive, ie. if backend returns phone, dropdown should be Phone)
  • If the response from the backend is "phone" dropdown must be read-only
• Unit test for this new endpoint is in scope
• Fix the following issues:
  • Phone Number:
    1. Current angular web app only allows following format “123-456-7890”
    2. Callback Number needs to be unformatted text field allow more than standard characters/alpha numeric and numeric. Number should NOT be masked.
    3. This will allow CXAs to enter multiple callback numbers as well as extensions
       1. Examples
          1. 123-456-7890
          2. 1234567890
          3. 123-456-7890 ext 112
          4. 1234567890 ext 112
          5. 123.456.7890 ext 112
          6. 123-456-7890 ext
  • HIPAA Matrix
    1. HIPAA matrix fields will need to align with requirements
    2. Example: member search, caller = non-member, relationship to policy holder = non-covered spouse, HIPAA options are duplicated
    3. Additional information can be found in the forum
  • Plan to plan + non-member shows two types of dropdown arrows next to sections/accordion to validate. One a carrot, other is a triangle filled in. This was actually a font/load error on the mockup when uploaded on UX side. Please use the same carrot icon that is not the filled in triangle.
  • Search results should default to 50 results. Currently defaults to 5.
  • Have the ability to deselect a birthdate once it is selected, and the clear search button does not remove the data.
  • Search criteria clear:
    1. When the user clicks “clear search” the app clears the caller name and callback number. These two fields should remain intact.

Final Submission Guidelines

• Updated frontend code