Change (correct) behavoir of the Update command in DTI Office add-in

[afabre]

The Update command in DTI:s Windchill Tab (MS Office add-in) in does not update the downloaded Primary-Content-file to the latest Version in Windchill as the tool-tip states:

It updates to the latest Iteration of the downloaded Primary-Content-files Revision (which is not necessarily the documents latest Revision).

Suggestion: Include a config option for choosing between Iteration or Version update

[smorris]

Hi, please see original discussion thread here: https://community.ptc.com/t5/Windchill/inconsistent-instructions-in-DTI/m-p/12541#482213

For some reason, commenting was not available for this idea, but Toby Metcalf‌ just fixed it up.

The summary of the discussion is that this is valid idea, but needs to account for the ability to choose between Iteration update and Version update. Windchill DTI currently only supports Iteration update, unlike CAD Data Management which supports the update paradigm defined by the Workspace's Config Spec.

Alexander Fabre‌, can you update the idea to include a UI option for choosing between Iteration and Version update and add one or more DTI Tags?

[afabre]

Ok, but I think a config setting rather than UI option is in place: if the approach towards document users is that a workspace concept is too complex, then grasping the implications of a iteration vs a version update should be so too.

[TomU]

I like the idea of a preference controlling this behavior.  For those who use DTI on a daily basis, do you really want to update only to the latest iteration of an object or would you prefer to go all the way to the latest version?  If you already have the latest iteration of a revision and run this command a second time, should it then go to the latest version?

[smorris]

I'd guess the differentiating factor would be context. If you have a Product hosted document, then Version updates are applicable when available. If you have a Project hosted document, it can only update to the Version available in the Project, which could be a new one or might not. If the document originated in the project, it will not have any Versions. If the document was Shared to the Project, it could have new Version available, but the Project context would need to be updated to make the new Version available.

The UX is tricky. You'd like to keep the options open to the end user, but it is better as a preference or interaction? Would you always choose one type of update vs. another? Would all users understand their is a preference to control this? Would an admin like to "lock in" the preference so their system only works one way?

I'm not a big fan of prompts, so I guess I'd lean toward a DTI preference that allows me to easily change the setting w/o navigating to Windchill to perform a Windchill preference change. Maybe the DTI preference does that for you?

[TomU]

If update simply went to the latest available, wouldn't that be universally consistent?  If the project doesn't have the latest version shared to it, then clearly there is nothing to update to.  It seems like you should get the latest version available in the product or project that you have permission to access.

[olivierlp]

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.