Create packages containing only specific softtype

[Alexander_Bgrd]

Is it possible to create a package that contains only a specific document softtype (reference documents).

What I'm trying to achieve is the following:

• Select a WT-part
• Add to package
• Create new custom package (custom package type is already set-up)
• Then the collector should only add reference documents (incl. reference documents for all dependents) but not described by documents

I could achieve this by filtering during the collector stage using the type filter, but I'm looking for a way to achieve this as a default setting, so that when the custom package-type is selected only that specific softtype of documents is included as content.

I tried working with the package type-based properties, but couldn't get that to work, because the content-role-type for both reference and described-by documents is Primary.

[d_graham · Accepted solution]

@Alexander_Bgrd 

One solution would be to create a custom action in the WTPart’s action menu named Create New Custom Package, or whatever.

When you select this action the action can run code that does EXACTLY what you have specified.

If you create these custom packaged a lot it’s probably worth doing.

Implementing this solution is simple and it’s very easily moved to other Windchill systems, including upgrades.

The of doing it this way also takes human error out of the package creation. There’s a lot to be said for automatic, bombproof solutions. 👍

Something to think about.

If interested send me a private message with exact specs and I’ll get it working.

David

[joe_morton]

Another way you could potentially achieve this is with a custom workflow:

• Create a new life cycle template for the custom package type
  • here I'm assuming you have other package types that should behave differently
• configure the first state to initiate a workflow
• in the workflow, add robots to automatically add/remove documents to the package per your requirements
  • with the ability to add and remove in the workflow, it doesn't matter what the package's default collector does

Easier said than done to be sure. Some benefits here is that with the workflow already running, it could help with downstream business processes. Maybe you can assign tasks or send notifications, etc.