12
Hello,

I know you all are trying to push Flows, but it is currently *not* a viable alternative to Workflow. It is more powerful and able to do most of the same things as Worfklow, sure. But it is also much more complex, it's not necessarily clear how to replicate functions previously handled by custom workflow plugins in Flows, and there is no way to convert Workflows to Flows easily rapidly.

For all these reasons, for the love of God, would you please resurface the background processes nav item in the UCI? I'm tired of having to navigate to the classic interface (made harder by the fact appending ?forceclassic=1 to the URL works less and less as you force UCI) or open an Advanced Find just to figure out if a Workflow executed correctly.

Don't get me wrong: I think the UCI is an improvement, I think Flows is very powerful and has tons of potential. However, until there is a quick way to convert Workflows to Flows, the fact that D365 in UCI is hiding background processes is extremely irritating.

Thank you,
Sam
STATUS DETAILS
Needs Votes

Comments

S

I also agree with this - now that we are getting closer to the UCI transition deadline, the fact that it is so difficult to find a record's related background processes is quite an issue.

Category: Unified Experience: Search, navigation and performance

S

On top of that, it is annoying to get these banners suggesting that there is now a "better way", only to be recycled right back where you started because there was actually, not a better way.

Category: Unified Experience: Search, navigation and performance