I would write my own custom task instance list - use the code from the built in Seam components as examples - use whats there to get the tasks from jbpm and then apply filtering using a loop or whatever.
I was hoping I could avoid a custom implementation, but it seems the only (proper) way to go here, indeed. Thanks for your reply :D
Extending/overriding built in seam components if needed for more complex use cases is often the right way to do it - we would definitely encourage you to do this...
Certainly. And contribute it back, should the code be good and useful for other people as well. ;)
I was hoping I could hook a drools-kind-of-solution here to easily swap it in runtime, or even disable such "filtering" capability as the user sees fit. That can still be accomplished by extending the component, as you suggested, but it implies in more coding - and, a script seemed like a better way.
But I see no problems extending it - the everlasting beauty of OOP in Java =D
For jBPM the 'pooled actors' is in one way nothing more than a string. So there might be a possible different solution
Creating a swimlane with the 'shippers' as assignment/role is possible and you can then have a custom assignment handler attached to this that returns another string with the 'correct value' e.g. shipper-americas, shipper-emea, shipper-south-pole. Which string is returned can be decided upon by e.g. drools based on whatever info you provide.
If you know which area a shipper is in (also e.g. via drools) you can just use the normal group tasklist.