Standard Agent runtime AccessGroup assignment
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
GB
Hello,
Thank you for your query. It has been passed to the appropriate members of our support team. Someone will contact you.
Regards,
Andrew Fontenelle
PDN Support Team
IP australia
AU
This may be not the best solution but when a standard agent runs it picks up the access group of the operator who put in into the queue. So before you do a queue for agent using the params change the operator page with the new access group. Revert the changes once its done.
Novitates
IN
Hi Palani,
There is an attribute in each queue entry "pyAccessGroup" which will be used to setup the Ruleset List for the thread execution. As the access group is dependent on the work object parameters, we can have a custom queue activity which creates a queue page and sets this property(pyaccessgroup) dynamically based on work object params instead of using a standard "Queue-For-Agent" method.
Thanks,
Krishna
Pegasystems Inc.
IN
Standard agents ignore Access Group configurations.
not sure, if this helps ...: https://community.pega.com/support/support-articles/changing-application-runs-incorrect-rules-async-processing
Maantic
IN
You can set the pyAccessGroup property with the desired access group name depending on your logic before queuing it. Check AddAssign activity of Assign- class for your reference where queuing is done for SLA processing.