Details
-
Sub-task
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
Description
Flow names are not sufficient to identify a flow. I noticed we used both "flowName" and "flowId" to point to the same thing. We need to unify them to flowName. Otherwise, front end users may think flow id is a top level concept and try to directly locate a flow by its flow id.