Advance agents Vs Standard Agents
Hello Guys,
I have a scenario, where I have a table and based on the status of every row, I need to trigger a case. Which agent is the best suited in this scenario?
Thanks,
Niharika
Accepted Solution
Coforge DPA
IN
Hi @Niharika,
Like @NileshKumarSaha, you can go for either way to create a case from status of entries in table.
Those were true solutions but to understand how to decide on which 1 to choose...Lemme give you a pointer.
- When you need an action to be done in the context of a case, go for standard agent as its transaction friendly.
- When you need some action to be done on a schedule basis, choose advanced agents.
So in your scenario, it looks like a typical bulk processing. I am assuming the staging table you are using gets updated based on some bulk processing of file, or manual entries. And you are supposed to create cases based on the flag in the table.
So the concept works running the agent to run once a day or hourly basis based on the requirement.
So i would suggest using advanced agent for your scenario. Again you can queue it to standard agent from within the advanced agent activity for load balancing, like NileshKumarSaha suggested that point.
Hope i explained clear.
Aaseya
IN
Hi Niharika ,
If the table is mapped to a class in pega and you are holding the status of the row in a property ,then
a) Create a declare trigger on the class and put a watch on the property value which is holding the status
b) Create trigger activity , to queue the particular record for a standard agent to pick.
c) Create a Standard agent to create a case
Otherwise , If this is a schedule job that has to be performed on daily basis ,
a) Create advance agent to browse the data from the table, loop through the records, if the record satisfy your conditions of status then queue that item for a standard activity .
b) Create a Standard agent to create a case
Thanks,
Nilesh
Accepted Solution
Coforge DPA
IN
Hi @Niharika,
Like @NileshKumarSaha, you can go for either way to create a case from status of entries in table.
Those were true solutions but to understand how to decide on which 1 to choose...Lemme give you a pointer.
- When you need an action to be done in the context of a case, go for standard agent as its transaction friendly.
- When you need some action to be done on a schedule basis, choose advanced agents.
So in your scenario, it looks like a typical bulk processing. I am assuming the staging table you are using gets updated based on some bulk processing of file, or manual entries. And you are supposed to create cases based on the flag in the table.
So the concept works running the agent to run once a day or hourly basis based on the requirement.
So i would suggest using advanced agent for your scenario. Again you can queue it to standard agent from within the advanced agent activity for load balancing, like NileshKumarSaha suggested that point.
Hope i explained clear.
Rabobank
NL
Thank you so much Guys for taking time out and answering my question.
Even I had this idea to use Advance agent because its just a row in the table. and I don't need AQM in this scenario, as if something failed, and the row status is not changed to "Processed", it will be picked up by another agent again.
Thank you again.
Thanks,
Niharika
STG Inc
US
Hello,
If you are implementing in Pega Infinity versions, use job scheduler as it is more efficient and faster background processing than agents and Pega recommends to do so. You may refer below. Cheers.