dhis2-devs team mailing list archive

["Elmarie Claasen" <elmarie@xxxxxxxx>]

Calle,

 

Have you tried clearing the system cache after editing the user role? 

 

Regards,

 

Elmarie Claasen

Hisp logo

Project Manager

Health Information Systems Program

Tel:      041-367 1027

Cell:     082 374 2209

E-mail:  <mailto:elmarie@xxxxxxxx> elmarie@xxxxxxxx

Skype:  elmarie.claasen52 

 

 

This message and any attachments are subject to a disclaimer published at  <http://www.hisp.org/policies.html#comms_disclaimer> http://www.hisp.org/policies.html#comms_disclaimer .   Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission. 
If you cannot access the disclaimer, kindly send an email to  <mailto:disclaimer@xxxxxxxx> disclaimer@xxxxxxxx and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer. 

 

From: Dhis2-devs [mailto:dhis2-devs-bounces+elmarie=hisp.org@xxxxxxxxxxxxxxxxxxx] On Behalf Of Adebusoye Anifalaje
Sent: 06 July 2016 05:17 PM
To: Calle Hedberg
Cc: DHIS 2 developers
Subject: Re: [Dhis2-devs] Data capturer - Events: Authorisation privilege missing

 

Got it Calle.

 

I just tested locally here and it works fine. Using 

 

Version:

2.22

Build revision:

22067




  <https://baosystems.com/sites/all/themes/bao/images/logo.png> 

 Busoye Anifalaje (PhD)

Director of Services (Principal), BAO Systems

UK: +44 7901-740-757 | US: +1 682-307-0986|

 busoye@xxxxxxxxxxxxxx | http://www.baosystems.com <http://www.baosystems.com/>  |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007

 

On Wed, Jul 6, 2016 at 4:05 PM, Calle Hedberg <calle.hedberg@xxxxxxxxx> wrote:

Busoye,

 

As I said, we have tried adding EVERYTHING (every single permission) to the user role - it still does not work. The only way to make it work is by adding ALL (then it works even without any other permission set).

 

Giving us grey hair, this problem is....

 

Regards

calle

 

On 6 July 2016 at 17:02, Adebusoye Anifalaje <busoye@xxxxxxxxxxxxxx> wrote:

Okay Calle. 

 

Checked the permissions you set. Not sure but can you try adding Add/Update Tracked Entity Instance. Strictly speaking an event does not have an entity but each record might be conceived as an instance. Worth trying I think. If it works then you want to also add Delete Tracked Entity Instance.

 

Let's know if that helps.

 

Busoye




  <https://baosystems.com/sites/all/themes/bao/images/logo.png> 

 Busoye Anifalaje (PhD)

Director of Services (Principal), BAO Systems

UK: +44 7901-740-757 <tel:%2B44%207901-740-757>  | US: +1 682-307-0986 <tel:%2B1%20682-307-0986> |

 busoye@xxxxxxxxxxxxxx | http://www.baosystems.com <http://www.baosystems.com/>  |
Skype: busoye | 2900 K Street, Suite 404, Washington D.C. 20007

 

On Wed, Jul 6, 2016 at 3:51 PM, Calle Hedberg <calle.hedberg@xxxxxxxxx> wrote:

Busoye,

 

YES, the program is added to the role, and its sharing is set to public view and edit (with login).

 

We have found earlier dev threads about very similar problems, but all indications are that those were fixed in 2.21. We have tested the latest 2.22 and the latest 2.23 - no difference. The only way to make it work is either to include ALL with that user role, or else log in as superuser. All other authorisations do not work.

 

Regards

Calle

 

On 6 July 2016 at 15:07, Busoye Anifalaje <busoye@xxxxxxxx> wrote:

Hi Calle, 
Have you added the event program to the role. The ALL authority is not a summation of all other permissions but a special designation that provides access to grant access to all apps and privately created objects (with the exception of dashboards).

Hope that helps.

Cheers,
Busoye 

On 6 Jul 2016 2:00 p.m., "Calle Hedberg" <calle.hedberg@xxxxxxxxx> wrote:

