I have created a Part with Rev A and moved the part to release state.
When I try to edit the Rev A (which is Released), it revised the item to rev B and changes are effective in Rev B.
When I edited the Rev A again, then it created a Revision Rev B again.
In this case I have two item with the same type, name and Revision with the only "Generation" field as unique.
Is the Type, Name, and Revision are not considered as unique in Aras? If not what is the reason for not considering the Type, Name and Revision as unique.
Until a revision is released, updates will only keep revising the generation. When you open an item, unless otherwise specified, the latest revision and generation will be opened.
If you want to always create a new revision, you could create a lifecycle map which automatically releases an item, but you could wind up with a lot more revisions than you want.
I'm not sure that it was vishnu's problem. His issue is that, when you lock and save a release item, it creates a new version in preliminary state and if you do it twice you have another item with the same version. Yes, we had some people testing Aras Innovator and finding this annoying. But guess what! Aras is open ! and you can easily insert some script, VB, C# or javascript to make sure it doesn't happen if you don't want this behavior. I'll get back to that post later to post some code to fix that. The thing is that different companies could have different way of dealing with it. You may want to disable a second lock to a release doc or you may want a dialog page asking you if you want to replace the already created new version...
How would you want it to work?
Yoann