Question
Collab Consulting Services B.V.
NL
Last activity: 2 Jul 2024 12:28 EDT
Relevence of SLARefreshListEachIteration app setting in Pega Infinity23
The below link for pevious pega versions suggests change in settings for SLARefreshListEachIteration app settings when SLA Agent runs in more than 1 background nodes:
https://docs-previous.pega.com/system-administration/system-settings-pega-procom-sla-agent
With recent upgrade of the environment to Pega Infinity '23, the SLA Agent is run by "Queue Processor: ProcessSLA" using pyProcessSLA. What is the significance of below settings going forward?
1) SLARefreshListEachIteration
2) SLAUnitsToProcess
3) SLAUnitsToRetrieve
Collab Consulting Services B.V.
NL
@MarijeSchillern - Pls let me know if you could prioritize this query internally? Are there any other settings that needs to change along with these three?
Pegasystems Inc.
GB
@LukaszKarnasiewicz @richz @nairv1 is this a question one of you could help with?
Pegasystems Inc.
IN
@MarijeSchillern - I'm including @ArunSarada from Case Management for specifics related to SLA feature
Pegasystems Inc.
IN
@Priyan_RS , In Infinity 23, SLA processing continue to be processed by Agents, and the existing settings remain effective. The feature to process SLA events via queue processors is not generally available and is controlled by a toggle feature.
Collab Consulting Services B.V.
NL
@ArunSarada - We have set below DSS to "true":
- Pega-ProcessEngine • UseSLAQueueProcessor
I was wondering if we also need to "disable" Agent: ServiceLevelEvents in below rule form:
- Agents: Pega-ProCom
Since we were running "Agent: ServiceLevelEvents" on 2 background nodes, will the below Application Settings be of any significance? (overridden in Production Ruleset)
1) Pega-ProCom • SLARefreshListEachIteration = true
2) Pega-ProCom • SLAUnitsToRetrieve = 30
3) Pega-ProCom • SLAUnitsToProcess = 5
Thanks,
Priyan
Collab Consulting Services B.V.
NL
@nairv1 @ArunSarada - Please advise for the above context.