Hi

 

Small correction: we have now ascertained that if the Data Capturer - Events have every single authorisation selected (except ALL), it does NOT work. If we on the other hand select ALL, then it works.

 

What is the difference between ALL and the sum of all individual authorisations?

 

regards

callee

 

On 6 July 2016 at 12:35, Calle Hedberg <calle.hedberg@xxxxxxxxx> wrote:

Hi,

 

We have an instance with an Event program and a user role called "Data Capturer - Events" with the following authorisations - but one or more is missing:

 

Add/Update event

Add/Update Tracked Entity

Add/Update Tracked Entity Data Value

Delete Data Value

Generate Min-Max Value

Run validation

See Browser Cache Cleaner module

See Dashboard Intergration Module

See even Capture Module

See Event Report Module

See Event Visualiser module

See GIS Module

See Pivot table module

See report module

See validation rule

 

Something is missing, though - when a data capturer opens the Event Capture app and selects an orgunit with a number of pre-existing events, nothing is showing. Also when selecting "Register event", all the drop-down option sets with a large number of options are blank.

 

If I add ALL to the user role, or if I add all the individual authorisations, everything works fine.

 

Two questions:

 

1. Can anybody see which authorisation(s) is/are missing in the list above?

 

2. Where can I find an overview of all authorisations in the system with a detailed explanation of (a) what exactly that authorisation provides access to and (b) what authorisations have an impact on which areas (routine data capture/use, event data capture/use, tracker data capture/use).

 

Best regards

Calle

 

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA 

Tel/fax (home): +27-21-685-6472 <tel:%2B27-21-685-6472> 

Cell: +27-82-853-5352 <tel:%2B27-82-853-5352> 

Iridium SatPhone: +8816-315-19119 <tel:%2B8816-315-19119> 

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************

 





 

-- 

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA 

Tel/fax (home): +27-21-685-6472 <tel:%2B27-21-685-6472> 

Cell: +27-82-853-5352 <tel:%2B27-82-853-5352> 

Iridium SatPhone: +8816-315-19119 <tel:%2B8816-315-19119> 

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************

 

 

_______________________________________________
Mailing list: https://launchpad.net/~dhis2-devs
Post to     : dhis2-devs@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~dhis2-devs
More help   : https://help.launchpad.net/ListHelp

 

This message and any attachments are subject to a disclaimer published at http://www.hisp.org/policies.html#comms_disclaimer.  Please read the disclaimer before opening any attachment or taking any other action in terms of this electronic transmission.  If you cannot access the disclaimer, kindly send an email to disclaimer@xxxxxxxx and a copy will be provided to you. By replying to this e-mail or opening any attachment you agree to be bound by the provisions of the disclaimer.





 

-- 

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA 

Tel/fax (home): +27-21-685-6472 <tel:%2B27-21-685-6472> 

Cell: +27-82-853-5352 <tel:%2B27-82-853-5352> 

Iridium SatPhone: +8816-315-19119 <tel:%2B8816-315-19119> 

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************

 

 





 

-- 

*******************************************

Calle Hedberg

46D Alma Road, 7700 Rosebank, SOUTH AFRICA 

Tel/fax (home): +27-21-685-6472 <tel:%2B27-21-685-6472> 

Cell: +27-82-853-5352 <tel:%2B27-82-853-5352> 

Iridium SatPhone: +8816-315-19119 <tel:%2B8816-315-19119> 

Email: calle.hedberg@xxxxxxxxx

Skype: calle_hedberg

*******************************************

 

 


-- 


*This message and any attachments are subject to a disclaimer published at 
http://www.hisp.org/policies.html#comms_disclaimer 
<http://www.hisp.org/policies.html#comms_disclaimer>.  Please read the 
disclaimer before opening any attachment or taking any other action in 
terms of this electronic transmission.  If you cannot access the 
disclaimer, kindly send an email to disclaimer@xxxxxxxx 
<disclaimer@xxxxxxxx> and a copy will be provided to you. By replying to 
this e-mail or opening any attachment you agree to be bound by the 
provisions of the disclaimer.*