M-Files is a 2025 Gartner Peer Insights Customers' Choice for Document Management
➡️Download the report!

Options
  • Locked Locked
  • Replies 5 replies
  • Subscribers 9 subscribers
  • Views 149 views
  • Users 0 members are here
Related
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
  • 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.
Reply
  • 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.
Children
No Data
M-Files
M-Files Support


© 2025 M-Files, All Rights Reserved.