Looking for a way to organize my flows into different folders. i make flows for different departments in our company and it would make it much easier to work with folders of flows rather than one long list
Our recommendation is to use Solutions to organize your flows. We are also looking at if there are additional organizational capabilities that we can add to help you organize your flows.
Agree, the Solution method is not enought for all scenarios. We do not use Common Data Service as Data Source and the Solution method requires to have it enabled. A basic solution to create Folder to manage flows or group them based on an created Application will be useful.
This is a must have so that we don't have scroll through them. Please help asap, and please don't mention the "Solution" option for CDS, we're not using that.
At a bare minimum, let the flow list be sortable, filterable and searchable, this way, we can have a cheap "naming" convention until we get manageable "tags" and be able to group by those tags. With tagas, a workflow should be able to able to be visible in multiple logical groups.
I have hundreds of workflows that I created and I'm now making mistakes due to the fact that I can't logically group them together around a logical departmental process.
maybe adding a tag, so we can tag a flow, or shared flow, in a way that is meaningful for us to group?
Hi @maahimscommune, an user reopen this ideia here: Provide a real method of organizing Flows
can you help voting?
I have a bunch of different flows that I have for multiple different clients. I need to be able to group my flows by client. Folders would help so much with this!
Currently there is no way to organize your Flows and this isnt a problem if you only have a few but once you start getting a few pages worth its hard find what you're looking for quickly.
In addition to adding additional relevant columns in the Flow list views, I'd like to see filtering and sorting on all the columns.
I comment this on the previous thread too.
Features like sort or filter wouldn't be something that they would be able to build easily due to the paging nature of the API. This is an honest, external feedback from understanding the APIs - it won't be something they can tackle when ranked against other big road map items, e.g. move personal Flows into Solutions is what I'd consider a big strategic feature.
In the meantime, I build https://flowstudio.app to provide some immediate relief for Flow makers dealing with a lot of existing personal (or team) Flows. Flow Studio takes the path of reading everything up front, then sorts a grid for us. Flow Studio is used by 1300 users.I have kept sort, filter and #hashtag grouping as free features that requires no subscription because of these thread.
Flow Studio's subscription tier is advanced tools for monitoring, run-as admin and Flow migration.jliu
Not everyone has CDS or a Plan license, so are we only completing requests for the premium users now?!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.