Question
Virtusa Corporation
US
Last activity: 29 Sep 2019 14:45 EDT
Queue Management in Standard Mode
In this link https://community.pega.com/knowledgebase/articles/how-agent-queues-work
It is mentioned for Advanced mode, we need to explicitly enable AQM check box. and for Standard mode, medntioned as " In Standard mode, the agent queue is engaged automatically ". So does that mean we no need to select AQM checkbox for Standard mode..?
For Standard or Advanced mode agent,
1) We first queue to agent using Queue-For-Agent method in an activity.
2) If standard mode, I need to have business logic with Obj-save alone as system going to do commit and rollback and if Advanced mode, I need to have business logic and Obj-save, commit and rollback steps explicitly mentioned in the agent activity.
Could any one please clarify my query and confirm whether my understanding about queueing mentioned above in steps is correct?
Accepted Solution
Barclays
IN
Standard Agent
1) Your point "We first queue to agent using Queue-For-Agent method in an activity." is correct.
2) System to provide object locking and other transactional support.
3) Need to check AQM if you want agent to opt AQM feature.
Advance Agent:
1) We can make queue bases processing for advanced agent.
2) we need to take care of bject locking and other transactional support (Commit).
3) If Queue based we can use AQM
Personly
NL
Hi,
In my experience with version 7.3.1 you need to check AQM checkbox and in the agent activity you should explicilty handle the obj-save and commit where needed .
I used standard agents to do straight through processing, in my experience when i did not commit myself at the end of the activity, pega would perform a rollback after transaction timeout.
My solution uses a flowaction in a flow that gets perfomed by the agent activity so that the rest of the processes runs until a next assignment step is reached or de flow/case is completed.
In case of an unhandled exception pega wil rollback and put the queue item in broken queue.
This article might give you more insight:
https://community.pega.com/knowledgebase/articles/how-agent-queues-work
Good luck and have fun :)
Virtusa Corporation
US
Thanks. But what is given as per definition is, for standard agents we no need to define transaction steps and only business logic steps to be given.
Accepted Solution
Barclays
IN
Standard Agent
1) Your point "We first queue to agent using Queue-For-Agent method in an activity." is correct.
2) System to provide object locking and other transactional support.
3) Need to check AQM if you want agent to opt AQM feature.
Advance Agent:
1) We can make queue bases processing for advanced agent.
2) we need to take care of bject locking and other transactional support (Commit).
3) If Queue based we can use AQM