Okay, so here is where the trouble comes in. When I checked on the card that I mentioned in the beginning, it was appearing on the form. But when checking the loggings from the label I created, the values returned should tell us that the card is not supposed to be visible.
Check loggings on the label below
Checking the logging values found on the screenshot above, the values notable for the visibility of the "Action Taken" field are
So if we check back the visibility condition of the "Action Taken" field, it should return "false" since the value of cardWPSignsAdequateFollowupActionRequired.Visible returned on the logging label is false.
Whereas in its visibility condition, it was expecting it as true before it appears.
So clearly, even if it didn't meet the conditions, the card still appeared.
To make the scenario more confusing, let me tell you how I ended up with this.
Before you proceed reading, let me enlighten you that the evidence above clearly shows us that there was something wrong already on the appearance of the card since it wasn't supposed to be visible because the logging said otherwise.
Anyway, this form is handling offline data by saving drafts into a collection.
So first this I did was created a new form, then saved it as draft using Collect functionality.
Then, I edited the draft by editing the same form which is now using the BrowseGallery1.Selected item, which is this exact item I created a while ago.
On this phase, the "Action Taken" field is now showing as expected.
Now, I saved the changes of the draft by using Patch functionality which targets on the same item, BrowseGallery1.Selected.
Then, I tried editing the same item again, then voila, the issue now appeared.
I don't know what happened here, but the point is, the values from the loggings tell us that the visibility of the "Action Taken" field is not supposed to appear, but its behavior showed us otherwise.
I can provide more information about this if ever you reached up to this point.