Field conditionals are triggered whenever a user updates a field at the user interface. This ensures that when a user enters a value, Pipefy checks the “field conditionals” to determine whether any actions need to be taken based on the Conditional Rules.
Great.
However, when we update a field via the API, Field Conditionals are not triggered.
This is either a known bug or a product limitation and desperately needs addressing.
Thanks
Update: This issue was fixed yesterday but unfortunately it isn’t working again.
Huh, what a strange bug. Hopefully they fix it consistently for once!
It varies greatly,@mark-theotcentre . There are issues that they fix very fast, e.g. when links in E-Mail templates to attachments were not working, and others like the date picker only working correctly in a few time-zones that are open since more than a year. I guess it is all about setting priorities. This one sounds to me like one that they would fix fast, as it is critical...
Have you sent a report to support@pipefy.com ?
Desperately hoping their team have some kind of eye on these forums ...
Hi guys, hope you are good!
@mark-theotcentre Are you still facing this issue? I’m checking this issue and I will be back to you soon!
The best way to report some issue to our support team is through the chat inside the plataform as is the mainly channel to support our users. The email is not the best way as there is no immediate follow-up and the message could be lost.
Hello, I believe this issue was taken care of by the suggestion given in this other post, right?
For the idea of updating the options of the drop-down dynamically via the API, I'm submitting it to our team, so they can consider on further improvements, thanks@mark-theotcentre !
Hi guys, hope you are good!
@mark-theotcentre Are you still facing this issue? I’m checking this issue and I will be back to you soon!
The best way to report some issue to our support team is through the chat inside the plataform as is the mainly channel to support our users. The email is not the best way as there is no immediate follow-up and the message could be lost.
Hi@mark-theotcentre I found your chat here with us and am sending you the ID of this bug in this chat.
Thanks for the feedback. I will talk to the support team about the need to always provide the BUG ID when it is mentioned.