Skip to main content
P
pwilliams-313-Aquamarine
13-Aquamarine
February 24, 2012
Question

Change Notice - Checkout Question

  • February 24, 2012
  • 6 replies
  • 1912 views
Windchill 10.0 M020

Hi Everyone,
For those of you familiar with the Change process, I have a question for you. Why is it that I cannot perform a checkout (or Add to Workspace) operation on the objects that are in the Resulting Objects table within a Change Task? I have to click Info on the objects first and then check it out from the Actions menu.

[cid:image003.png@01CCF301.9ED8D8B0]

Patrick Williams | Engineering Systems | o: 616.698.3766 | c: 616.947.2110
[cid:image004.jpg@01CCF301.9ED8D8B0]

6 replies

M
MikeLockwood22-Sapphire I
22-Sapphire I
February 24, 2012
We'd like this as well.
D
ddemay1-Visitor
1-Visitor
February 24, 2012
It's probably just configuration of the actions ? Not too difficult to add?


Sent from my Verizon Wireless BlackBerry
S
sdrzewiczewski10-Marble
10-Marble
February 25, 2012
Unfortunately add to workspace and check out actions do not work in the resulting data tables. This is true for 9.1, not sure about 10. I know there some talk about adding this not sure if it was for 10.1 or just future versions.

Steve D.



P
pwilliams-313-AquamarineAuthor
13-Aquamarine
July 10, 2013
If I am creating a change notice for 2 objects that live in 2 different products, each product has different team participants, who then becomes the Reviewer? Is it possible to prevent a change notice from containing objects that live in a different product context from the product context in which the change notice was created?

Patrick Williams | Engineering Systems | c: 616.947.2110
[cid:image001.jpg@01CE7D5C.B79C2550]

D
ddemay1-Visitor
1-Visitor
July 11, 2013
If they can't read the data in the other product, then they can't add it.
Otherwise, have to detect location and revise programmatically after
submission to remove from affected or spin off a derived CN isolating said
products. I could see that two furniture components being completely
unrelated, but having a similar team member handle same approval/rejection
being an issue here. In lieu of altering the UI, the detection algorithm is
best. Altering UI might include utilizing a different data utility or form
processor to search for affected, but then this doesn't get around OOTB
searching, so best to detect and remove undesired but affected from the
object itself, optionally revising the CN and setting older rev of CN to an
appropriate state with record of cause.



Hope that helps.




S
srector1-Visitor
1-Visitor
July 11, 2013

I haven't tested this, but, wouldn't the CN pick up the Teaming information based on the Product it was created in, rather than from the contexts of the models/drawings?

Terms & ConditionsAccessibility statement