dhis2-devs team mailing list archive

[Sam Johnson <samuel.johnson@xxxxxxxxxx>]

Hi Abyot,

When you say “users have no control”, do you mean admin users, or data
capture users?

My understanding is that admin users can control this by having
different roles, and only giving the relevant ones this authority.  They
would only assign the role if they want enforce users to being able to
search all tracked entity instances – eg they want to avoid the same
patient ending up with duplicate records in different regions, simply
because one region’s users weren’t able to find the other region’s
original patient record.  (For us, ensuring everyone shares a single
patient record is very important.)

And data capture users should still have control over their searches –
even if they’re given this authority, they can still go into advanced
search, and use the tree to narrow down the tree of all org units to
just show patients from a particular district or facility.

I think it’s really useful keeping this authority – it is effectively a
shortcut which saves admins from having to individually assign each user
the top-level org unit as a ‘search org unit’ (and making this a role
rather than a user-by-user setting will reduce the number of manual
setup errors, which will in turn reduce the risk of duplicate tracked
entity instances).  It also makes managing security much easier/safer –
if there’s a role that we decide shouldn’t be able to search all
patients after all, we can just remove this authority from that role;
without this authority, we’d have to go into potentially hundreds of
individual user records, manually re-assigning each user’s ‘search org
units’ to match their data capture org units.

>From my perspective, the current design is actually quite good – it just
needs this bug fixed.

Cheers, Sam.

PS – the one tiny tweak I’d suggest would be to move the ‘search org
units’ setting to the same place as the ‘data capture org units’ and the
‘data output org units’, ie the user management screen, so we can see
them all side-by-side (which is important, because my understanding is
that in the absence of a specific ‘search org units’ setting, DHIS2 will
use the ‘data capture org units’ by default).

-- 
You received this bug notification because you are a member of DHIS 2
developers, which is subscribed to DHIS.
https://bugs.launchpad.net/bugs/1625143

Title:
  The role/authority ‘Search tracked entity in all Org Units’  is not
  working, and even with this authority, a search will return only
  tracked entity instances that are registered/enrolled within user's
  own assigned org units

Status in DHIS:
  New

Bug description:
  Hi all,

  The ‘search tracked entity instance in all Org Units’ authority
  doesn’t appear to be working in 2.24 – see section 26.2 of the 2.24
  User Guide for details of this authority.  (This feature has been
  documented for quite some time now, but I haven’t yet had a chance to
  check whether or not it’s working in earlier versions of DHIS2.)  Even
  after being given a role containing this authority, users do not
  appear to be able to search for tracked entity instances outside of
  their assigned ‘data capture’ Org Units.

  
  To reproduce this in the 2.24 stable demo:

  1. While logged in as ‘Admin’, go to ‘Tracker Capture’, select ‘MNCH /
  PNC (Adult Woman)’, and select the Njandama MCHP org unit.

  2. Type ‘Sarah’ in the search box – it should return a record for
  Sarah Thompson registered at Ngelehun CHC.

  3. Go to the User app, and update the role ‘MNCH / PNC (Adult Woman) program’ to include the following authorities:
  - Add/update tracked entity data value
  - Add/update tracked entity instance
  - Delete tracked entity data value
  - Delete tracked entity instance
  - Search tracked entity instance
  - Search tracked entity instance in All Org Units
  - See browser cache cleaner module
  - See dashboard integration module
  - See Tracker Capture Module

  4. Create a new user with just this role, and give it only the
  Njandama MCHP Org Unit.

  5. Log out and back in again with this new user.

  6. Go to ‘Tracker Capture’, select the Njandama MCHP Org Unit (it
  should be the only one showing), and select the ‘MNCH / PNC’ program.

  7. Type ‘Sarah’ in the search box – no records are returned; click to
  show ‘detailed search’, and only the Njandama Org Unit is showing
  (rather than the wider OU tree mentioned in the documentation),
  meaning this user is not able to search for tracked entity instances
  registered/enrolled at Ngelehun CHC.

  
  Tested on DHIS2 2.24 stable demo (revision fff20a3); Chrome version 53.0.2785.116 (64-bit); Mac OSX 10.11.6 (15G1004)

To manage notifications about this bug go to:
https://bugs.launchpad.net/dhis2/+bug/1625143/+subscriptions