Using task flow not only for dev purposes

Hi,

I fully agree with the replies before. Yes, its primary purpose is to visually explain and split the Fabric items. Also, you may find it convenient to filter the items using the workflow diagram.

What may be counterintuitive is that when you choose the item on the diagram to filter, you may see the items from the different domains, and it may be a bottleneck to use that feature effectively.

So, my advice here is:

1) Formulate what use cases may be interesting for the users on UAT/DEV to use the workflow to understand the engineering part of the solution better? For example, it may be related to the Medallion structure (Bronze, Silver, Gold layers) or different pipeline groups (API, local Data sources, external pipelines).

2) Having in mind the previous thing with domains mixing, I noticed, if the company or the team has a common name convention, it may help to overcome that impediment. Example: adding prefixes to the notebooks/fabric pipelines related to the domain. Like domain1_bronze_dim_loremipsum. Then, when you have that flow, you will be tagging that notebook to the bronze pipeline block, and it will be very easy to use the flow. Because it will be clear what domain it relates to.

That's it from me. Thanks for the good question. If this info helped you out, a thumbs-up 👍 would be awesome! Best of luck, and happy fabric-ing and engineering!