The service level agreement rule is identified in the default .pySLAName property, typically defined by a data transformation for the worker class. The default value is the default agreement for the service level. The Pega-ProCom agent detects unsuspected service levels – goals or deadlines not met – in a timely manner. If a service level agreement is not concluded before the limit, the system can automatically perform one or more actions, for example. B notifications, escalation of allocation, reallocation of the case, etc. Escalation actions are actions that your application performs at the service level based on a given agreement, to enable faster resolution times. You can configure escalation actions for service level agreements to notify the delegate, manager, and participants. to re-evaluate the task; or to resolve the case when goals or deadlines occur. Hello, Brahmesh, there will be no problem. Suppose you have configured the ALS for the river level so that the river ends by the 5th day, the river will be completed, which means that all assignments will end. For z.B. -what is going to happen, we use SLA`s at the case level and SLA at the stage level and assignments together of the SLA implementation functions at the step and flow level, much like SLA at the global and step level. So we`re going to go straight into the back-end execution of Flow SLA.
Step 3: In the Process tab of the river rule, add the agreement to the service level. Case, stage, flow, and assignment service levels work independently of one another. For example: Hello Prem, do we have a real-time scenario? If we have configured Flow Level Sla to be completed within 4 days and in the same flow, we will have the task to accomplish within 6 days. I do not think that if we have to finish the flow within 4 days, then why it is necessary to give an order with sla = 6 days. Please indicate a real-time scenario for the same. Thank you. You must design a service-level dataset to meet these escalation requirements and define a local action within folder range to allow users to apply the dataset at any point in the fall process. 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. To ensure that the rules managed by your application do not conflict with the service level agreement rule, select the Never use option on the Destination and Timeout tab in the Service Level Agreement (SLA) list. 1) Just try to have an empty destination event like (0,0,0,0) and set up your times in the deadline event at the destination location. 2) Try if this can be replaced by waiting. Since you only have one event to set up, we think the form of waiting would be sufficient. You can refer to our following article on the form of waiting. onestoppega.com/background-processing/wait-shape-its-configuration-usage-execution/ In my project, we have assignment and work SLAs, but depending on the customer objective, customer wants sla (SLA RESPONSE TIME) where we created this SLA organization? Please help us Use the target page Designer Studio > Process and Rules > Processes > SLAs to identify service level agreements in the current application and drill down to the rules they refer to. . .