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]

I can't remember the exact version of the plugin (it just got updated again), but when you update the Employee Center plugin to its latest you should see the code - but I believe it should be after version 38.0.5, maybe 38.0.7! 

[Community Alums]

Hello @Sebastian L 

Thanks for your quick suggestion, as I have checked, we are currently in 38.0.7 too, however the OOB code are not available, I guess raising a case with ServiceNow will be better.

If you have any other suggestion, please do let me know.

Thanks,

Prithwish Sur

[Sebastian L]

Check if you are using a cloned version of it? That would be my best guess since it should be updated through the store and kept out of the box in the "sc-cat-item-v2". 

[Community Alums]

Yes, we are using the cloned version of "sc-cat-item-v3" due to few custom requirement but I have checked both widgets (custom and OOB) however there is no update with the those line of code in both the widgets.

Thanks,

Prithwish Sur