While a user is making changes to any rule or data element, autosave the changes periodically (e.g. every minute). If the user is logged out automatically – which erases all unsaved changes, the user can have the option of recovering from his last auto-saved state and pick up his work from there.
The autosave does not need to create a new revision automatically. New revisions should still be made when the user saves manually.
At bare minimum, auto-save before log out!
I'm interested to know if viable option would be to notify the user, say, a minute before the auto-logout and allow them to continue their session if they would like. A sudden auto-logout is no good.
@aahardy That would be slightly better, but the problem is that users are often on another tab (or off grabbing some coffee or something)- if they're inactive for long enough to auto-logout, they're probably not going to be there for the warning either.
Agree with @jenn9 that auto-logout wouldn't be the ideal solution here. Also because it still requires human intervention, which defeats the purpose of doing something automatically.
I'm thinking of something like Medium's interface where, as you type an article, it saves the draft periodically on its own.
We're thinking about the UX on this. I'd love any feedback y'all have. Here's what I have so far...
If you have other thoughts on how this should work, please let us know!
@markhicken , my responses:
@analytics_union Thanks for the feedback!
I love the idea of doing this at the base resource level (rule, data element, extension). Do you think it still makes sense to do this at code editor level even if we do it at the base resource level?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.