Revision History and Undo/Redo in Rich Text Fields

  • siemonco
    Asked on June 17, 2021 at 11:49 AM

    This is a feature request. I have had many instances where I was editing a rich text field, and when I clicked on the field, all of my text disappeared. The form saves changes far too quickly, and finding the method of undoing a change is not intuitive. Also, when undoing a change, the revision history doesn't seem to provide enough. The latest example (this happens all the time) is on the form in the link. I had a rich text field at the top. When I clicked the field to add text, it all disappeared and I couldn't figure out how to undo it. I went back to the field a few times looking for a way, then exited the form to see if I had the text saved in another version. When I didn't, I went back and found the revision history, but it only saved one step, so the prior version of that field was also blank because I clicked in and out of it. 2 things I would like to see:

    • Undo/Redo buttons front and center in the UI
    • More robust revision history
    • An option to have a save button rather than the constant auto-save

    Thanks

  • Andrew Manager of Enterprise Frontline Support
    Replied on June 17, 2021 at 6:23 PM

    Hello there,

    Thank you for your feedback! I will be escalating this thread to our Developers as a Feature Request, as per your request. The manual saving options and undo/redo buttons are both great ideas and fairly self explanatory, however, if you could provide some additional details regarding the features included in the "More robust revision history," this would be extremely helpful.

    For the time being, if you are ever working on a form, and accidentally make an unwanted change that is immediately saved, you can always revert this change quickly by clicking CTRL+Z on Windows devices, or CMND+Z on Mac devices.

    In order to keep these requests as granular as possible when escalating to our Developers, I will be splitting the features you are requesting here into three separate threads. This thread will be used for the "More robust revision history" request, and we will hold off on escalating it until we get some more details here.

    Your other two requests will be moved to new threads prior to being escalated. These threads can be found here and here. I will respond to you via these threads as soon as they have each been escalated, and as previously stated, will escalate this thread as soon as we have a few more details.

    Thank you again for your feedback, and have a great day!