Most of us spend a lot of time reviewing reports, identifying what is going on, then taking some (often very predictable) action.
Why? Why spend time looking at data of what happened and pressing the same buttons over and over? The report may be incredibly pretty, but why spend our time looking at it if we already know what to do about it.
Is your job to look at stuff or to do stuff? I want to spend my time getting stuff done.
With ServiceNow, we can use Performance Analytics to drive more efficient, faster, and better outcomes while the work is being done.
Overview
In our Performance Analytics and Reporting Office Hours session on November 4, we looked at integrating the analytics into workflows to make them smarter and more robust.
We discussed Flow Designer Actions and what an Analytics Spoke could look like.
Then we discussed how you could use these actions in Flow Designers Flows and Subflows. Here is a simple example (which you probably wouldn’t use in real life) that executes after a Data Collector completes and then fires a different Data Collector. In more common cases, you might run some other (non-Data Collector) after a specific Data Collector completes or run a Data Collector as part of a different flow.
Presentation
Here is the recording if you missed it:
Useful Links
| Flow Designer | Now Learning: Flow Designer Fundamentals |
| Developer: Flow Designer | |
| Docs: Flow Designer | |
| Script Actions | Docs: Script Actions |
| Performance Analytics API | Docs: Performance Analytics JavaScript API |
The presentation is attached for your reference. See you at a future Performance Analytics and Reporting Office Hours session. We run the sessions every other Wednesday at 9 am Pacific, Noon Eastern, 6 pm Central European time.
