I posted this question several years ago in the forums and was told it was something that was being looked into. I wanted to followup to see if this was on the road map for Workflow or if anyone had found a way around it.

I prefer to develop commonly used workflow activities (such as queries, move/rename/create shortcut, ...) as shared workflows that can be invoked by any other workflow to handle these tasks.  It decreases development time, ensures all workflows use the same query lookup values (should they change), and makes it easier for customer's to design their own workflows, as they don't have to worry about these common tasks.  It is simple to do when working in a single repository, as they all share the same connection profile. The issue arises when I need to run the same shared workflow across multiple repositories.  I'd like an activity to dynamically change the connection profile for the shared workflow, along with all remaining activities, similar to the Change Starting Entry activity.  This could be accomplished by referencing the connection profile, as a token, from the workflow that invoked the shared workflow or just a Routing Decision to choose the profile based on the Starting Entry's repository.  

I am hoping this is coming or someone has found a way around as this will make programming for my large, multi-repository customers considerably quicker to build and update.