Lock states logic

[philipfrench]

Has anyone worked out the exact logic of Lock States?

I had this question from a student on a course.

If I go this route, when I arrive Trainer Signature, it is locked, because I have gone through the Lock State.

However, when I go back to the initial state, it is editable, which is what I want.

My conclusion is that this is the rule:

If you arrive at a state that you have already visited BEFORE you met the lock state, then it is Editable.

Any state you visited for the first time AFTER you met the lock state, then it is locked.

However, if I have written this correctly, then (below) when I arrive at B for the first time, it is Editable (yes).

When I arrive at B for the second time, I have met the lock state, but because have gone to B before, it is still Editable (yes) [like the initial state in the first example].

However, now when I move to F, I have not visited this state before, and I have passed the lock state to get here.

So I expect this to be like “Trainer Signature”, and be locked. But it is Editable.

This means that my summary of the rules above is not correct.

Has anyone figured out, and can clearly describe the logic used to determine if a state is locked?

(BTW I did not design the original workflow)

[ashleyohooper]

Hey Phil,

Long Time...I just seen your post and what I would weigh in my thought on how it worked...

From what I can see and I just tested this logic, please image below...when I transitioned from A to C the record became locked and then any transitions from then onwards were locked, it didn't matter if I had entered them previously before, however if at any point I interacted with Workflow State "A" again the record would unlock and any future transitions would be remained unlock until reaching the locked state again.

However from what I can see what ever the original state was which locked the record in the first placed for example "A" is now the only state in which can unlock it.