Requirement
There are many circumstances where Card Flow through a Pipe needs to be based on Data Condition(s)
Problem
Currently Pipefy Flows are static. Movement of a Card from Phase A to Phase B might be invalid for cards with certain data field values. In these situations, a card user has to push a card from Phase A to Phase B anyway which can be confusing for the user but also represents an unnecessary step and process delay.
Pipefy’s ‘solution’ for this currently is either to create an Automation to move the Card out of the redundant phase. However, the user first has to move the card to the redundant Phase!
The other ‘solution’ for this is to get the user to disable the move button for the redundant phase, but this is clunky.
Solution
Allow Conditions to be created on Flows
Hi,@mark-theotcentre
Does the following automation not help you?
If a field X is updated, based on conditional Y, move to phase Z
If that's what I understood, I think it helps you. I had this problem and I solved it this way. I created logic to display such fields, at the end of completion, to prevent the card from being moved prematurely
Hi@marcosmelo
THanks for this, much appreciated. Unless I’m misunderstanding that implementation, then I agree it works *but* from a card user’s perspective it is confusing.
For example, let’s say a card flow is Phase A → Phase B →Phase C → Phase D most of the time. But when a Card sits in Phase B and has a specific condition (based on Data in Phase A) then when the user submits the Card to Phase C, an Automation will skip Phase C and move it to Phase D.
The problem I have is that in this circumstance, even though the card takes the correct route (skipping Phase C), I don’t want the user to see the “Phase C” button. It’s sometimes confusing when the user clicks the Phase C button only to discover that the card moved to Phase D.
Or am I simply not implementing this in the right way?
Appreciate your help. THanks
Hi,@mark-theotcentre
In this case, you need to create conditions that follow the logic you need.
Take a look at these conditional articles.
What are field conditionals?
Show or hide specific fields in a form according to specific answers so that users can complete requests faster.
https://help.pipefy.com/en/articles/1740887-what-are-field-conditionals
How to create waterfall conditionals
Make forms and phases even more concise and allow multiple items to be added at once.
https://help.pipefy.com/en/articles/6584774-how-to-create-waterfall-conditionals
How to hide fields on forms with conditional rules
Show or hide specific fields in forms when a person selects a particular option.
https://help.pipefy.com/en/articles/1740888-how-to-hide-fields-on-forms-with-conditional-rules
How to set up automation conditions
Define the conditions needed for your automations to run.
https://help.pipefy.com/en/articles/781403-how-to-set-up-automation-conditions
Hi@marcosmelo thanks again, much appreciated. Yes we make comprehensive use of field conditionals and waterfall conditions.
Best regards
Hi,@mark-theotcentre
Great, I hope you can solve these questions with the tips.
Hey, guys! Good discussion about this solution here! Indeed@mark-theotcentre , I believe @marcosmelo 's suggestions will definitely help you here. If you need extra customizations based on your processes' business rules, the different conditionals, field labels, and hiding of card movements possibilities give you many flexible options!
In any case, I'm still submitting this feedback to our team, so that we can analyze it in the future looking for opportunities to simplify the achievement of this scenario. Thanks for sending it!