Mandatory fields

Produto_529
Produto_529 Posts: 12

Hello guys, we really need mandatory fields. The current option with important fields istn´t enough

0
0 votes

· Last Updated -

Comments

  • Paulo_82
    Paulo_82 Ex-Pipedrivers Posts: 8
    Pipedrive Employee
    edited February 24 #2

    Hey there, that's a great feedback, I do know a workaround to have some mandatory fields using workflow automations that you can use while Pipedrive do not have native mandatory fields. 

    For example, if you want to create an automation that will stop a deal from progressing to a stage unless a deal value has been added, this is possible using our automations. In this case, you would need to choose “Deal Updated” as your trigger and define what the conditions you want are (in this case if “Deal stage has changed”, “Deal stage is Proposal Made”, and “Deal Value is 0”).

    You can take a look at an example of the trigger below.

    image

    Then, we have the action to update the deal’s pipeline stage to the stage it was in before the update. This will act as “reverting” the deal back to its previous stage if trigger conditions are met.

    image
  • Produto_529
    Produto_529 Posts: 12
    edited March 2020 #3
    Paulo said:

    Hey there, that's a great feedback, I do know a workaround to have some mandatory fields using workflow automations that you can use while Pipedrive do not have native mandatory fields. 

    For example, if you want to create an automation that will stop a deal from progressing to a stage unless a deal value has been added, this is possible using our automations. In this case, you would need to choose “Deal Updated” as your trigger and define what the conditions you want are (in this case if “Deal stage has changed”, “Deal stage is Proposal Made”, and “Deal Value is 0”).

    You can take a look at an example of the trigger below.

    image

    Then, we have the action to update the deal’s pipeline stage to the stage it was in before the update. This will act as “reverting” the deal back to its previous stage if trigger conditions are met.

    image

    Thank you, Paulo, but isn´t a option for us, because automation isn´t available in my plan. Anyhow, I believe that mandatory field is a option that should be available for everybody, no matter the plan

  • Paulo_82
    Paulo_82 Ex-Pipedrivers Posts: 8
    Pipedrive Employee
    edited March 2020 #4
    Paulo said:

    Hey there, that's a great feedback, I do know a workaround to have some mandatory fields using workflow automations that you can use while Pipedrive do not have native mandatory fields. 

    For example, if you want to create an automation that will stop a deal from progressing to a stage unless a deal value has been added, this is possible using our automations. In this case, you would need to choose “Deal Updated” as your trigger and define what the conditions you want are (in this case if “Deal stage has changed”, “Deal stage is Proposal Made”, and “Deal Value is 0”).

    You can take a look at an example of the trigger below.

    image

    Then, we have the action to update the deal’s pipeline stage to the stage it was in before the update. This will act as “reverting” the deal back to its previous stage if trigger conditions are met.

    image

    You are welcome. And I do understand it, indeed the workflow automation is a feature available only in advanced and professional plan but either way the feedback has been passed to our product team.  

  • Boris Tsibelman
    Boris Tsibelman Community Driver Posts: 1,037
    1000 Comments Second Anniversary Combo Breaker Photogenic
    edited March 2020 #5
    Paulo said:

    Hey there, that's a great feedback, I do know a workaround to have some mandatory fields using workflow automations that you can use while Pipedrive do not have native mandatory fields. 

    For example, if you want to create an automation that will stop a deal from progressing to a stage unless a deal value has been added, this is possible using our automations. In this case, you would need to choose “Deal Updated” as your trigger and define what the conditions you want are (in this case if “Deal stage has changed”, “Deal stage is Proposal Made”, and “Deal Value is 0”).

    You can take a look at an example of the trigger below.

    image

    Then, we have the action to update the deal’s pipeline stage to the stage it was in before the update. This will act as “reverting” the deal back to its previous stage if trigger conditions are met.

    image

    This is a great work around idea! 

  • Jan Visser_342
    Jan Visser_342 Posts: 108
    edited April 29 #6

    While this technically works - I am not sure you guys have the right idea of what the average (and certainly my) CRM user looks like ;)

    If I create this automation where the stage is reverted without an error message, users will likely not even notice. They will think it's done - and we end up with a lot of projects in the wrong stage that need either discussion or administrative cleanup. 

    This CRM stuff is supposed to make things easier, remember ;)

     

  • Marcelo Silva_43
    Marcelo Silva_43 Community Driver Posts: 291
    100 Comments Second Anniversary Photogenic Community Driver
    edited April 29 #7

    Entendo, realmente seria muito interessante.

    Mas é uma questão de cultura as vezes, se seu vendedor não se preocupa em preencher os campos importantes é por que ele não vê valor nisso, e a tendencia de você obrigar ele a preencher, não gerara valor nem para ele nem para o processo.

    Eu tentaria entender, pergunta para eles, por que não preenchem os campos?

    Uma alternativa seria uma auditoria em determinada etapa, e você poderia bonificar quem esteja preenchendo adequadamente.

     

    Eu acredito que Obrigar um vendedor a fazer algo, é tirar o empoderamento dele de de fato assumir a responsabilidade sobre o processo e consequentemente a venda.

  • Produto_529
    Produto_529 Posts: 12
    edited April 29 #8

    Oi Marcelo,

    Obrigada pela colaboração e é importante seu ponto de vista, porém por ser um processo manual, é vital mitigar erros (falta de preenchimento) não intencionais, sem onerar em um processo adicional de auditoria ou menos ainda bonificação. 

    Acredito que um vendedor pode se sentir empoderado e ter responsabilidade, mesmo tendo campos obrigatórios. Do meu ponto de vista isso não é excludente. Aqui na Concil em específico, isso seria muito útil pra gente porque temos integração com outros sistemas que usam esses campos obrigatórios e quando eles não estão preenchidos, gero erro e retrabalho pro vendedor.

    Então em resumo a ideia é mitigar erros não intencionais e evitar retrabalho ;)

  • Mike van der Valk
    Mike van der Valk Posts: 4,386 PIPEDRIVE PRODUCT MANAGER
    2500 Comments Third Anniversary 25 Likes First Answer
    edited February 24 #9
  • Marcelo Silva_43
    Marcelo Silva_43 Community Driver Posts: 291
    100 Comments Second Anniversary Photogenic Community Driver
    edited May 2021 #10