Hello. I have been researching the various methods people use to implement SLAs in screen flows. None of these methods seem to fully leverage the OOTB SLA functionality, so I was wondering if there is an agreed upon, best practice for implementing SLAs in screen flows.
I have a process flow that includes 2 screen flow subprocesses. The client wants there to be separate SLAs for each subprocess, because different users will be completing each screen flow. This makes things difficult, as the urgencies must remain separate for each screen flow, yet update properly. Any thoughts?
Thanks for the reply. I have tried this method, but when I apply the SLA on the scree flow rule, it only calculates the time when the user is actually working on the work object, not when it is sitting idle in the worklist. And on top of that, it updates the entire work object urgency, not just the assignments within the screen flow.