Help...how to handle request drafts vs. Catalog 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.

Has anyone built something or otherwise manages checking for existing drafts before an update or rebuilding 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

(cross-posted in ITSM) 

@JayGervais  

[Dr Atul G- LNG]

Hi @Kristin J This appears to be expected behavior. When an item is updated while in the Active state, the user must click the ‘Save as Draft’ UI action to save the changes. If your requirement is for the item to auto-save whenever it’s updated, you would need to build custom logic, which would be a significant customization

[Kristin J]

That's just what I was afraid of! I'm thinking I might need to build something into the development process that involves checking for drafts before deploying a change to the item and then if there are some, preserving them or contacting the users, or something....

Thank you for the reply!