Using Flow Designer flows for SLAs?

Zoltan Tougas
Mega Explorer

I am setting up SLAs for Incident for the first time, and was wondering if SLA Workflows are limited to not be attached to Flow Designer flows? If not, how does one enable and SLA to be attached to a Flow instead of a Workflow? Should I not be concerned about this and only use Workflows?

1 ACCEPTED SOLUTION

SatheeshKumar
Kilo Sage

yes you cannot use flows for SLA because it will be executed async!

 

Check the below statement from servicenow!

Flow Designer vs. Workflow

If you are creating something new, always begin with Flow Designer.  However there are a few circumstances when you should still use Workflow.

  •  Instance is running on an earlier release than Kingston.
  •  If the process requires very complex/scripted flow logic, it can be written in Workflow and called from a flow.
  •  Changing logic already developed using Workflow.
  •  Steps required do not exist yet in Flow Designer and require unsupported protocols.
  •  SLA Timer required.

     

     

     

View solution in original post

2 REPLIES 2

SatheeshKumar
Kilo Sage

yes you cannot use flows for SLA because it will be executed async!

 

Check the below statement from servicenow!

Flow Designer vs. Workflow

If you are creating something new, always begin with Flow Designer.  However there are a few circumstances when you should still use Workflow.

  •  Instance is running on an earlier release than Kingston.
  •  If the process requires very complex/scripted flow logic, it can be written in Workflow and called from a flow.
  •  Changing logic already developed using Workflow.
  •  Steps required do not exist yet in Flow Designer and require unsupported protocols.
  •  SLA Timer required.

     

     

     

Thanks for the answer. For some reason I was under the impression that Flow Designer is the way things are moving towards and that eventually workflow will be decommissioned. Didn't realize there are some things you cannot do in Flow.