Forum Discussion
DanielJohnson2
4 years agoQrew Trainee
Hey Jim,
I don't think I can remove one route because the button route allows user to log consecutive contact attempts. There's now way with a multi-choice field to change from Email to Email, for example. With the button, the user can click email, let a few days go by, and click email again, thus logging both activities. And I can't get rid of the multi-choice field because there are only 3-4 contact attempts we want to log activity for, but 21 other choices like Out of Office, Declined, In Dialogue, the list goes on.
------------------------------
Daniel Johnson
------------------------------
I don't think I can remove one route because the button route allows user to log consecutive contact attempts. There's now way with a multi-choice field to change from Email to Email, for example. With the button, the user can click email, let a few days go by, and click email again, thus logging both activities. And I can't get rid of the multi-choice field because there are only 3-4 contact attempts we want to log activity for, but 21 other choices like Out of Office, Declined, In Dialogue, the list goes on.
------------------------------
Daniel Johnson
------------------------------
JeremyAnson
4 years agoQrew Cadet
Just came across this post and I think it highlights a challenge with pipelines. As designers/developers we would like to have tools that work in the 'back end' of applications, responding to user actions, updating data and showing the results back to the user (well, I would). Automations worked quickly enough for this to be possible most of the time, but pipelines don't and we either have to implement workarounds or convince users that their actions are being reflected in the data, despite what they see on the screen.
------------------------------
Jeremy Anson
------------------------------
------------------------------
Jeremy Anson
------------------------------