Windchill Packages are great, but they could be easier to work with. When we create a package, we have to seed it with objects. Then we have to configure the collector. Then we have to apply a filter.
All of these are on different screens and there is no way to save a "recipe" to use on the next package. We can set collector defaults, but we need different collector settings for mechanical vs software vs electrical. We need different filters for different recipients ( supplier vs customer ).
There should be a single screen that lets us configure all of the settings in one place, and save the configuration as a template to use again.
Once a package is locked and a delivery is created, there is no way to see the "recipe" that was used to create it.
We need clarification on how packages are actually pulled together. For example we might seed a package with a Part 123 Rev A and Document 123 Rev B. The Part is Described By Document 123 Rev A.
If the collector is set to pull Documents for Parts. Which Rev or Document 123 will be in the package?
What if we apply an effectivity date filter and Part 123 Rev B is effective? Will it keep the seeded Part or replace it to meet the spec of the filter? What if Document 123 Rev was effective on the same date?
We should be able to guide the process with a series of check boxes.
Seeded overrides collected.
Filter Rules override relationships.
