đź‘‹ 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
I think it would be very nice to have something like git implemented in the studio. The current versioning system only lists changes very rudimentary.
Like "Step 2: Advanced command changed" ... if step 2 consists of more than 1 advanced command you have to ask your colleague what exactly they changed or you have to trust them to fill the notes.
There is no diff feature to see or monitor changes done to processes. Also restoring versions is limited to the last 8 (don't know exactly, but very limited) versions.
If you now have someone who clicks safe more often you might sit there with only the defunct version available to restore. In that case you have to go to the database and summon your inner mssql guru to dig that one from the history grave.
Since the content is just a zipped XML file it should be possible to add some kind of versioning system maybe?
This might increase the acceptance by non business users (it developers) a little.
