Currently Robotic assignment shape is accepting static value for Workqueue and Automation activity. This will work only if we have only one dedicated queue for each assignment but we have a requirement to use dynamic routing based on workgroup or other case attributes. For e.g. one robotic assignment can be routed to multiple queue based on "Source System"
The standard assignment shape accepts dynamic workbasket or parameters (like PAram.Workbasket) or we have option to write our own router activity, but Robotic assignment shape does not allow this. Looks to be a limitation There seems to be some validation which says
Param.Workbasket does not exist or is not a valid entry for this ruleset and its prerequisites
With this limitation, other workaround is to replicate the same robotic assignment shape for each work queue and use fork shapes to route to appropriate work queue, which seems to be very bad work around, not easily scalable and difficult to maintain and does not follow best practice. Please advise if there a better solution or if a fix is available.
Some asked a similar question in following article 1 year back but there is no solution. Does this continue to be a limitation at Pega side?