Notes

1. bundles active/inactive - list API (role-based condition) (not to show inactive bundles for clinic/ group admins)
2. Bundles inactive/active - If a bundle is assigned to a client (Many to many map)
now we need a new class, where we will maintain (clientId, bundleId, bundleStatus)

UserSurveyBundle - userId + bundleId
New UserSurveyBundle - clientId + bundleId + status + bundleAssignDate ...

Conditions :
1. if bundle inactive/active - make bundle inactive in New UserSurveyBundle
2. bundleStatus table - active/ inactive
3. New UserSurveyBundle - based on this -- a list of surveys in IPAD (get active bundles)


3.Manual bundles - bundle assign date
Conditions :
We are not saving the bundle assign date!
LIST -> manual bundle -> start date === bundleAssignDate + ,,,, calu ( end date, overdue ,, ) - bundleStatus + fileStatus - insert records with this data.

4.Unassign bundles :
permanent removal and we have to re-assign if needed.
UserSurveyBundle - remove the record
bundleStatus & fileStatus - if bundleStatus is not COMPLETED - records delete.

5. Edit client - either bundles edit / edit gender / edit age :
I need two separate lists - deleted bundles & newly added bundle

if( deleted list is not empty){
1.delete from intermediate table
2. delete from bundleStatus & fileStatus - if bundleStatus is not COMPLETED - records delete.
indirectly it is bundle unassignment
}
if(new added bundle ! = empty){
1.add in intermediate table
2. add in bundleStatus & fileStatus
}

gender/age :

que : shall we delete older bundles? of older age/gender

delete all bundles for the user. ( default/ baseline/ manual / pushed)
1. in this case , deleted list wil be empty, but gender/ age is edited --- so,, we have to clear the intermediate table & bundleStatus & fileStatus & userSurveyAnswer and graph of the user.
bundleList != empty ==== [manually / manually pushed ]

que : intake date --- two months edit -- though default/ baseline bundles are assigned but they will not be visible to answer as the intake date is expired.
que : if a bundle is active for trigger 1 and then made inactive for trigger 2,,,, but in the window period of trigger 2 ,, it is made active again ... shall that bundle be displayed to the user if the window period is active ?
que : if a bundle is active for trigger 1 and then made inactive for trigger 2 and made active at trigger 3 ... should that trigger count 3 should be displayed as 3 or 2? If has to be displayed as 2, on what basis shall that be displayed , because there wil be no link for us to backtrack.
que : if a bundle is active for trigger 1 and then made inactive for trigger 2 and made inactive at trigger 3... but, I made it active in the 3rd trigger window period, so, will that bundle be displayed ?
and also , if the bundle is made inactive, should that bundle be hidden?

1. add new manually / manually pushed bundles of edited age/gender into an intermediate table ( from bundleList) - save
2. save -- as normal
3. recurring bundle will be considered by intake data only.