Skip to main content
Solved

Move Card to New Phase - mandated fields


mark-theotcentre
Forum|alt.badge.img

We’re using the Pipefy API to move a card to a “Cancelled” Phase when an external event occurs.

The issue we face is that the API bombs out with a runtime error when there are incomplete mandatory fields on the cards current phase. 

I’m trying to come up with a way to manage this particular situation.

One solution, in theory, could be for the API to set the value of a particular field on the Start Form to signal field conditionals (on all phases) to hide all fields. That would work, except there’s an established bug in Pipefy which means that field conditionals are not triggered when a field is updated via the API. They only trigger when a field is updated via the user interface. (A bug I reported more than 12 months ago!).

Any suggestions very much appreciated

Thanks

Best answer by Leonardo Lucena

Hello, Mark! I hope you're doing well. I understand how frustrating this situation can be and I wish I could offer an alternative solution, but unfortunately there's no way around this problem. As for prioritizing the bug, it actually follows the process I mentioned earlier in the support chat. I'm happy to help with any other questions or needs you may have.

View original
Did this topic help you find an answer to your question?

3 replies

Leonardo Lucena
Pipefy Staff
Forum|alt.badge.img+1

Hello, Mark! I hope you're doing well. I understand how frustrating this situation can be and I wish I could offer an alternative solution, but unfortunately there's no way around this problem. As for prioritizing the bug, it actually follows the process I mentioned earlier in the support chat. I'm happy to help with any other questions or needs you may have.


mark-theotcentre
Forum|alt.badge.img

Hi Leonardo, thanks for the reply. This is a different bug to the discussion we had recently. There are two significant bugs concerning field conditionals which I reported over 12 months ago.


  • New Member
  • 4 replies
  • January 29, 2025
mark-theotcentre wrote:

We’re using the Pipefy API to move a card to a “Cancelled” Phase when an external event occurs.

The issue we face is that the API bombs out with a runtime error when there are incomplete mandatory fields on the cards current phase. 

I’m trying to come up with a way to manage this particular situation.

One solution, in theory, could be for the API to set the value of a particular field on the Start Form to signal field conditionals (on all phases) to hide all fields. That would work free live cam to cam chat, except there’s an established bug in Pipefy which means that field conditionals are not triggered when a field is updated via the API. They only trigger when a field is updated via the user interface. (A bug I reported more than 12 months ago!).

Any suggestions very much appreciated

Thanks

You could pre-fill the mandatory fields with default values via the API before moving the card to the "Cancelled" phase to prevent the runtime error. Alternatively, add conditional logic in the API call to check for incomplete fields and handle them before transitioning to the next phase. Keep following up with Pipefy support regarding the bug with field conditionals not triggering via the API.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings