We have the need to upload a Lifecycle Template that references an abstract parent type rather than multiple instantiable child types. Currently, the lifecycles must reference an instantiable type (like WTDocument) in order to be uploaded. Here is our scenario.
We have a structure of types based on a custom Modeled class. This structure includes an abstract parent type with multiple instantiable child types.
ModeledClass
- AbstractParent
- InstantiableChild1
- InstantiableChild2
- InstantiableChild3
All of the instantiable children types use the same Lifecycle and Workflow. We have limited the lifecycle to a specific object type, rather than have it available for all object types (WTObject). Our process uses a load file to load the lifecycles and workflows into various Windchill environments (Development, Integration, Preproduction, Production). In order to load the lifecycles, we have to change the AbstractParent to make it instantiable before loading the lifecycle. Then after loading the lifecycle we have to change the AbstractParent type back to being uninstantiable.
If the AbstractParent is not instantiable at the time the workflow is loaded, this is the warning we get:
Warning: The com.myCompany.ModeledClass|com.myCompany.www.AbstractParent supported class is not found in the current system. Attempting to create the Life Cycle without a supported class specified...
