Forum Discussion
DanielJohnson2
4 years agoQrew Trainee
Hey Mike,
Thanks for the response. I tried your first suggestion, but the problem there is that there are scenarios where the same activity has to be logged twice in a row, and the pipeline wasn't getting triggered when that happened. So, let's say the Contact Status field was already set to Email, and the user sent another email, clicking the button that triggers the webhook wasn't triggering the pipeline. I guess because the field the pipeline was triggering off of wasn't updating? The same thing would happen with your second suggestion because it's possible the user clicks the same button consecutively. Thoughts?
------------------------------
Daniel Johnson
------------------------------
Thanks for the response. I tried your first suggestion, but the problem there is that there are scenarios where the same activity has to be logged twice in a row, and the pipeline wasn't getting triggered when that happened. So, let's say the Contact Status field was already set to Email, and the user sent another email, clicking the button that triggers the webhook wasn't triggering the pipeline. I guess because the field the pipeline was triggering off of wasn't updating? The same thing would happen with your second suggestion because it's possible the user clicks the same button consecutively. Thoughts?
------------------------------
Daniel Johnson
------------------------------
MichaelTamoush
4 years agoQrew Captain
There may be some solutions the way we were heading, but knowing this it seems that the people really need to push the button, so the 'Keep it Simple' approach would be to force them to push the button.
From your original scenario, what if you went a simpler route? What if you put things back the way they were, then set up your form so in edit/add mode you don't even show the contact status field? So it's not even possible for someone to go in edit mode and change the status? If you wanted, in edit mode you could show the button, so they are forced to press the button in any scenario. Or you could display a message in edit mode only 'Please return to the table report to set the status'. You could also make the change status field read only, and in the info bubble write 'Please use the table report to set this field'. Etc...lots of ways to lock people out of setting the status in edit mode.
------------------------------
Mike Tamoush
------------------------------
From your original scenario, what if you went a simpler route? What if you put things back the way they were, then set up your form so in edit/add mode you don't even show the contact status field? So it's not even possible for someone to go in edit mode and change the status? If you wanted, in edit mode you could show the button, so they are forced to press the button in any scenario. Or you could display a message in edit mode only 'Please return to the table report to set the status'. You could also make the change status field read only, and in the info bubble write 'Please use the table report to set this field'. Etc...lots of ways to lock people out of setting the status in edit mode.
------------------------------
Mike Tamoush
------------------------------
- DanielJohnson24 years agoQrew TraineeHey Mike,
Some more info: on the grid edit report where the buttons are there are only three buttons that log are there to making logging specific types of contact easier, Email, VM, LinkedIn. On the form, there are 23 other contact status that are less frequently used, but vital to other form rules and processes. Users still need to be able to edit that field.
------------------------------
Daniel Johnson
------------------------------- MichaelTamoush4 years agoQrew CaptainSo if it is Email, VM, or LinkedIn, a button push is necessary because some APIs run, but in other scenarios they simply need to select a Status?
When they select one of the other status', do the APIs need to run?
Also, if the status field is a multiple choice, can you just make that field logged? Why have a second logged field?
------------------------------
Mike Tamoush
------------------------------- DanielJohnson24 years agoQrew TraineeTo answer you're first two questions, yes, only certain status need to trigger the API. We count Emails, VMs and messages sent on LinkedIn only to be able to assess how many times we've attempted contact because that let's us know whether or not we have a warm or cold lead. So, if a user sends an email then the Contact Status field is set to email. If that email comes back with an automatic reply and the person is on PTO, then the Contact Status field gets manually changed to Out of Office. We don't need to log when changes like that are made, but we do need to make the change so that email stays out of the next round of outreach.
I'm going to try making a checkbox field that gets toggled when the button is click, and have a pipeline fill in the other fields AND switch that checkbox back off. So, the pipeline will fire when that checkbox field changes.
------------------------------
Daniel Johnson
------------------------------