I am just starting with Podio and Podio API, but there is a thing I already stumbled upon several times.
We have fields in our apps we do not want our users to fill out but instead they are filled via API hooks (e.g. user enters a customer address and in the background our geocoder stores coordinates and a link to a dynamic map). For now they are normal text/number/link fields and when creating an item they are shown to the users and they have to know, that they should ignore it. Of course they will remember this after some time, but it also adds unnecessary clutter to the edit forms.
Another case are calculated fields with dates that we want to update daily. In this thread (https://help.podio.com/hc/communities/public/questions/201885938-How-to-update-date-calculations) it is recommended to not even use a calculated field for this but instead directly fill in a normal field via API. But again, we do not want the user to edit - we just want to show the result of a calculation. So having a possibilty for a readonly field would also work here I think.
We can already easily mark a field "mandatory" or "hidden if empty" - adding an "readonly" option and later treat it like a calculation field in the edit forms should be rather simple to implement in my understanding.
What are your thoughts about this? Could others also use this feature?
Please sign in to leave a comment.