This level of job filtering generally requires WVS filter customization and/or Windchill listeners.
We can use the publish filter to exclude undesired publishing jobs via Windchill attribute (e.g. authoring application or file extension). However, there are no OOTB attributes that capture the scope of the submission (number of dependents).
The primary issue with filtering by dependency count is WVS doesn't count the objects until after the job has been submitted to a specific queue group for publishing AND it has entered the Executing state. At that point, it is too late to migrate it to another queue group.
We need to identify object counts before jobs are submitted. One way to accomplish this is thru a CAD-specific customization that populates a parameter with the dependency count upon save. Another option is to use a similar customization or just manually add a ‘scope’ attribute that defines the assembly as large or top-level.
The custom job filter and/or publishing rules can be used once we have a Windchill attribute (usually mapped to a CAD parameter) that defines the ‘scope’ of the assembly.
