Currently to perform a workflow task on objects in Products you have to use some change object, a promotion request, Change request, notice, etc. This requires the objects to have a transition, and promotable/changable state. The "Route" option exists in Projects but not in Products/Libraries/etc. It should be able to be used on all file types in all contexts.
We have found a great deal of usefulness out of workflows that do not change the state of an object. Today we use promotion requests to run these workflows but do not have it change the final state of the objects, or use Under Review and set them back to In Work. If the objects do not have a promotable state it causes a failure.
Today the current alternative is to create customized actions. Which can be time consuming and requires validation with each update to Windchill.
Our users have adapted to using Promotion Requests for things like peer reviews, but they aren't technically being promoted. Route or some other non-change object seems like a more logical place for these kinds of workflows.
Adding this functionality would open up the workflow configurable side of PDMLink and allow for a lot more workflow utilities without full customization. Workflows can be really powerful if not restricted to the change object restrictions.
Move to Library with approval - Moves models/files to a library after approval from the librarian
Revision matching - If a new weldment member is added this workflow will update the revision to match the parent assembly (We keep all design revisions matching for an inseparable assembly)
Peer Review/Notify - We use promotions today, but this could easily be done in route or as a notify route.
Mass changes - We don't have this today but some actions could be done via workflows