User Management – Add ANM and CHO logins with roles and ASHA mapping (Testing & Prod), and reconcile shared data against Prod

XMLWordPrintable

    • Admin
    • All

      Background / Context

      Your notes say to add ANM and CHO logins "as well", which implies a user/login setup for ASHAs is already in scope. The data for this activity has been shared and needs to be compared against Prod data.
      [TBD/CLARIFICATION REQUIRED: the parent ticket or activity this extends, and what the "data shared" is.]

      Problem Statement

      • ANM and CHO users have no logins, roles, or mapping to their concerned ASHAs in Testing and Prod.
      • The shared data has not yet been checked against Prod data, so gaps are unknown.

      Current Behaviour

      [TBD/CLARIFICATION REQUIRED: not stated in the notes. Confirm whether ANM/CHO logins exist in either environment and whether ASHA logins and mapping are already done.]

      Expected Behaviour / Requirement

      1. Create logins for ANM and CHO users.
      2. Assign the correct role to each ANM and CHO user.
      3. Map each ANM and CHO user to their concerned ASHA(s).
      4. Do the above in both Testing and Prod.
      5. Compare the shared data with the Prod data, validate any gaps (anything missing), and report the findings.

      User Story

      As an operations/admin user, I want ANM and CHO users created with roles and linked to their concerned ASHAs, and the shared data reconciled against Prod, so that these users can log in with the right access and any missing data is identified.

      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.
      • Given the shared data and the Prod data, when the comparison is run, then a report lists every record that is missing or mismatched.
      • Given gaps are found, then they are reported with the affected records identified.

      Business Rules / Validations

      • ANM and CHO must be mapped to the concerned ASHA.
      • Roles must be assigned to each ANM and CHO login.
      • [TBD/CLARIFICATION REQUIRED: mapping cardinality (one ANM/CHO to many ASHAs, or the reverse) and the rule for identifying the "concerned" ASHA.]
      • [TBD/CLARIFICATION REQUIRED: login ID and password format.]

      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.
      • Access to Prod data for the comparison.

      Impact / Affected Areas

      • User/Employee Master (logins, roles).
      • ASHA-ANM-CHO mapping.
      • Testing and Prod environments.

      Out of Scope

      Not stated in the notes. [TBD/CLARIFICATION REQUIRED]

      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 the gap report against a sample of records.
      • Verify that no existing ASHA logins or mappings change as a side effect.

      Open Questions / Clarifications (required before development)

      1. What does "the data shared" refer to (file, source, owner)?
      2. What are the exact role names for ANM and CHO?
      3. What is the mapping rule between ANM/CHO and ASHA?
      4. Who owns the Prod change, and is any approval needed before running it in Prod?
      5. What format and recipient does the gap report need?

              Assignee:
              Unassigned
              Reporter:
              Shivani Garg
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: