Ok, as we all know, the SetProcess action in workflows no longer works for changing BPFs. So I'm here to ask if anyone has resolved this issue.
Short story on my side, client has a number of processes for Case resolution, all unique to the Subject type. There is no commonality to them, other than the Subject being required. I've looked into merging them into one giant branching Business Process, but that looks unmaintainable after trying to map it out.
What I have done so far:
1. Set up a workflow that Creates the appropriate BPF record based on Subject. This works great, in the sense that the BPF gets created. However, the default BPF is still on, and is the one that's showing. (tried this both real-time and async)
2. Set up a dummy Default BPF that just asks for the Customer and the Subject in one lovely stage.
3. Autocomplete/disable dummy BPF the moment the Subject is selected.
Even with all of this, the one-step dummy BPF is the one that is selected (and shows as finished), not the real Case BPF they need to do their work. How do we set this so the only BPF that is running/showing is the only one valid for the subject? I want to avoid code if at all possible, as my client needs to maintain it afterward.
This seems like such a huge functionality step backwards, to me. All these enhancements to support multiple BPFs, and no easy way to set the active BPF.