I have a requirement where we want to introduce versioning on CR / CO. I know this is possible since if we look the APIs for these change objects, it has "iterated / Versioned" mentioned. See attached snapshot
hance was just thinking if there is a switch to turn on either versioning / iterations on CR / CO.
To add a confirmation step for revise action follow the step - https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS159794
I too was wondering if there could be version/iteration control on CNs/variances. It is a bit confusing to users where if you searched for a change object or even looked within the product's changes folders, you would see the change object's version (ex, 1.1, 2.1). Yet within the actual change object there is no iteration. If version/iteration control is not offered on change objects, why do you display it as a Version on searches and folders?
Windchill offers change and revision control on change objects. This feature is controlled by a preference and is turned off by default. To enable this functionality, set the value of the Change Modification Tracking preference to Yes. This is in Preference Management > Change Management
Then you have to enable revise transition in the corresponding life cycle template.
This will enable revise action in the options
The interesting thing this action will not prompt a confirmation before it actually revises the CR. You click the revise, the revision will change.
To add a prompt follow the steps in https://support.ptc.com/appserver/cs/view/solution.jsp?n=CS159794
Excellent....but then can I track what users has changed / modified / added what to the Change Objects?
I would also like to compare the differences between the different revisions? is this possible? like its available in WTPart and WTDoc objects "Compare Info" icon?
I don't see that option. However, you state that it offers change and revision control on change objects (which we already have - CN123456 Rev 1, Rev 2 etc.) but what we were looking is the ability to iterate change objects (CN123456 Rev 1.1, Rev 1.2, Rev 1.3, etc.)
Never noticed before that change objects are displayed with an Iteration (e.g A.1 or 1.1). Seems like this must be from using a common component for display only.
We've done about 40,000 CR's in Windchill - all with Revisioning enabled. Thinking about the comments here and wondering if Iterations would help.
In general, users create change objects and may edit many times, but then submit. After submission and during routed approvals, no changes are allowed; assume that most approach this way (equivalent to not being able to change a paper document with multiple signatures after obtaining some of the signatures). Any changes require a new Revision, possibly with edits, then re-submission. For this reason, I'm not seeing the value of Iterations - but may be missing the point.
A compare tool of some kind would in fact be very helpful.
Note: Another major consideration is the linking between change objects with Revisions. If for example you have a Problem Report with 2 Revisions, linked to a Change Request with 3 Revisions, linked to a Change Notice with 2 Revisions, and then maybe a Change Task with 2 Revisions >> nagivation is always latest to latest. Query Builder Reports may or may not grab latest. Change summary reporting should be examined closely for intent.
Mike - our users are concerned more about the after submission and during routed approvals (but not yet approved) where changes may have to go back to rework (due to reviewers/customers comments). The customer states they can't really tell what changed since the CN doesn't iterate. They want some way to distinguish that there have been updates to the change object. Yes you can put comments on the object that you updated it but if you were to resubmit the CN (for example) to the customer there is no indication on the CN or its history that it has been modified/updated. (For example on documents, during the review cycle, when you add attachments and make changes the document iterates until such time that you release it (Doc 123456 Rev A.1, A.2, A.3). Once it is released, you would then revise the document. (Doc 123456 Rev B.1)). Our users/customers would like the same concept for change objects (CN123456 Rev 1.1, 1.2, 1.3) and then once it is approved you would revise the change object (CN123456 Rev 2.1).
Valid points - Confirms (as always) that people approach things in different ways - and it requires the system to be very flexible to accomodate.
For now, Only Revisions are available so appears that using the Idea forum is best to request Iterations. If PTC does add Iterations, hopefully it will allow keeping things as they are (Revisions only) for customers who choose this.