đź‘‹ Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!
If you have questions about Nintex Ideas, please contact ideas@nintex.com
If you require support, please visit Nintex Customer Central
If you have a sales inquiry, please contact sales@nintex.com
If two contributors edit a process at the same time, there is no indication of a conflict until you save and get an error saying you can't save because you're not in the current version. An automatic checkout when you start editing, and an error right away if someone else is already editing, would same much time, lost work and frustration with using Promapp. Even a manual checkout would be better than the current state.
I agree, we have had instances where there have been multiple SME's editing a single process, it's time wastage. A simple checkout or locked feature would help avoid this.
This feature is sorely needed, as some of our processes require collaboration between a group of Subject Matter Experts who work remotely and across time zones. We have had multiple instances where two Process Experts or Process Champions are editing separate sections of the process at the same time and they get the save error.
A check out feature (against the sections being edited), or a feature which allows live collaboration would be amazing
Just some helpful tips. I created our guide/framework to follow that eliminates this risk by showing ownership during creation of a new process and ownership of making edits to a publish process. Example: A new process developed is sent to Group Champion on confirm process workflow/mapping. During this time, the Process Expert knows they cannot make any edits. It works very well