Help...how to manage catalog request drafts vs. item updates?

[Kristin J]

Hello! We recently implemented the "save as draft" functionality along with a couple catalogue items that are designed to be iterative (information is gathered and input over a period of time before the full form is submitted).

We are coming up against the situation where there are saved drafts for an Item that requires an update.  If we do nothing, these drafts are deleted when the system detects the update to the Item, and then when the user returns to their draft, they can only start over.

Is anyone out there proactively checking for existing drafts before an update, or better yet, has a way to re-map fields and rebuild a draft somehow? Deleting drafts is not acceptable for us as there is a lot of detail being submitted in these forms, and I'm concerned that we have released an unsustainable service.

Thank you for any help you can offer!
Kristin

@JayGervais  

[Sebastian L]

I tested it in our instance and found that if you e.g. delete a variable that was there before, then it simply ignores that and fills in the ones that are still present. So, so far so good! 

Please let me know if you find something that is not working as intended! For now we have just set the property and our users are happy! 🙂 

[Kristin J]

Yay Zurich! I really appreciate your pointing this out and the follow-up. I will let you know what happens with us. 🙂