This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Workflow: add to "No State"

Former Member
Former Member
Hi.

I have a nifty workflow, working great.

The only thing that I don't see is why I can't add a document (lets say "class foobar")  to a Workflow without manually entering the first state name.

There is only one possible state after the 'No State', namely: 'New document'. From that state, some triggers will advance de document through workflow states and that is working fine.

I tried several configurations for state transitions, but keep getting the message 'The field ?State transition? must not be empty' when a document is added (while keeping state empty).

How can one add a document to a forced workflow, without entering the first state?

I'm proberly missing something obvious, hopefully someone can shine a light here.
Parents
  • Former Member
    Former Member
    I think I gave the answer myself.

    When I deselect the "force workflow" checkbox, it all works as intended, including automatic transition to the first workflow step.

    Selecting a forced workflow is not the same as forcing to select a state?

    Is this a glitch, or is this design?

Reply
  • Former Member
    Former Member
    I think I gave the answer myself.

    When I deselect the "force workflow" checkbox, it all works as intended, including automatic transition to the first workflow step.

    Selecting a forced workflow is not the same as forcing to select a state?

    Is this a glitch, or is this design?

Children
No Data