Thanks for the detail Butch ... sounds like a regression. If it impacts customers, have them file a ticket ... and we'll see if we can get support to get a fix to them. I'll go ahead and start the process on my end to get the wagons circling =)
FYI: Issue: JIVE-70915
Hey Ryan Rutan, do you have a date when this fix will make its way into a release (Cloud or onPrem)?
I banged my head into the same wall last night:
This doesn't only apply to the launcherless app (<action id="com.tembosocial.launcherlessapp" path="jive/apps/launcher?filter=false()"/> ) but to all filters....
To tailor app availability to customer's needs, we set an extProp in Groups, Spaces, Projects - so, this works perfectly on a Jive 184.108.40.206:
action id="com.tembosocial.spaceaction" path="jive/actions/places/space?filter=equals(context.extprops.tembosocialpollsenabled,true)"
while the action always shows on Jive 220.127.116.11, regarless of extProp value.
Trying to figure out why it didn't accept my extProps, I even reverted to
action id="com.tembosocial.spaceaction" path="jive/actions/places/space?filter=false()" - and it was still showing on 18.104.22.168
Summing up, it seems that no Conditional App Action Display filter works due to this bug.... that's a tough bug.
By the way - just tested and it works on Cloud: Jive SBS 2016.2.3.1
This bug is slate for fix in 8.0.4 (to my knowledge), but I do not have the dates at this time. I would recommend that any customers running into this issue request a back port for their environment. We see this in the JC currently as well, so we are hoping we can do the same when the time comes.