-
Type:
Task
-
Resolution: Unresolved
-
Priority:
Low
-
Affects Version/s: None
-
FLW Sprint 55, FLW Sprint 56
-
Admin
-
All
Background / Context
ANM and CHO logins need to be added as well, alongside the ASHA setup that is already in scope. This implies a user/login setup for ASHAs already exists as an activity
Problem Statement
ANM and CHO users have no logins, roles, or mapping to their concerned ASHAs in Testing and Prod.
Expected Behaviour / Requirement
- Create logins for ANM and CHO users.
- Assign the correct role to each ANM and CHO user.
- Map each ANM and CHO user to their concerned ASHA(s).
- Do the above in both Testing and Prod.
User Story
As an operations/admin user, I want ANM and CHO users created with roles and linked to their concerned ASHAs, so that these users can log in with the right access in Testing and Prod.
Acceptance Criteria
- Given the shared ANM and CHO data, when the setup is done, then each ANM and CHO user has a login in Testing and in Prod.
- Given a created ANM or CHO login, when it is checked, then the correct role is assigned.
- Given an ANM or CHO user, when mapping is done, then the user is linked to the concerned ASHA(s) in both environments.
Business Rules / Validations
- ANM and CHO must be mapped to the concerned ASHA.
- Roles must be assigned to each ANM and CHO login.
- CLARIFICATION REQUIRED: mapping cardinality (one ANM/CHO to many ASHAs, or the reverse) and the rule for identifying the "concerned" ASHA.]
Dependencies
- The shared data file/source for ANM, CHO, and ASHA mapping.
- ASHA records and logins already existing in both environments.
- Role definitions for ANM and CHO.
Impact / Affected Areas
- User/Employee Master (logins, roles).
- ASHA-ANM-CHO mapping.
- Testing and Prod environments.
QA / Testing Considerations
- Log in as an ANM and a CHO in Testing and verify the role and linked ASHA(s).
- Repeat the check in Prod.
- Verify that no existing ASHA logins or mappings change as a side effect.