You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a supervisor, I should be able to approve forms filled by ASHAs
AC:
Being able to order the user groups in hierarchial way/similar levels - higher - more power, lower - less, same level - similar power
When approval enabled for atleast one form of User subject type: As a user at a higher level, based on the below criteria decide to sync user forms of lower level users other than the self forms:
If user is at lower address level and
([All address levels of lower level user belong to higher level user] or [when a user at lower level assigned to user at higher level])
Reset sync for below cases:
- When address removed/added from/to user's catchment
- When catchment of user changes
- When a new user added/removed to one of the user groups at lower level - reset sync for all higher level users
- When catchment of user at one of the lowest address level changes - reset sync for all higher level users
- When address removed/added from/to catchment of a user at one of the lower address levels - reset sync for all higher level users
- When level of user group is changed
- when approval enabled/disabled for any form of user subject type
Points of discussion:
All address levels of lower level user belong to higher level user - some optimisation table/tree structure for this
References: Link 1Link 2
Is it based on just subjectTypeUuid or also based on user group uuid - to minimise the data that reset sync would involve
Add a tab called 'About' to edit level, name, and display audit details.
Aprroachers:
hierarchy
location - a, b, c, d , user 2 - b, c,d,e - is needed - handle,
assignment -
Are there any usecases where they need to see the forms when clicked on Search.
The text was updated successfully, but these errors were encountered:
As a supervisor, I should be able to approve forms filled by ASHAs
AC:
- When address removed/added from/to user's catchment
- When catchment of user changes
- When a new user added/removed to one of the user groups at lower level - reset sync for all higher level users
- When catchment of user at one of the lowest address level changes - reset sync for all higher level users
- When address removed/added from/to catchment of a user at one of the lower address levels - reset sync for all higher level users
- When level of user group is changed
- when approval enabled/disabled for any form of user subject type
Points of discussion:
References: Link 1 Link 2
Aprroachers:
The text was updated successfully, but these errors were encountered: