Explicit state of workflow feels superflous #4528
matthias-ronge
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
All our projects and process templates behave in the same way: When they are used for the first time, they cannot be edited any more, in place of the edit button, the view button (eye) is shown. Workflow is different, as you have to set its state to „active“ manually and save it. I don’t see a necessity or benefit thereof. I believe that the „draft state“ is more something conceptual, a workflow is a draft as long as it isn’t used.
I think that the „state“ drop-down of the workflow could be eliminated, and the workflow state is determined as the state projects, process templates.
Beta Was this translation helpful? Give feedback.
All reactions