Keep a WIP/Draft/partially filled Webform state around

[DiegoPino]

What is this? Yet again another webform thing?

41 and #26 are all ready a little bit high on feature requests so wanted to move this feature to its own ISSUE.

The work i have on #41 allows an orphan Metadata edit session to be recovered if the user followed all the steps and pressed 'Save Metadata' (which will change to a different name) but did not press 'Save' on the Node form. Basically no new Node/ADO was created.

But what if the user goes away in the second step or the form is huge and the user wants time inbetween or wants to come back next day because the huge IMAGE never uploaded but feels not OK with creating the ADO anyway without an image/or because the system admin made the IMAGE upload required for that webform? So many uses cases! 🤣

Well i want to have a 'Save Draft' or 'Keep my progress around' button that triggers something different. It will just save whatever current state the form is in. So if some step is missing, that is Ok. This 'Keep my Progress around' can not generate a new Node until retaken and all steps are finished and we end again with either situation that #41 is dealing with or the node is saved. In both cases the WIP is deleted/purged.

How?

This requires two things to happen

• Another entry in our Drupal private store (means only the same user can see it)
• I plan on having a single one per CMODEL/Webform combination (for new Objecs) or simply based on Webform/UUID for objects being edited and drafts should also auto expire so we don't have to be cleaning stuff around. They can not be edited/nor manually loaded.

Code

• On every Edit/Create (for every a submit process triggered by a special Keep my Progress around button, or even automatic means next/back/save? what do you think) take whatever values are already validated and save them there.
• Next time, on Create/Edit. See if an abandoned session is around (#41). If so, WIP/Draft is not even important and we won't load it. Actually (jajaja coding as i write) i should delete the draft if there is an abandoned session, since it will fulfill the same role! (good i thought of that!)
• If no abandoned session is around, load the draft, but! Here is the beauty. The Draft should also contain the last step the user was in (where they either pressed this Keep my Progress around or auto save happend. And i should be able to programatically move the user to that step.

And will also allow, same as in #41 a button that when a temp is loaded, any of both, you can of course also always start fresh and avoid this values.

@giancarlobi mentioning you here so it does not look like i'm talking to myself (which i am hahahaa) Is my idea idea clear @mitchellkeaney?

[mitchellkeaney]

@DiegoPino the idea is clear (i think)! This will be creating a "Save Draft" button, in other words a way for a user to tell the system "I'm still working, but I want to save where I'm at so I can do something else", which sounds great to me. How does this logic differ from the current "Save Draft" section of Descriptive Metadata? Currently if a user saves their object as a draft, does a node still get created?