Skip to main content
K
kpritchard1-Visitor
1-Visitor
October 7, 2010
Question

Change Task (wtChangeActivity2) Soft Types?

  • October 7, 2010
  • 4 replies
  • 1137 views

Has anyone out there attempted to soft-type wtChangeActivity2? With success?

Conceptually, I'd like to give users the ability to create more robust Change Implementation Plans to define a Change Notice. As an example, a BOM (WTPart Structure Change) that involvesremoving a component (Part) being made obsolete and the creation of a newcomponent as direct replacement. The challenge is that each of these elements isideally routed differently. ThePart Structure Changemight go to Manufacturing Engineering department internally, theNew Component to supplier selection and Purchasing and the Obsolete Part would go to the warehouse to disposition inventory and include a set stateExpression Robot(to Obsolete - any insights on accessing container contents andwhatcode snippets would need to look like?)

4 replies

M
MikeLockwood22-Sapphire I
22-Sapphire I
October 7, 2010
We investigated using multiple CT types but backed off once we found that there is no way to avoid having the Change Task that is created with the Change Notice be the first (alphabetical) CT Type that exists. After that point, users can select from available types but there is no UI to select the type of the first one.

We know of one Windchill user who has this workaround:

- Allow the system to create the first CT with the CN using the default CT type

o With ACL's, allow no users to see that CT type so it's hidden from all

o Make the workflow on that default CT type just have a start and end

- Have users create all needed CT's with appropriate type selection

We almost went down this path but it seemed really non-elegant. Still looking for some options. Meanwhile, we have a hugely complex workflow for our one CT type, with lots of branching.
S
ssenthil1-Visitor
1-Visitor
October 7, 2010
There is a preference setting for choosing the change task type.



The description states




Set Preference


<
K
kpritchard1-VisitorAuthor
1-Visitor
October 7, 2010
Definitely interested in the "don't create Default Task at Change Notice
creation! It will actually simplify some autonumbering of Change Tasks
(based on Change Notice number)

Keir Pritchard
Senior Designer & PLM Specialist | Westport Innovations Inc.
604-718-1948 | kpritchard <">mailto:kpritchard@westport.com> @westport.com
www.westport.com
M
MikeLockwood22-Sapphire I
22-Sapphire I
October 7, 2010
Tried this - helpful for user-selections in the New CT wizard. Does not govern the initial creation. Regardless - you want a choice to be presented for the initial CT, not a preference.

From: Swamy Senthil [
Terms & ConditionsAccessibility statement