Has there been any thoughts into having a change acceptance or rollback function? Collaborative software is nothing new, but there have been a few tricks I've seen to handle such efforts incase a change is made that the primary author doesn't want. I've seen my fair share of content roll-backs.
I get the option to do both. In one instance I use collaborative projects as on-boarding mechanisms for new trainees. It allows them at a point to get their hands into real work. A rollback feature can ensure a safety net if they break something. Imagine they deleted a module accidentally. Once a change is made, it's set. That can be dangerous in collaborative projects.
Second case is common with SME work. I've had them pull old content back in (or want to). It'd be nice to roll back to a previous version.
4 Replies
Hey James!
Great question :)
You have the option to either collaborate and work together or send a copy to work independently. Take a look at this comparison.
If you do have a strong use-case for roll-back, please share the details here so that we can better understand.
Hey Leslie,
I get the option to do both. In one instance I use collaborative projects as on-boarding mechanisms for new trainees. It allows them at a point to get their hands into real work. A rollback feature can ensure a safety net if they break something. Imagine they deleted a module accidentally. Once a change is made, it's set. That can be dangerous in collaborative projects.
Second case is common with SME work. I've had them pull old content back in (or want to). It'd be nice to roll back to a previous version.
Thank you for the details James - I'll get a feature request submitted on your behalf.
Would have been useful...
This discussion is closed. You can start a new discussion or contact Articulate Support.