Skip to main content
New

Filter Database entries through a connection

  • September 4, 2024
  • 7 replies
  • 119 views
  • Lucas Democh
    Lucas Democh
  • Ezequiel Souza
    Ezequiel Souza
  • rafael.jefte
    rafael.jefte
  • vicente-lemes
  • Cece
    Cece

ERICK FABIANO REZENDE DA SILVA

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?

7 replies

Ezequiel Souza
Forum|alt.badge.img+14

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.


ERICK FABIANO REZENDE DA SILVA

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”.


marcosmelo
Forum|alt.badge.img+18
  • Legend
  • 1466 replies
  • September 5, 2024

Great Suggestion 


Ezequiel Souza
Forum|alt.badge.img+14

Good idea!


fernanda.cunha
Community Manager
  • Education Team
  • 53 replies
  • September 5, 2024

That is an excellent feedback, @ERICK FABIANO REZENDE DA SILVA! You can leave certain instructions for the person operating the process not to choose that position, such as the description or the filed or even the name of that position by adding a "[closed]" before the job title, but we appreciate your thorough explanation and I'll definitely pass that suggestion on to our Product team.


ERICK FABIANO REZENDE DA SILVA

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”.
 

 


ERICK FABIANO REZENDE DA SILVA

I think this suggestion has not been considered yet.
Any update?

 

Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings