Bugs with new card creation endpoint update


Pipefy has updated its endpoint for card creation, and now we need to provide values for all fields marked as required, even if there is a condition hiding these fields. As a result, we will be forced to allow multiple-choice fields to have options such as "-" and make fields that should be required optional.

I would like to request that Pipefy review this update or allow us to revert to using the old version of the endpoint.

The example below is a attachment field that should be required only in a specific situation, as defined by the conditional.

 

 

This change is presenting high impact! 🤕


NewSubmitted

Very important!