Skip to main content
J
JJ_110711536-Contributor
6-Contributor
August 25, 2025
Question

Default WNC Action for document opened in authoring CAD application.

  • August 25, 2025
  • 2 replies
  • 335 views

Version: Windchill 12.1

 

Use Case: Client would like to avoid changes on the modified assembly that is not closed in CAD system session (comes from not latest version), but it indicates in workspace as latest after update(Do not Close action). Thus he would like to know if there is a possibility to set allways default option for "The document is open in the authoring application.Would you like to close it?" = Close and Update


Description:

Scenario:

1. Open in workspace non-latest iteration of CAD object.

2, Some changes are made on the level of the main assembly fe. colour of the components are changed.

3. Save in CAD application is made

4. Item is not checkout message.

5. Item is not checkout - continue action for all components/subassemblies except main assembly, for which check-out action is selected.

6. Message: Assembly can not be check-out as it is not latest iteration.

7. Wokspace refreshed, main assembly with status modified and still in non-latest revision.

8.  Update out of date vesions used on main assembly.

9. Conflicts window: "The document is open in the authoring application.Would you like to close it?" 

At last step we can choose "Close and Update/Do not Close" -> client want to disable/hide "Do not Close" option and have all the time "Close and Update" option active/set as default without conflict window pop-up. Is it possible?

10. If option "Do not Close" is choosen in workspace the latest version of CAD assembly is active with modified status, but in session we have old version which can overwritte newest one - clinet would like to avoid this scenario (it can be now check-out and check-in).

 

This can be related to this article : https://www.ptc.com/en/support/article/CS421866?source=search , but there was no option to have this conflict window hidden with one default option choosen ("Close and Update" or "Do not Close". Is it possible now?

 

2 replies

Catalina
CatalinaCommunity Manager
Community Moderator
August 28, 2025

Hi @JJ_11071153 

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant.

 

Best regards,

Catalina | PTC Community Moderator
avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
August 28, 2025

I do not think pursuing changes which would be customizations to workspace functions (and likely the CAD version/WGM version) would be fruitful. If this is something they really want to pursue, this should be a Windchill Idea and they can post a write up there.  From reading this, is the client concerned that they might accidentally modify the assembly? Not possible since its not the latest but if they locally modified, updated, checked it out and then back in, that's a lot of steps and not in the realm of accidental errors that we should customize to avoid. Some responsibility is on them.

Certainly locking items from check out is key to avoid accidental modifications. You can also prevent local modifications on unchecked out items from being saved to the workspace locally. I believe there are preferences on this. They also should keep their workspaces up to date on a regular basis. I tell my users to periodically clear their workspaces when done and redownload so they do not linger for weeks with old copies. Just know so long as they do not update and then check out a locally modified file, there should be no risk of accidentally check an old copy back in. 

There is an option when you  update to overwrite local content. That is No by defauly but if yes, it would replace that locally modified assembly with the latest during that update step. There are cases I can see where a user might want to do this and in the UI, you can always toggle this per user demand.

Terms & ConditionsCookie settingsAccessibility statement