Like plugins, workflows may utilize properties to customize and parameterize its implementation. In the case of workflows, it is up to the workflow developer to define which properties, if any, are needed. A workflow property is useful, for example, when needing to manage the value of a property that is ultimately passed down to an underlying script called by that workflow. Since no plugin understands this type of requirement, it is important for the workflow provider to define the properties it needs.
When a workflow is associated to an instance, FlexDeploy understands that all of its properties must be available for configuration on the environment instance (for environment instance scoped properties) or on all projects (for project scoped properties) which use those instances.