Looking at business processes, users should not be able to revise by clicking on Revise. This should be done following a process which is known as Change Management.
That is the change objects associated with that object will have all the necessary information to say why such object has been revised. There is a difference between iteration history and revision history. The revision history depends on the change process.
That is the reason why I voted down this idea which to me is not good data management practices. since it means that Change Process is not implemented.
not all are using the change management process. There are a lot of small companies, which using PDMLink as CAD data management and there is a function like this very welcome.
let's say A.5 is released. You create a new revision and create B.0 at that stage B.0 is not really different than A.5, the file content is the same, the attributes are the same only created by, modified by and version is different but really your CAD file is identical.
The user will have to check it out and back in to make a change in the system and this will create B.1. Is the iteration comment to check in the working copy of B.0 not sufficient enough ?
If you have the possibility to add an iteration comment for B.0 well B.0 has not changed really.
I still can see why it will help to add a comment while revising. All this information can be added when creating B.1
I appreciate that the origin of the idea if for when people are not using CMII but in that not defeating the object and transforming Windchill to fit requirements which should not happen at the first place ? ie why not simply implementing CMII rather than always find work around and putting plaster ?
If it is like if I buy the best car in the world (let's say a ferrari Enzo) and I ask Ferrari to higher the frame, but off road tired because live in the moutain where there is no road ? Well I should be not buying a Ferrai but a 4x4
another possibility would be that a user can add a set state comment. Before the engineer is going to release the objects again, he knows what he actually changed.
@Chris: I understand your point of view and I'm on your side, but unfortunately it's not that easy....
