We have updated our pipelines for Deals and Leads to better fit with our processes. We have created workflows to move the pipeline and stage from one to another when certain conditions are met, but it will only change the stage, not the pipeline. It is greyed out as an option when building the workflow. Is there any reason why pipelines can't be changed through the workflow? Our current work around is to assign a task to someone to do it manually, but that seems like a waste of time when the workflow is already changing the pipeline stage.
I thought I had the same issue but actually observed that setting the "Ticket pipeline and status" property via "Edit record" action in a workflow updates both status and pipeline.
For example, my workflow action says "Set Ticket pipeline and status to New issue (Cake topper tickets)." The bit in parentheses is the pipeline. Any ticket going through the workflow will end up with status "New issue" and pipeline "Cake topper tickets".
On reflection this makes sense because status values (stages) are defined per pipeline, so setting status independent of pipeline value isn't consistent with the data model.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
