cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

The PTC Community email address has changed to community-mailer@ptc.com. Learn more.

Update browser upon check-out/check-in via DTI

Update browser upon check-out/check-in via DTI

User are often confused about the following Windchill / DTI behaviour:

1. Open document from Windchill by clicking on Primary Content or Format icon

2. Confirm "Do you want to check-out" dialog in office application -> browser is not updated

3. Perform changes and chek-in from office application - browser is not updated and still points to previous iteration of document

4. User wants to check if modifications have been uploaded and reopens the document without refreshing the browser. This way he opens the previous iteration -> changes are missing -> user is confused.

Additionally, if the browser is refreshed after check-out in office application, and then refreshed again after chek-in of the document from office application, the browser enters an endless loop "You do not have access to this document or it does not exist."

This is already state-of-the-art in other web-applications and should be supported by Windchill / DTI as well.

2 Comments
sm
1-Newbie
1-Newbie

This is a good idea, but possibly challenging from an application standpoint. WTWindows is busy communicating with Windchill and Office. It does not have any knowledge of open browser sessions connected with Windchill. PTC would have to add a client or server side query to find any and all connections opened by the current user and push a refresh action from the client or server to these browser(s). Maybe that's easy to do, TBH, I am not sure.

Regarding the browser refresh, it should resolve to the latest iteration of the document. In my test case, I opened the Details page for a document, opened the Word file directly from the format icon, checked it out on the fly, made changes in Word, saved and used the Check In option from the DTI ribbon. This did create a new iteration of the document, but when I came back to the browser and hit F5, the iteration bumped from A.4 to A.5. I did this test with 10.2 M030 in Firefox.

olivierlp
Community Manager
Status changed to: Archived

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.