In my project, we use SLA to retry service calls. SLA is launched each time the service call fails. No urgency is mentioned and we do not think about it at all. We only use SLA to retry service calls. Mentioned the destination as 5 minutes, deadline as 20 minutes and Passed Dead Line as 1 for 10 intervals. Use the designer Studio target page > processes and rules > > SLAs processes to identify service level agreements in the current application and drill down to the rules that return them. The formula used to calculate the urgency takes into account the values of the work + phase + stage + level of allocation. For z.B. -what will happen, we will use Case Level and Stage and Assignment Level SLAs together Great article, thank you. During our implementation, we are dealing with a collection of about 25 types of cases with different SLA parameters.
Please explain. Service level agreements are part of the process category. A service level agreement is an instance of the obj-ServiceLevel service rule type. Each of the internal currents has its own unique quality. For example: OverallSLA is an internal flow that was created to process SLA at the case level. If we solve the case at some point, the system will deal with it with the ticket assigned in that river. The same goes for Stage Level, Step Level SLAs. With the service level feature (sometimes called SLAs) in Pega 7, you can use the most frequently used actions, such as notifications or advance feeds, without having to configure activities.
The service level form allows you to create a number of actions by simply adding them to a list without the need for any additional configuration. If I have defined SLA at the case level and there is another SLA at the second level, it is also defined. Excellent contribution😉 Thank you for providing such a good example. In addition, Pega 7 offers two flow actions that allow users to change a service level or replace an existing service level with a service level specifically designed for a particular situation. In the case designer, you can enable these case-level service-level flow actions so that users in the user portal dashboard can update service levels at any time during case processing. These flow actions can be configured at the Stage, Flow, or even assignment level. Each service level agreement supports time intervals that standardize how long you need to run a task or resolve a case. After first development and testing, selected service level agreements can be maintained by online business managers and not by application developers. . . .