Always Hide Fields
Completed
I use fields to drive and control triggers. It would be nice to allow setting in fields to always hide in the UI. I know there is a Hidden when empty option, but would be nice to be able to hide always no matter what.
-
Official comment
Hey everyone! We've just released the option to always hide fields. Read about it here:
http://blog.podio.com/2017/02/23/the-power-of-apps/
Hopefully this will help keep your apps more clean and efficient :)
/Jacquelyn - Podio
Comment actions -
+1 for this idea!
As an admin, i have a ton of fields that I use for sensitive calculations or other things that the 'regular' members on my team don't need or want to see. This can mean my apps get cluttered up and less user friendly for regular users. Ultimately, it makes my colleagues not want to use podio at all, and I think about ways of getting users OUT of podio (in terms of our day to day company workflows).
Since Podio makes money on per-user subscriptions, this strikes me as a very important matter, and something worth elevating on your product roadmap. -
I'd like to second this request.
The system I am building also uses calculation fields as methods of incorporating extra functionality and references often using javascript. It would really help to be able to hide the fields from the app UI.
What would be really useful would be the options for each field
- hide if empty (already exists)
- hide from print
- hide from app -
Any update on this. I really need to hide away fields that contain data. For example, I use a workflow to pull in the google address information (JSON) from a location field, and then calculate the other address field so that I can separate these into specific fields (Street Number, Street etc). The issue is that the Json field is multiline and is long. This means that the app is a mess unless I can hide the JSON multi-line text field.
-
I have to create a please ignore section in so many apps because this doesn't exist.
-
We can definitely use a Podio enhancement that enables a field to be hidden from the normal app view. That being said, I've found a number of cases where I'd want a hidden field that is still accessible/viewable in the following places:
- Globiflow. For calculations and other data manipulations.
- Webforms. Example here is a data capture form, where the data is captured into a field that won't be visible later because it is transformed/manipulated (either by Calculations or Globiflow) before it is shown in the normal app view.
- Reference Badges. Sometimes 5 fields is not enough and you concatenate multiple fields together so they are viewable in a Reference Badge. Or you create a "Quick Reference" field in the app that you only want to show in the reference badge but not in the normal app view.
- Tiles. For dashboards and reporting (and similar to reference badges) you may want a "Quick Reference" visible in a Tile but not the normal app view.
-
I don't personally see a need to show hidden fields in badge or table layout.
One other comment: it would be useful to look at the need for read-only fields (writeable only by calculations, Globiflow, or a workspace admin) at the same time as hidden fields. That way the need for "Quick Reference" fields (computed from other user-entered data) is addressed in a comprehensive way.
Please sign in to leave a comment.
Comments
53 comments