How to persist "Save for Later" draft data after updating Catalog Item definitions?

[晃秀黒]

Hi everyone,

I am currently facing a challenge regarding the "Save for Later" functionality in the Service Catalog.

The Issue:
Whenever we update and publish a new version of a Catalog Item (e.g., adding or modifying variables), any existing draft data saved by users is either cleared or fails to load correctly.

While I understand this is likely due to data integrity checks triggered by version mismatches or configuration changes, it poses a significant UX issue. Many of our catalogs contain a large number of input fields, and users are understandably frustrated when they lose their progress due to minor administrative updates.

Goal:
Even when a Catalog Item definition is updated, I want to allow users to load their saved drafts for any variables that remain unchanged. (It is acceptable if modified or deleted variables do not populate.)

Questions:

Is there a way—via system properties or OOTB configurations—to persist and load existing drafts (from sc_cart_item, etc.) after the item definition has been updated?

Is it possible to bypass or relax the standard logic that invalidates drafts when a version mismatch is detected?

If this is not feasible within OOTB functionality, what are the recommended best practices or workarounds to prevent data loss for users during catalog maintenance?

I would appreciate any insights or advice from the community. Thank you in advance!