Leverage existing solutions vs build from scratch ServiceNow provides REST and SOAP web service API access its capabilities in the platform. These capabilities may be exposed to 3rd party applications for a micro-service approach, enabling rapid deve...
Circling back on this thread, in Paris we updated Flow Triggers with a configuration option, to run on extended tables. See docs link here, for more information
Please note, not triggering on extended tables is the same behavior of the legacy Workflow product. Triggering on extended tables is planned in a coming release, tenatively Paris, where user can set the Flow trigger configuration to run on extended t...
The only way to change it, is to make a copy. At time of copy (via ellipses menu on the top right), you'll be presented with an application scope picker to choose the scope of the copy.
There should be no discernible difference between global scope and private scoped execution. I've had our Quality Engineering team run through a battery of tests, and can confirm there is not difference. I suspect there is something else occurring (n...
If you configure your flow to run in the foreground, it will use the current thread vs dropping into the sysevent queue. See https://docs.servicenow.com/bundle/newyork-servicenow-platform/page/administer/flow-designer/reference/flow-triggers.html for...