Hi devs,
first, I’ve been working on a custom data entry form for tracker (2.22 and 2.23). I’ve customised the same form as programmes with and without registration, and I notice that in Tracker Capture everything is seemingly "magnified" by 25% or so compared to Event Capture (e.g. rows that are 35px high in EC are 44px in TC). Is there a reason for this? The way it is rendered in Event Capture seems more "normal" to me, whilst opening custom forms in Tracker Capture always make me think Chrome is set to zoom…
Second, in Tracker Capture, there seems to be no way of displaying "validation warnings" (defined through program rules) - could there be something similar to EC, with a "Validation warnings" widget? Similarly, while EC will highlight missing required fields when completing ("Required" in red), there is no indicator TC as to what field(s) are missing.
Hi devs,
first, I’ve been working on a custom data entry form for tracker (2.22 and 2.23). I’ve customised the same form as programmes with and without registration, and I notice that in Tracker Capture everything is seemingly "magnified" by 25% or so compared to Event Capture (e.g. rows that are 35px high in EC are 44px in TC). Is there a reason for this? The way it is rendered in Event Capture seems more "normal" to me, whilst opening custom forms in Tracker Capture always make me think Chrome is set to zoom…
Second, in Tracker Capture, there seems to be no way of displaying "validation warnings" (defined through program rules) - could there be something similar to EC, with a "Validation warnings" widget? Similarly, while EC will highlight missing required fields when completing ("Required" in red), there is no indicator TC as to what field(s) are missing.
Yes, we have been talking about the same, we need a way of showing the warnings in custom forms, and adding a widget like EC is perhaps the hottest option. Another one that was mentioned was adding them inside the form, somehow - for example as a small icon in or next to the input field. We are also discussing a use case for having validation errors that is triggered/shown when trying to complete the program stage. Maybe some warnings could be nice to show upon completion also - inside the dialog for confirming the completion for example.
···
10. mai 2016 kl. 15.45 skrev Olav Poppe <olav.poppe@me.com>:
Just a note that in 2.23 Tracker Capture you are not able to complete a program stage if required fields are missing. Each datavalue is saved once captured though and you are still able to close a form with only some fields captured. But at least the enforcement on completing a program stage does help.
first, I’ve been working on a custom data entry form for tracker (2.22 and 2.23). I’ve customised the same form as programmes with and without registration, and I notice that in Tracker Capture everything is seemingly “magnified” by 25% or so compared to Event Capture (e.g. rows that are 35px high in EC are 44px in TC). Is there a reason for this? The way it is rendered in Event Capture seems more “normal” to me, whilst opening custom forms in Tracker Capture always make me think Chrome is set to zoom…
Second, in Tracker Capture, there seems to be no way of displaying “validation warnings” (defined through program rules) - could there be something similar to EC, with a “Validation warnings” widget? Similarly, while EC will highlight missing required fields when completing (“Required” in red), there is no indicator TC as to what field(s) are missing.
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@hisp.org 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.
Hi,
thanks both. My challenge is that we have two fields, where the user needs to fill one of them. So we can’t make either of them required, and currently we can’t show a warning to remind users to fill in one of them (since we use a custom form). This should address this when implemented: https://blueprints.launchpad.net/dhis2/+spec/program-rules-error-on-completion
Markus, regarding widget vs inside form, I think there are pros and cons to both - but the main thing is that there is something! And it wouldn’t hurt if there was consistency between how this was handled in TC and EC.**Currently EC has a mix of both, with “required” labels in the form and warnings in the widget.
Just a note that in 2.23 Tracker Capture you are not able to complete a program stage if required fields are missing. Each datavalue is saved once captured though and you are still able to close a form with only some fields captured. But at least the enforcement on completing a program stage does help.
first, I’ve been working on a custom data entry form for tracker (2.22 and 2.23). I’ve customised the same form as programmes with and without registration, and I notice that in Tracker Capture everything is seemingly “magnified” by 25% or so compared to Event Capture (e.g. rows that are 35px high in EC are 44px in TC). Is there a reason for this? The way it is rendered in Event Capture seems more “normal” to me, whilst opening custom forms in Tracker Capture always make me think Chrome is set to zoom…
Second, in Tracker Capture, there seems to be no way of displaying “validation warnings” (defined through program rules) - could there be something similar to EC, with a “Validation warnings” widget? Similarly, while EC will highlight missing required fields when completing (“Required” in red), there is no indicator TC as to what field(s) are missing.
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@hisp.org 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.
