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