As mentioned in one of the responses about changing the manager for the default@TGB workgroup to Admin@TGB, the problem of stuck routings is gone. But that is not the root cause of the problem. After changing the workgroup manager, all the approval assignments now getting routed to Administrator. The primary problem still is that the routing is not able to locate the Manager@TGB operator and thereby routing it to the manager of the workgroup. Can we have someone from the exercise development team or an SME look at this and figure out what is wrong with the routing? The Manager@TGB operator is very much available in the system and is selectable at design time.
In the audit of the work object/case, system is saying "This assignment has been reassigned to Operator Administrator@pega.com, as Manager@TGB is unavailable". The same issue happens if i route work object to any oprerator ID. But i could see, all these operator ID exist in the system.
I suppose that you don't need solution anymore but maybe it will be useful for any other who will face the same issue in the future and will look for it in pdn.
Why you are getting the error in audit log like "This assignment has been reassigned to Operator Administrator@pega.com, as Manager@TGB is unavailable"? Is clearly explain under below link but maybe not directly ;) .
The thing is that in this exercise you have to assign your case to particular operator which has some specified working hours e.g 8am - 4pm from Monday to Friday. I suppose that you were do your tests (online training practice exercise) outside these hours, I mean at the evening, weekend or different time zone that is assigned for Manager@TGB user in PEGA. This has resulted that when you had created your test case the Manager@TGB was beyond his working hours so PEGA according to the logic described in the link above, reassigned the case to the WorkGroup Manager. A workaround I used is to create a custom calendar with 24H working hours and assign it to this operator. After that you can do your on-line training anytime you want and your cases should be assigned to the operators which you expected. :) Have fun!
that explains why case was trying to cascade to Administrator. Your suggestion fixed it. But additionally, work was failing to cascade to Administrator because of the config error reported by HarishRAdama (HarishRAdama March 12, 2017 - 12:46am). So thank you both.
I ran into the same problem. Apperently this is a bug in the 7.2 version of Pega and is resolved in 7.2.1. However, 7.2.1. isn't deployed yet to the Academy environment. Hopefully the fix is deployed soon.
Since you have replied to a thread with a number of different issues can you please explain what exactly your issue is? What case are you working on? What issue are you facing? Any screen shots you can provide would be most helpful.