When a card revisits a phase, Pipefy, instead of showing previous phase selections (history) as if they are current selections (most current visit selection), previous selections should be stored in history of the card, which would serve data security concern. Now when we purposefully want a card to revisit a phase several times, we have to clear previous visit selections which defies other benefits. Is this expected behaviour? Just a feedback. Every visit of a phase by a card should start with fresh fields,and any previous visit field selections should be stored in history of the card.
Best answer by belsalemmeView original
@jamestek , that is indeed the expected behavior, the fields belong to each phase and if you move a card back into a phase it’s been before, the information in its fields will be filled with the previous values. If you happen to edit the content of the fields that will be stored in the activity history (lower right corner of the card), like this:
If you need each revisit to start with blank fields you can use a workaround and setup an automation rule to clear them up, it takes a bit of effort though. Let me know if you want to know how to do it, it demands having field conditionals (available in business and enterprise plans) and the use of one automation rule per phase you’d like to clear. Also it’d be great if you could add this to the product feedback section of the community.
I would love to know how to clear all fields in each revisit. Is there a tutorial about this?
I need the same! I tried with automations and was unable. How can I set this up?
EDIT : SOLUTION FOUND
Figured it out! Or at least a way to do it! Here it is: