How the wait shape will get activated on its own?
This was asked in an interview that for a wait shape if we consider a timer say of 5 minutes then how will it get invoked and the assignment will wait for 5 minutes?
Accepted Solution
Updated: 11 Apr 2024 7:07 EDT
Cognitonic Systems Australia
AU
@TanyaS58 Depending on the configuration of the Wait shape backend behavior varies:
Time Configuration: When the wait shape is configured with time, PEGA creates an entry in the OOTB work queue and writes an entry to System-Queue-ServiceLevel with a minimum date for processing attribute in PEGA. All the Wait shape entries are processed by ServiceLevelEvents Agent by PEGA. This agent checks the items waiting in the queue to process and processes the item once the minimum time for processing is reached.
Case Dependency: When the wait shape is configured with case dependency, using Dependency OOTB activity pega creates an entry in the work queue. For every case type that is associated as a dependent case, PEGA creates a pyCaseDependency declare trigger. This gets invoked when the criteria are met and the case is advanced resolving the work queue entry.
Regards,
Naga.
Updated: 29 Oct 2023 17:24 EDT
Cognizant
IN
@KotaC382 so basically for both the configurations the wait shape will be triggered by declarative rules? whether its an SLA or an OOTB activity? because say we have configured the wait shape with a timer of 2 minutes so pega will automatically create an entry in the OOTB work queue and writes an entry to System-Queue-ServiceLevel?
P.S. Attached screenshot of the timer configuration