I have 2 pipes: one where I keep all the “open job positions” and the secod where I process the onboard of new employees. Once the open posion is concluded, I create a data base entry through an automation, inserting a new register on my Job Positions database
To start an onboard on my onboard pipe, I need to indicate what job position that new employee will be filling. I use a connection field for that, connecting to the Open Position database. Once the onboard is completed, I update the open postion status on my Open Position DB using an automation, the new status will be “Position Closed”.
When I start the next onboard, that position from the previous employee onboard can not be shown in the list of open positions, because it was already filled and is currently “Closed”.
What is the best trick to solve this?
You already “used” the job position, to start a new one process you need to create another job position, because your process is 1 to 1.
The thing is the used position is still available in the connection field for choosing.
Pipefy should have a filter for the connection field. So I could tell the system to do not show Positions where status is equal to “Closed”.
Great Suggestion
Good idea!
That is an excellent feedback,
I found that each DB register has a status (system default) which can be changed manually only.
If Pipefy add this default field to the list of the automation to update a DB field, it could solve the problem.
I would create an automation like: When a card reach the fase “Closed” > Change a DB field. “Status”.
Join us in the Pipefy Community! 🚀
No account yet? Create an account
Login with your Pipefy credentials
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.