an end state that you can leave?

[slustbader]

I'd like to create a process that has an end state, but unlike the EndState class, I'd actually like to be able to transition out of the state. As an example, think of a bug report that is closed but can be reopened. The "closed" state is the end state, but it's possible to go back into the middle of the process. More importantly, I need to be able to find this end state without knowing in advance which it is.

What I'm trying to do is end this process as a side effect of another operation. I won't necessarily know what node I'm currently in, and because my process can be edited by the end user, I can't guarantee that the end node will always be named something like "Closed" or "End."

Is there a way to set a flag or some other metadata on a State (or some other type of Node) that I could use for this purpose, or would I have to create my own subclass?

[kukeltje]

there is a very simple solution. Do not re-open the old bug, but open a new one an reference the former. Much simpler than adapting many things in many places.

[kukeltje]

but you can also remove the end date/time on the root token an place it somewhere in a node. I have no example code for this, but if you dig a little into the testcases in the source, you probably find some info