Save As Draft - are we doing it wrong?

[bvlo]

On paper, the Save as Draft feature for catalog items sounds great. In reality, though, it’s causing a lot of frustration among our users. We’ve received numerous incidents related to users’ drafts being lost.

It appears that even the most minor change to an item triggers a version update, which in turn invalidates any existing draft versions. Is there any way to exclude certain fields—such as owner, type, or catalog—from triggering a version update? While I understand that we could implement a process to manage these updates, doing so would create a lot of overhead. At this point, it seems we might be better off simply disabling the feature altogether.

I’m curious how others are handling this issue. Ideally,  we don't want to touch this BR -> Update cat item version 

Thanks in advance

[Sebastian L · Accepted solution]

If you don't want them deleted, you can create and set the property  "glide.sc.delete_draft_item_on_version_change" to "false". It will then not delete it. I am not sure which release of the employee center this got released, but make sure to update the plugin if this does not work. It should have this line in the widget "widget-sc-cat-item-v2"

[bvlo]

Thank you Sebastian !