Conflict upon Attempt to Modify
If you attempt to modify a workspace object that is not checked out (and also not locked), then upon attempting a check in, the system presents a Conflicts window, informing you that the object is read-only because it is not checked out. You can choose to resolve the conflict, using one of the following options.
• Check out now – Perform an immediate check out on the object, enabling you to modify the object and later check in the modifications.
• Revise and Check Out — Replace current file with the first iteration of a new revision, checked-out to the workspace.
• Continue – Continue, with modifications saved to the active workspace with a locally modified status.
|
|
You can upload locally modified objects to the server-side workspace when the Allow Upload with Numbering Conflicts preference is enabled (set to Yes). However, you cannot check these objects into Windchill without first updating their temporary number.
|
If your attempt at modification involves several checked-in objects, you can specify different resolutions of the conflict for each object, or you can use the Set All menu to apply the same resolution to all.
The following figure shows the Set All button on the Conflicts window:
