Enable different validations for “Draft” and “Published” content

I would like to be able to save a draft that is missing some required fields. However, I should not be allowed to publish my draft without being prompted to fill in the missing required fields.

The point is: Not everybody uses Publish the same way. Some users have Review steps and I guess they want to have have everybody filled in until it gets reviewed. So at least we need to make it configurable.

Good point. Maybe we could have a checkbox on the validation page for “Required to save a draft”. This way people adding content on large teams can share the work load without changing validation rules.

Hi @Sebastian
We are struggling on this issue with our Editorial team. They want to disable the required fields when saving drafts (as this is a native requirement for heavy publishing house functionality especially for onboarding more authors and making them create all the articles within the editor itself)

Is there any scripting or rule based workflows which can enable this that would be helpful.

You can make the validation through scripting, something like

if (!ctx.data.myField || !ctx.data.myField.iv) {
   reject('My field is required')