We would like task flows to be included in source control, and included as a publishable item, so we can view our task flow across development/test/production, and propose changes to the task flow documentation and tagging via branching.
3 Comments
- Status added:Needs Votes
- This would be benificial for us as well. Now, it is just a representation of the artifacts in a workspace, in stead of a workflow representation the current state of your environment. So when you publish a new artifact to the next stage, you will have to manually update the corresponding task flow. i.e. the task flow is not aware anything has changed. Furthermore, I want to use a custom task flow and import it from my GIT repo. So that when I setup a new workspace, I can just sync the basic custom task flow from GIT, without having to manually click every part together.
- This would be very helpful, and adding the Task and Tags values to the items' ".platform" json file could be used to support this as well as provide a way to get the task and tag assignments without the missing public API (a public API for these would be nice too though 🙂 )
