Is it possible to configure an RPA robot to pull work from multiple applications sharing a workgroup/workqueue?

Given: 

• Applications App1 and App2, are built on a FW app that contains the class FW-Work-CommonProcess (both apps can access the class & case type)
• Access group App1AG maps to the App1 application with the default workpool as FW-Work
• Access group App2AG maps to the App2 application with the default workpool as FW-Work
• The class/case type FW-Work-CommonProcess routes to a robot assignment to a workqueue (WQ_Common) under the workgroup: WG_Common.

In this scenario, pyGetAccessGroupForRobotByWorkGroup maps the workgroup to the access group.  When the bot moves to the workgroup, its default access group is updated according to the table. The bot will then only pull cases in that workqueue/workbasket, that are under the application of that access group.  This is what we're trying to overcome.  The decision table (pyGetAccessGroupForRobotByWorkGroup) doesn't support multiple access groups. 

We'd like the bot to pull from either/any application, so long as the work item is in that workqueue/workbasket (WQ_Common/WG_Common in this example).

From Angel Hermira's previous comment (https://support.pega.com/question/my-rpa-bot-unable-pick-cases-workqueue): Check the Operator being used and confirm that the default access group is set to the one that you want to use (If the operator has multiple and the default it is set to anything different will use that one and won't get any work). If the AG it is correct, check the roles associated to that AG to ensure that has access to process work. 

This appears to support what we're seeing; that the bot will only pull from 1 app at a time.  Does this mean we must create a new workgroup to support the other application running the same robotic process?  This would also mean we can't use a single bot to concurrently support the same process for both applications.

Any suggestions or clarifications based on our understanding?

Thanks!