I am experiencing some issues with a Tracker configuration and the few workaround that I have tried also proves unsuccessful. I am using 2.40 and also testing on 2.41.3.
Capture App does not support Program Rule to Hide field (without deleting existing data for fields being hidden). Tracker capture app behaviour for hide field included not removing the existing captured values but this is back in Capture app. Is this by design or still coming feature for Capture or a bug?
To circumvent the above we decided to created Enrollment Sections but the program rule to hide sections does not appear to support hiding sections under Enrollment (as only sections in events show up in the dropdown list).
When an Event Data Element called “Is this a true Signal” has a TRUE value to update the TEA called “Event” with a TRUE value and to assign value “Event Verified” to Signal/Event Status but this does not update correctly.
Related to the above when you view the Enrollment you still see previous value but when editing the enrollment you see that the Event/Signal Status is “Verified” but only active when saved. We do not want the user to have to open the Enrollment again to update the TEA values.
Assistance with these would be greatly appreciated.
We also had an issue when trying to hide fields while keeping the value.
We found that hiding secions instead of fields, allowed us to keep the values of the fields of the section with Capture App, and Android application, while they were hidden to the user.
I understand this does not work in your case because you want to hide enrollement section and not program Stage Section.
However, from what you state about the previous behaviour of Tracker Capture App, I would be interested to know from the development team about the supposed beahviour in the future for both hide field and hide section: Are they supposed to blank the values, or to keep it in the 3 applications (Capture App, Tracker Capture App and Android Application).
If this is supposed to change in the future, we will need to find another way to hide sections while keeping the values.
Thanks for your response. I find it interesting that one can hide a section in the event but not in enrollment, yet you can create a section in enrollment. Hopefully someone will provide some clarity to your questions as well as they are certainly valid for future consideration.
I am not sure I was talking exactly about the same thing here.
Elmarie wants to know if we can hide a section from enrollment form using progra Rules.
My associated question is:
When we hide a section, all data elements keep their values if they have been assigned befoire.
When we hide a field, the value is blanked out.
It seems that before, with tracker Capture, the value was still assinged to the data element, even when the DE was hidden by a PR.
But In capture app, the data element is blanked when hiding it by PR.
The main question si to know if the normal behaviour when hiding a field or a section is to blank the value or to keep it. In order to know if the behaviour will change during next releases and anticipate if we need to change the configuration.
Firstly I think I highlighted too many issues in the same post but thought it is related.
Issue 1: Capture app is removing values for captured records if a PR hides certain fields. I think my issue is slightly different than the reported bug (which seems to not display the message for the 2nd PR because the field is hidden) but let me clarify.
When signal is ticked there are a number of fields including those under the “Signal details” section that is shown and captured. (see attachment)
After that the signal may be verified and Event captured. When it is an event certain fields are hidden (and when they are hidden those values captured are blanked out which is a problem for us because we need to calculate indicators for 7-1-7 from the time the signal was detected to response etc. I tried to circumvent the blanking out of values by adding the attributes into a section and hiding the section but again it is not possible to hide a section.
We had similar issues in Tracker Capture before where fields that had values were blanked when a program rule hides a field. In our use case we do not want to blank out these fields.
My question here is whether this is a bug or I should add in a feature request to include a program rule action for hide field (without deleting data) which existed before but was closed.
Issue 2 I have a Program Rule on an event which should update a value for an attribute but it is not updating the attribute - only when you edit and resave the enrollment the attribute gets updated.
Just to tidy up this issue we have found the answers which I will share if it will help others in the future.
For issue 1 where fields are hidden when you select an option that hides fields but you do not want the records deleted, we opted for showing all the fields and only hiding those that you would not mind removing the values for. Also it is not possible to hide a enrollment section at this time only program sections.
For issue 2 @Karoline confirmed that one can set a PR up to update a TEA but the Profile will need to be edited if you need that saved. In our case the PR would not update the TEA because it was a Yes Only field. In this case what we had to do was to set a warning message on the event data element to ask the user to open the profile and then to edit the profile accordingly.
Thank you so much for the clarification and sharing of the solutions to those issues.
If I understood correctly, it’s confirmed that it’s the normal behavior that PRs will remove the values when hiding fields? I think the expectation here is that if the field is to be hidden then it’s not anticipated to have a value (@gregory)?
My other suggestion for the case when a field’s value is removed because it’s hidden by a PR, is to assign it a value (while it’s hidden) using a PR… but maybe this won’t work because I’m not sure if the value is going to be saved for a ‘hidden’ field.
Hiding enrollment sections is not yet supported in program rules. We have a JIRA here: Jira
For hiding fields/sections program rules, there has been some thinking on that here: Jira If we are working on this, we will expand the actions, so there is no need to worry that any of the program rule action behaviors will change @gregory.
So If I understand correctly Karoline’s post, the curent behaviour of blanking value for a field when hiding “Fileds” from PR, but keeping the value, when hiding the section is the expected behaviour and will remain as is?
This means I can be confident that my program will still work in the future, and the “Hide Section Action” will not blank the values.
However, it seems there is a supposed way to hide a field and assign it a value at the same time, but i never managed to make this work.
Shall I use priorities to first hide (by PR action hide field) and then assign the value (By PR Action assign value to DE)?
I already tried a few times to do it but never manager to have it working.
