I make a tutorial. I wrote requirements as a numbered list. For each step, I will create a step or condition. I can set a title for each state to describe step number. I cannot set a title for a condition. There should be an optional auto numbering for states and conditions. When I insert a step I can get ordered titles again. I guess it is not suitable for graphs that have braches. You assume that this number describes the depth of the element. My scenario has 30 steps and it is better to maintain it step numbers and the requirement list. Auto numbering should be set graph level and it should and number as a prefix to the title of the state.
I honestly do not understood what you mean here, or what you refer to. I am really sorry :/
What do you mean “auto numbering for states and conditions”?
“You assume that this number describes the depth of the element”…What “number”?
I attached what I mean. For sequential actions, you can call it order number. I have 40 steps in an FSM. I set name for actions. I can add prefix “1-” “2-” manually. when I insert a state before 4th state I have to rename all followings state names.
I see what you mean, but I do not really understand what you are suggesting 🙂
Are you suggesting an option to auto prefix the state names by some ID, and if so what that ID would be, or from where that ID would result out from?
ID will be the depth level of the node from the start state. what I suggest is not meaningful for complex graphs. it is useful for sequential actions. you can assume there is a tutorial. the tutorial has 30 steps(states) and each state connects with a condition that requires a human input. ID will be a sequence number and will be added as a prefix. You can also assume that those IDs are item number in the requirements document. this is a nice to have feature. Don’t accept it as a mandatory feature.