LSA 23 Course - Designing background processing challenge question on evaluation option with sla.
In challenge: https://academy.pega.com/challenge/designing-background-processing/v5/in/62316/69216 At the evaluation of the option using SLA it states as con:
- Keeping the case unresolved just for the sake of email notifications will create a process hindrance with too many assignments and an unresolved case.
What process hindrance do you foresee? I suspect it may be performance on reporting and processing becouse of the number of assignments in the table? Or maybe it clutters overview of generic work status reports including the open cases for long period of time, basically as long as a subscription is active the case is open. Are there reasons i overlooked? Thanks in advance!
Accepted Solution
Updated: 30 Dec 2024 3:34 EST
HCA Healthcare
US
@Niels_U By keeping cases unresolved just for sending email notifications can cause several issues. It can clutter worklists and dashboards, making it harder to track actual work. It can also affect system performance, as long-running cases increase the load on database tables and SLA processing. This approach can skew reports, inflate unresolved case metrics, and complicate data cleanup or archival. Additionally, it creates risks for compliance audits if open cases are misinterpreted as pending work. A better solution is to resolve the case and manage email notifications separately, such as using a dedicated notification system, child cases, or event-driven processing like Pega's Pub-Sub model to handle subscription-based notifications efficiently
Personly
NL
@RameshSangili Thanks for your reply.
Accepted Solution
Updated: 30 Dec 2024 3:34 EST
HCA Healthcare
US
@Niels_U By keeping cases unresolved just for sending email notifications can cause several issues. It can clutter worklists and dashboards, making it harder to track actual work. It can also affect system performance, as long-running cases increase the load on database tables and SLA processing. This approach can skew reports, inflate unresolved case metrics, and complicate data cleanup or archival. Additionally, it creates risks for compliance audits if open cases are misinterpreted as pending work. A better solution is to resolve the case and manage email notifications separately, such as using a dedicated notification system, child cases, or event-driven processing like Pega's Pub-Sub model to handle subscription-based notifications efficiently
Personly
NL
@Sairohith Thanks for your reply.