This thread is about a request to change how Creo displays information. WIthout changing Windchill to a Push system, there can be no enhancement to Creo to allow it to display information the Windchill client doesn't have.
As you know, ProductPoint was built on SharePoint, an entirely different platform, and is no longer available.
The only objection I've gotten to a Windchill Push system is the bad behavior of a third-party app that could be resolved in a number of ways.
"Without changing Windchill to a Push system, there can be no enhancement to Creo to allow it to display information the Windchill client doesn't have." I disagree. The Windchill client does have this information. Out of date status and checked out status are both already visible in the workspace just like state and version. All that is being asked for is the ability to display this information directly in the Creo client. No push is required. Anytime the workspace is refreshed the Creo session will simply reflect it (again, just like it does now for lifecycle state).
I don't see the gripe about Pushing or Receiving. It is not that important and I would let PTC programmer’s argue between themselves. I can say this:
If I drag and drop a part into Creo and save it to my workspace, Creo is the one pushing up the status, attributes,… and not Windchill. That is how I see it.
The main idea is for Creo to take over some of the info that is on the Browser. BTW we already can display about 80% that I’m proposing with ”display_full_object_path YES”. It is only missing 2 items.
I think this improvement is very small and attainable, and may not add much for some users, but If we all vote for it, this will be a big step for all the members of the ProUser groups. An enhancement voted and done by us. By the users for the users.
And if PTC does not respond one way or another, it will be a big letdown. No users will bother to participate again.
As long as Windchill is a Pull system the user can never know the status of objects without specifically running a query or update; the information is not available to the user unless the user asks for it. Under the Pull system, the only way around this is to continuously poll Commonspace for status. Continous poll is not going to make anyone happy.
"Anytime the workspace is refreshed the Creo session will simply reflect it (again, just like it does now for lifecycle state)."
That's exactly what Pull means. The user is not notified that the model he has opened is in any state until that information has been Pulled by request from Commonspace. The state could change one second later, and the Workspace would not be current, unless the user Pulled the information from Commonspace at least that frequently.
If the user opens a model and works on it and saves it, he will not be notified that someone else has checked it out until the Workspace is updated with status information that the Workspace client has to Pull using a request from Commonspace.Only then will it be clear the modifications are either going to require discarding and re-doing or Integration.
This is in distinct difference from a Push system, where the modified model would be flagged without any user-side action on the client to refresh the Workspace status. The Push system would allow a flag to be raised within some arbitrary small amount of time after the Commonspace status of the part changed.
"If I drag and drop a part into Creo and save it to my workspace, Creo is the one pushing up the status, attributes,… and not Windchill. That is how I see it."
Creo is Pushing a request, but Pulling the results. This is about Windchill status getting to the client, and that is only available from Pulling.
Suppose one of these two conditions:
1) Someone who knows you sends you a gift.
2) To get a gift you have to ask everyone you know if they are going to send you a gift, which they won't send until you ask. If they don't have it at the time, but decide to get one later, you have to ask everyone again.
The first is the Push system; the second is a Pull system.
"If I drag and drop a part into Creo and save it to my workspace, Creo is the one pushing up the status, attributes,… and not Windchill. That is how I see it."
Creo is Pushing a request, but Pulling the results. This is about Windchill status getting to the client, and that is only available from Pulling.
Suppose one of these two conditions:
1) Someone who knows you sends you a gift.
2) To get a gift you have to ask everyone you know if they are going to send you a gift, which they won't send until you ask. If they don't have it at the time, but decide to get one later, you have to ask everyone again.
The first is the Push system; the second is a Pull system.
To answer your original question, all of the shown in the image below are OOTB (Out of the Box). What you need to do is create a CUSTOM view for your users.
If you place you mouse over the icon it will tell you the meaning.
Yellow box - checked out to me + - modified locally clock - out of date object person icon - object checked out by John Doe or whoever
Lance Lie Sr. Info Sys Technologist II Global Business Services - Information Technology Raytheon Company
This message contains information that may be confidential and privileged. Unless you are the addressee (or authorized to receive mail for the addressee), you should not use, copy or disclose to anyone this message or any information contained in this message. If you have received this message in error, please so advise the sender by reply e-mail and delete this message. Thank you for your cooperation.
