I am not sure when the
Save Draft button should be available to (or enabled for) users. I want to be sure to explain this feature correctly and am not sure if I'm looking at an environment issue or if I'm just missing expected behavior. Does this sound right?
- While editing text in the UI Update (Experience Manager or XPM), the
Save Draftbutton appears unavailable (grayed out) until I change fields or otherwise click off of a given component presentation.
- Then for a brief moment, before XPM saves a minor change (e.g. "version 1.1") to the edited component, the
Save Draftbutton is available and appears click-able.
- It quickly becomes grayed out again.
In case its meant for page changes, if I insert a new component presentation, XPM will prompt me with "All changes have been saved" and
Save Draft isn't available.
Are there scenarios where I would be able to manually press
Save Draft? And is clicking outside of a field the right way to have XPM recognize we've made changes to a component (and save minor changes), for just a selected component?
Session preview isn't enabled for this environment, if it happens to affect the button's behavior.
Edit: I found one scenario where the button stays available: edit a text field then select the
Properties button in the toolbar. The
Save Draft button will become available and stay selectable until you click elsewhere. :-)
To be clear, I don't care that XPM saves changes quickly and that
Save Draft is rarely available. I'm just wondering when we'd actually need it. Maybe it'd be okay to remove it in a GUI extension even.