Ask the Community
Connect with other Pipefy users and community experts to get help building great workflows and processes.
- 364 Topics
- 1,053 Replies
Hi team, we are working with a project which the cards will be created by email, we were planning to redirect all emails from the generic mailbox to pipefy email address, but now they are saying that the forwarding rules are not allowed as per their global security policies. Do you know of a different process on how to create cards from Generic mailboxes?
We have a need in a field to capture both a “category” or “classification” and the description in one field. In this example, a user would enter the request the classify it as required, desired or optional. I have seen this done with jotform and other form builders. How can I accomplish this with Pipefy?
Is there any way we can filter cards on connection fields? We’re in a design process where we have multiple jobs to fill, and where candidates will go through selection pipes. However, we need one of the following options: One pipe per job to fill The possibility to filter candidates (cards) on the job they are evaluated for (connection field) Is filtering on connection fields (2) at all possible? If not, I’m thinking of using the clone pipe api call to programmatically create a candidate selection pipe for each new job to fill. Or maybe there would be a better way of approaching this? Edit: found this discussion where it was stated 2 years ago that filtering on field values was on the road map is it still? Edit2: also found this roadmap item where group of filters is in progress for reports, but this seams mostly unrelated to filtering cards on field values. No other item on filtering cards unfortunately.
Hi friends, 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.
My name is Michael Gruber and I work for UNICEF Canada. I’m here because we have a legacy home brew workflow for requesting translation of documents and content. This runs on MOSS 3.0 / Sharepoint 2007 and the servers are quite old and need to be upgraded. The only problem is that the latest operating systems don’t support the old versions of Sharepoint so I’m faced with either upgrading sharepoint or switching. I found Pipefy through an online search and it looks promising. I’m not a programmer, but I do understand the logic in the workflow. If anyone has seen anything similar to what I’m trying to accomplish, I’d really like to hear about it. Thanks!
Community Experts Leaderboard
Join us in the Pipefy Community! 🚀
No account yet? Create an account
Login with your Pipefy credentials
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.