Issue with event form activation after beneficiary transfer between organisational units on mobile devices

Support - Assistance technique
1

Hello Team,

I would like to report a potential issue related to the behavior of event forms on mobile devices.

We have encountered a problem where, after transferring a beneficiary from one organisational unit to another, the event form becomes inactive (all fields are disabled). The form remains inactive until the user manually selects their organisational unit from the list.

However, the beneficiary already belongs to the user’s organisational unit, and the correct organisational unit should be set by default.

Could you please confirm whether this is a known issue and if there are any plans to address it in future releases?

Steps to reproduce:

  1. Open the DHIS2 mobile application on a tablet
  2. Select a beneficiary who has been transferred to your organisational unit
  3. Open the event data entry form
  4. Observe that all fields are disabled until the user manually selects their organisational unit

We would appreciate any clarification or guidance on this matter.

2

Hi @Dmytro.D

Welcome to the DHIS2 Community of Practice!

Thank you for your post, it has been triaged to @dhis2-android team and they’re having a look. Meanwhile, may I ask what is the version of the DHIS2 android Capture app that you are using?

Thank you!

3

Hi, AL-Gassim Sharaf Addin!

Thank you!
The version of Android app is: 3.3.1.

Best regards,
Dmytro.

4

Hi @Dmytro.D,

I suspect that behavior you described might be connected to this reported bug.

The problem is that the ‘Transfer TEI’ function does not actually completely transfer a TEI. You still need to go to user settings and grant at least ‘Search Access’ to the original OU, don’t you? Otherwise, the recipient user will not be able to see the TEI, even after a Data/Metadata sync. And yes, it is very annoying. For both - admin and end-user

5

Hello @Dmytro.D, @m.siusko,

This ticket has been partially fixed in version 3.4.0 (to be released in May). We can say there are two parts:

  • The transferred TEI is not visible for the receiving user unless the original orgunit belongs to the user’s search scope → this has been solved in 3.4.0.
  • The transferred TEI is still visible for the user that transferred the TEI out → this is still pending.

Sorry for the inconvenience. I hope version 3.4.0 solves the main problem with this issue, I will appreciate your feedback when 3.4.0 is out.

6

Hi Viktor!
Thank you for your reply!
This is very good news!