skip to Main Content
0 811 69 64 45 (Lundi-Vendredi 9h-12h / 14h-18h - Prix d'un appel local)

Service Level Agreements In Pega

According to your statement, we have 2 types of ALS – assignment level, level of work ALS. Are ALS the same for work items and ALS at case level? What do you mean by standard intrusiveness, is this urgency always included in the calculation of the urgency of tasks? Why does Pega create these flows and why they come back? In my project, we have the assignment and the SLA work object, but according to the objective client demand there, customers want SLA level organization (RESPONSE TIME SLA) where we created this SLA organization? Please help us 1) Just try to have an empty goal event like (0.0,0,0,0) and set your schedules in the deadline event instead of Goal. 2) Try if this can be replaced by Wait. Since you only have one event to set up, we think the waiting form would be sufficient. You can read our following article on the form of waiting. onestoppega.com/background-processing/wait-shape-its-configuration-usage-execution/ Nice. I have a question to ask how service agentlevelevent select the queues that have been reached at their target time, and have processeevent deal with notifications dependent e.v.r. here. This will be really helpful if you can shed some light here. Tip: Use the case designer to set service level agreements for a case, phase and steps.

Open a rule of understanding at the service level that is in the class path of your request type by clicking on the protocol service level agreement and performing one of the following actions: Each internal stream has its own unique functionality. For ZB: CombinationSLA is an internal flow that was created to treat ALS at the fall level. If we resolve the case at any given time, the system will process it using the ticket assigned in that stream. The same goes for stage-level SLAs. Only one ALS rule can be set for each allocation, but also at the Flow, Step- and Stage level in your process and in the case as a whole. See the relationships presented below in the class diagram. Like the « Send an email » shape, the standard notification actions (pyNotifyAssigneeOnGoal/DeadlineTime and pyNotifyManagerOnGoal/DeadlineTime) are related to the participants (work parties) you listed in your case. However, you can write your own SLA actions in the form of activity rules. In addition to escalating the type of activity, you can also set one or more data transformations, call or advance another stream, or simply transfer them to another person`s work reserve or work basket lens.

Back To Top