dhis2-devs team mailing list archive

[Lars Helge Øverland <larshelge@xxxxxxxxx>]

On Thu, Dec 5, 2013 at 12:48 AM, Juan M Alcántara Acosta <
jmalcantara@xxxxxxxxxxxxx> wrote:

> I agree in part and definitely prefer to assign access to org units just
> by selecting the parent rather than multiple units in the same branch. The
> requirement to select a number of children org units came from the
> specifications to be able to use the advance search option "all visible" in
> Find/Add Person. Back in august I started a conversation with Tran to
> request a way to limit the scope of the search to only the org units a user
> can access -Thank you Tran!- I'm not familiar with the use case that
> resulted in the current specification but if you ask me, I'd vote to modify
> this option to make it work with the selected parent and all the children
> :-)  -not the same as selected and bellow-. We need this to keep users from
> searching in all system org units and getting access to person records from
> different countries or org units out of their allowed scope of work.
>
> Sorry for the detour... back to the bug report. The tabular report is the
> only section of the system that misbehaves in the way the org unit tree is
> presented; data entry, visualizer, pivot tables, etc. all present the org
> unit tree correctly. I'm including two screen captures, one from our
> development server and another one from the Sierra Leone demo. To duplicate
> in the demo I created an account and selected National, District and PHU
> levels.
>
>
Hi Juan,

okay, I don't quite follow.. What is the difference between "selected
parent and all the children" vs "selected and below" ?