Tasks: multi-note system, claims-first viewer dropdown, TaskNote schema
This commit is contained in:
parent
a583d76fc7
commit
4aa19e6a21
20 changed files with 1478 additions and 388 deletions
51
dev/Horizon_NewFeatures.md
Normal file
51
dev/Horizon_NewFeatures.md
Normal file
|
|
@ -0,0 +1,51 @@
|
|||
# Horizon
|
||||
|
||||
This is a web application that syncs insurance policy data from an insurance brokerage's line of business system to a local database (postgres) and then allows for additional functionality:
|
||||
|
||||
- Client Filtering
|
||||
|
||||
- Designation
|
||||
|
||||
- Claims Assignment
|
||||
|
||||
- AE
|
||||
|
||||
- Policy Grouping
|
||||
|
||||
- Groups don't cross clients, they are meant to align work tasks in an efficient manner. For example pulling a clients credit report is a per client task not a per policy
|
||||
|
||||
-
|
||||
|
||||
- Task Assignment
|
||||
|
||||
- Policies may need to retain individual tasks even if they are a member group.
|
||||
|
||||
- Tasks should be able to be assigned to a policy group or individual policy
|
||||
|
||||
- Tasks should be automatically assigned based on a date trigger: Group Date, or Policy Expiration Date
|
||||
|
||||
- Tasks should only be assigned automatically after a policy exists in the system for 20 days
|
||||
|
||||
- There should be a manual assignment in the ui that let's users assign tasks en masse using filters (policies for client A, new policies with no assignment, or just manual checkbox selection of multiple policies)
|
||||
|
||||
- Logging
|
||||
|
||||
- Authentication
|
||||
|
||||
- Task Activities
|
||||
|
||||
- Assignment
|
||||
|
||||
- Changes
|
||||
|
||||
- Removal
|
||||
|
||||
- Completion
|
||||
|
||||
- User Activities
|
||||
|
||||
- Creation / Deletion
|
||||
|
||||
- Role Change (Admin/Manager/Advocate)
|
||||
|
||||
|
||||
Loading…
Add table
Add a link
Reference in a new issue