Friday Fun: EXISTS statement for user preferences, and New Home stats
Additional note for 2024: please note that the post below was applicable for a beta version of Home which did not include the option to opt your entire instance into Home. At the time, admins were concerned over the usage and control of the beta Home product, so I developed the filter below as a way to help these discussions or to help alleviate the concerns. Since this post, Workfront has provided the option to opt in your entire instance, and over time, will probably change more. I'm leaving the post below because it still is a really good teaching tool for exists statements and user preferences -- but it should not be considered as a reliable way to indicate who is or isn't Home.
Based on a prior post here:
I took things to their logical conclusion, which was to use an EXISTS statement to discern who had particular preferences toggled.
For example, with all the discussion of the New Home interface, and who is using it, a sample piece of text mode for a USER report is:
EXISTS:a:$$OBJCODE=USERPF EXISTS:a:name=home-workspaces-opt-in EXISTS:a:userID=FIELD:ID EXISTS:a:value=true
(you could use "value=false" for those who opted back out, or "value_Mod=notnull" if you want both)
This means, you can easily see who is currently using New Home, who didn't want to continue to use it -- and everyone else who doesn't have a value, ignored the blue bar.
Thanks as always to @doug_den_hoed__atappstore who started me on my journey with his response here:
--------------------------------
If you liked my post, please like my ideas at
--------------------------------
