• Replies 6 replies
  • Subscribers 43 subscribers
  • Views 7639 views
  • Users 0 members are here
Options
Related

Will the upcoming Innovator 12 edit concept lead to tons of nonsense revisions?

AngelaIp

Hi,

I think this one is a good topic for a Community discussion.

I have seen the Aras Innovator 12 demo at ACE Europe 2018. One upcoming UX enhancement is a simplified way to edit an Item. I really like the new concept, but I wonder if it will eliminate the ability to overwrite existing generations when using the automatic revision mode.

Let´s assume we have an Item with Versioning Disciple “Automatic”. Typical use cases are Methods, Workflows but maybe also the standard Parts or Documents.
As long as you have locked an Item, the existing Item generation will be overwritten while editing. The current “Lock” helps to prevent that every little change leads to a new Item revision.

But as far as I have understand the demo, “Lock” will be removed in the upcoming Innovator version.
Of course we have the option to choose by our self, if we want to use Automatic or Manuel revision mode. But especially for core ItemTypes, it isn´t wise to change the revision mode.

What does the new edit concept mean for the automatic revision mode? Will we now get tons of nonsense revisions?

I am already looking forward to your opinion! And I hope Aras will correct me if I got things totally wrong.

Best regards!
Angela

Parents
  • Offline

    Leaving a door open is now impossible in Innovator 12. In Methods in particular, you are compelled to always generate a fresh Version of a Method, even if you merely closed the window by accident. At all times, the claim flag is automatically removed. geometry dash breeze 

  • in reply to Ericalynn

    There is actually a better solution available. Just deactivate the Automatic versioning in the Method ItemType! This way you always overwrite the current version and can create new version on demand by some relationship action. 

    That´s the Method I right now currently use in ALL Innovators I work on (I have a script to set it automatically on new instances). I even spent the time to cleanup all unnecessary method generations. Using manual versioning has the risk that you actually destroy Methods when you don´t pay attention, but that´s what backups and test servers are for. This way I can even add a revision history to the Method that actually matches the Method generation which truly ensure to "preserve the business meaning of versions". Sunglasses

Reply
  • in reply to Ericalynn

    There is actually a better solution available. Just deactivate the Automatic versioning in the Method ItemType! This way you always overwrite the current version and can create new version on demand by some relationship action. 

    That´s the Method I right now currently use in ALL Innovators I work on (I have a script to set it automatically on new instances). I even spent the time to cleanup all unnecessary method generations. Using manual versioning has the risk that you actually destroy Methods when you don´t pay attention, but that´s what backups and test servers are for. This way I can even add a revision history to the Method that actually matches the Method generation which truly ensure to "preserve the business meaning of versions". Sunglasses

Children
No Data