Workflow: add to "No State"

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?

I often use forced workflow on a document class without any trouble - they always pass on to the first state automatically. If you change a document's class to "foobar" it should also work automatically. If you had documents in the "foobar" class before you added the workflow and set it as "forced" then you may have to go back to those documents and add the workflow manually. I haven't seen problems in that situation either.
Automatic transition is not necessary from No State to the first possible state, it will happen by default
Karl.

Strange, since this occurs to new documents. Might be worth a supportcall. Cheers

Something I might have overlooked.
When using the Graphical designer, you don't pay to much attention to the old-fashion gui.
In the old gui, you can order states up and down.
When I sort my first state to be on top of the list, transition goes without issue.

If that is true, it would be swell to have some indicators on the visual states to see the logical order. Like a TabIndex on a form.

Just had a customer call on a case like this. Internal users had no trouble adding objects to a class with a forced workflow, but external users got an error saying that the Workflow state could not be empty - they had to select the state manually. I had given external users permissions to create objects in this class and to see the workflow, but I had forgotten to give them permission to see the Transition between "No state" and the first state of the workflow. After adding permission it works just fine.
The workflow itself is a simple one that allows users to create an entry and edit it the same day and then changes permissions to read only to prevent anyone from changing the entry later on.