"The field State transition must not be empty" Error in Object Creation with a Forced Workflow

Overview

When there is an M-Files workflow that is set to be forced for new objects in the class properties (pic. 1.) and there is an automatic state transition configured from the initial "(no state)" to the first "real" workflow state that is triggered with a certain object criteria (pic. 2.) and user instead manually creates the objects, user can get a "The field "State transition" must not be empty" error (pic. 3.) and object creation cannot proceed. 

This can be caused by a property that is not available/visible when creating the object manually but is filled in with some other automation that triggers the initial workflow state transition. As an example, objects that are imported from external database, come from external data source or there is some other M-Files connector that creates new objects and also automatically adds the properties that are used in the automatic state transfer trigger condition but are missing in manual creation of that object class.

Pic. 1

Pic. 2

Pic. 3

<MetadataEditor>, -, The field "State transition" must not be empty. (0x800403EA)
ScriptErrorHelper.cpp, 96, The field "State transition" must not be empty. (0x800403EA)
MDispatchExImpl.h, 688, The field "State transition" must not be empty. (0x800403EA)
MDispatchExImpl.h, 850, The field "State transition" must not be empty. (0x800403EA)
MetadataCardAction.cpp, 386, The field "State transition" must not be empty. (0x800403EA)
MetadataCardAction.cpp, 570, The field "State transition" must not be empty. (0x800403EA)
MetadataEditor.cpp, 2959, The field "State transition" must not be empty. (0x800403EA)
MetadataModel.cpp, 4235, The field "State transition" must not be empty. (0x800403EA)
MetadataModel.cpp, 4412, The field "State transition" must not be empty. (0x800403EA)
MetadataControl.cpp, 2743, The field "State transition" must not be empty. (0x800403EA)
MetadataControl.cpp, 2890, The field "State transition" must not be empty. (0x800403EA)
(M-Files <Version> <Timestamp>)

Solution

Possible solutions:

1. Add the property to be visible to the user in metadata card when creating objects. Property can be visible by default in the class properties, or it can be configured to be show by a rule in metadata card configuration in vault Configurations. Note: not all properties can be configured to be seen on metadata card.
2. If there is a triggering property that cannot be added to the metadata card, add an additional workflow transition from "(no state)" to the first "real" workflow state without any transition trigger:

3. Create a separate copy of the WF for manual creation of the object and remove the triggering criteria