pyProcessSLA Queue Processor Disabled in 8.6
In 8.6, the pyProcessSLA Queue Processor is disabled by default, while the ServiceLevelEvents Agent is still running.
However, it sounds like the general recommendation is to use job scheduler and queue processor rules instead of agents in many of the Community posts – e.g.: https://community.pega.com/knowledgebase/articles/system-administration/86/using-job-schedulers-and-queue-processors-instead-agents
Is the recommendation to manually enable the pyProcessSLA Queue Processor in 8.6 and disable the Agent, or will pyProcessSLA be enabled by default in future versions of the platform, once it's ready for production?
Thanks!
Accepted Solution
Pegasystems Inc.
GB
@morak pyProcessSLA will be disabled. pyProcessSLA is just present in the product as a place holder and disabled by default and not suggested to be enabled. This QP is again removed in Pega 8.7 versions to avoid confusion.
For better scalability, ease of use, and faster background processing, use job scheduler and queue processor rules instead of agents in scenarios that previously required agents, such as service-level agreements, sending daily emails, or queuing items.
The agents in the Pega-ProCom ruleset process email, service-level agreements, and assignments. The agents in this rule provide the following types of processing:
- Processing service-level agreements and escalation ( ServiceLevelEvents )
- Applying a flow action to assignments in bulk ( AgentBulkProcessing )
- Sending out email correspondence ( SendCorr )
- Checks whether starting flows references have been updated ( GenerateStartingFlows )
- Checking incoming email (deprecated) ( Email_CheckIncoming )
Please see the following for the most up-to-date documentation:
Background processes included with Pega Platform
@morak pyProcessSLA will be disabled. pyProcessSLA is just present in the product as a place holder and disabled by default and not suggested to be enabled. This QP is again removed in Pega 8.7 versions to avoid confusion.
For better scalability, ease of use, and faster background processing, use job scheduler and queue processor rules instead of agents in scenarios that previously required agents, such as service-level agreements, sending daily emails, or queuing items.
The agents in the Pega-ProCom ruleset process email, service-level agreements, and assignments. The agents in this rule provide the following types of processing:
- Processing service-level agreements and escalation ( ServiceLevelEvents )
- Applying a flow action to assignments in bulk ( AgentBulkProcessing )
- Sending out email correspondence ( SendCorr )
- Checks whether starting flows references have been updated ( GenerateStartingFlows )
- Checking incoming email (deprecated) ( Email_CheckIncoming )
Please see the following for the most up-to-date documentation:
Background processes included with Pega Platform
Background processing best practices
Using job schedulers and queue processors instead of agents
Accepted Solution
Pegasystems Inc.
GB
@morak pyProcessSLA will be disabled. pyProcessSLA is just present in the product as a place holder and disabled by default and not suggested to be enabled. This QP is again removed in Pega 8.7 versions to avoid confusion.
For better scalability, ease of use, and faster background processing, use job scheduler and queue processor rules instead of agents in scenarios that previously required agents, such as service-level agreements, sending daily emails, or queuing items.
The agents in the Pega-ProCom ruleset process email, service-level agreements, and assignments. The agents in this rule provide the following types of processing:
- Processing service-level agreements and escalation ( ServiceLevelEvents )
- Applying a flow action to assignments in bulk ( AgentBulkProcessing )
- Sending out email correspondence ( SendCorr )
- Checks whether starting flows references have been updated ( GenerateStartingFlows )
- Checking incoming email (deprecated) ( Email_CheckIncoming )
Please see the following for the most up-to-date documentation:
Background processes included with Pega Platform
@morak pyProcessSLA will be disabled. pyProcessSLA is just present in the product as a place holder and disabled by default and not suggested to be enabled. This QP is again removed in Pega 8.7 versions to avoid confusion.
For better scalability, ease of use, and faster background processing, use job scheduler and queue processor rules instead of agents in scenarios that previously required agents, such as service-level agreements, sending daily emails, or queuing items.
The agents in the Pega-ProCom ruleset process email, service-level agreements, and assignments. The agents in this rule provide the following types of processing:
- Processing service-level agreements and escalation ( ServiceLevelEvents )
- Applying a flow action to assignments in bulk ( AgentBulkProcessing )
- Sending out email correspondence ( SendCorr )
- Checks whether starting flows references have been updated ( GenerateStartingFlows )
- Checking incoming email (deprecated) ( Email_CheckIncoming )
Please see the following for the most up-to-date documentation:
Background processes included with Pega Platform
Background processing best practices
Using job schedulers and queue processors instead of agents