SLA agents to QP conversion
Hi,
We have an application with thousands of cases created each day. It was written in Pega 6 and now migrated to Pega 8 from Pega 7. We have many SLA's set for resuming flows, and then these SLA's are calling important Soap services during flow process. We are planing implementing Queue processors instead of each SLA's which are resuming flows. Although it is rare sometimes SLA's stop becuase of server issues, and queues are lost, we manually resumed all cases. We thought requeue option for QP's will be good in such cases.
Do you think it is a good idea for taking this risk for such busy application and convert SLAs to QPs? What can be disadvantage, risk for this conversion?
Accepted Solution
Updated: 14 Oct 2022 8:09 EDT
Lventur
IN
Recommended approach will be to use the OOTB functionality code. You might need to find the root-cause why SLA agent is getting stopped and to provide fix for that.
If you are using SLA, then you will be having below advantages
- You will be able to use all latest features which Pega introducing related to SLA after each upgrade without any code change needed.
- You can use Pega OOTB activity to update the SLA time if needed.
- Inbuild SLA process exception re-try logic will be avail in OOTB code.
Queue-Processor Disadvantages
- You need to build all logic from scratch.
- You will not be able to reset the SLA time once the request was queued.
- Already SLA agent is avail on top of that you are introducing new Queue-Processor, this will result in additional resource consumption