Forum Discussion
Using task flow not only for dev purposes
Hi all, thanks for your replies.
I consider the task flow an high-level visual feature more important to provide a graphic and immediate representation of the data flow to build, combining data objects (e.g. lakehouse, warehouse, database, semantic model) and data operations (e.g. pipeline, dataflow, notebook) pictured in processing phases and data architecture, so to present/tell the entire data path, from the sources to the consumption point, to the end-users, also project managers and CIOs/CDOs.
A such graphic representation can be captured and put into a functional requirements document to describe better the data flow for the project approval: a such document is read from business users.
I think this feature has more potential value than it might seem: it is limiting to use it only for development purposes.
The task flow allows a good navigation between the implemented items, often put in folders.
I think that this feature could be further improved, in terms of graphics and navigation.
Thanks for your attention.
Hi pmscorca,
Thank you for sharing your thoughts. Your use case for Task Flow as a high-level architecture and communication tool is clear and makes sense. According to the current documentation, Task Flow is designed as a visual, non-operational feature, and your feedback highlights potential areas for future improvement. Since this would be a product enhancement, the best next step is to submit your suggestion directly to the Fabric product team.
You can do this in the Fabric portal by navigating to Help → Feedback → Submit an idea.
Thank you.