Posted: 28 Jun 2016 11:21 EDT Last activity: 30 Jun 2016 20:21 EDT
SLA for screen flows
Hello. I have been researching the various methods people use to implement SLAs in screen flows. Most articles I find are a few years old and one 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?