Problem/Motivation

Content moderation works for any content entity but the default states are of the opinion that it makes sense for the entities to have draft and published states. Furthermore, it assumes that once an entity has been published, the published revision should be its default revision.

Proposed resolution

Remove the default states.

Comments

c7bamford created an issue. See original summary.

cilefen’s picture

cilefen commented
Title: Remove the default states. » Remove the default states

I am asking seriously: In what use-cases do those assumptions become unsuitable?

cilefen’s picture

cilefen commented

#2844594: Default workflow states and transitions

sam152’s picture

sam152 commented
Status: Active » Closed (works as designed)

These default states are essential when enabling content moderation on bundles that have a lot of existing content. In order to choose a set of appropriate transitions for the user, the content needs to be assigned some starting state. For all existing content, it made sense to allocate these to "draft" and "published" for content that was already "draft" or "published" in the non-moderated sense.

You can actually cut both of these states out of your workflow entirely by setting a new "default state" at the bottom of the workflow form, and then creating transitions to your own states from that point forward. You could also delete any transitions to "published" and "draft", allowing you to essentially never allow the user to return to those two states if they aren't relevant for your workflow.

At this point, without addressing that fundamental use case of assigning existing content to a workflow, these states have to stick around.

Please reopen if you think this needs any further clarification or discussion.