ID907 - Workflows Explorer gives you a complete, readable picture of how your e-automate Workflows are set up: every workflow, the trigger events that start it, and the actions each trigger fires - with e-automate's internal ID codes translated into the names you actually recognize.
Jump to a specific section by clicking a link
Overview | Samples | Variables | Alert Functionality | Power BI Reporting | Related Alerts | Webinar
Click to Subscribe and Download Template
Overview
Overview
e-automate Workflows let you automate work inside e-automate. When a trigger event occurs - for example a sales order reaches a certain status, or a service call is created - the workflow runs one or more actions such as creating a call, changing an order or PO status, placing or releasing a hold, adding a note, or notifying staff. This automation is powerful, but it lives deep in e-automate's setup screens, spread across triggers, steps and event actions, and everything is stored as internal ID numbers. Once you have more than a couple of workflows it becomes very hard to see what is actually configured - or to explain why e-automate did something.
ID907 - Workflows Explorer reads your workflow configuration directly from e-automate and presents it in an interactive Power BI report. It lists every workflow and lets you drill into each trigger and the actions it fires. For each action it shows the full target detail (target table, status changes, call type, bill code, hold codes, note type, branches, item, SH attribute); for each trigger it shows the full firing conditions (proc, order types, SO / detail / PO statuses, call types, item, branches) - all with the raw ID codes resolved to friendly descriptions. Selecting an action highlights the triggers that call it, and selecting a trigger highlights the actions it fires, so you can trace your automation in either direction.
In short: pick a workflow from the Select a workflow drop-down, browse its triggers and actions in the header lists, click either side to cross-filter, read the full detail in the Action Details / Trigger Details cards, and narrow the picture with the Event/Action and Event/Trigger filters on the right. An (i) info button beside the selector opens an on-page reading guide (see Power BI Reporting below).
Run Schedule: On Demand
Type of Output: On Demand Power BI Report
* * *
Sample
Sample
The Workflows Explorer page. Choose a workflow from the Select a workflow drop-down at the top; the (i) button beside it opens an on-page reading guide. The four cards on the left and centre show the actions and triggers for the chosen workflow; scroll right for the filter panels.
Left: Action Headers (each action + a ⚡ count of the triggers that call it) and Action Details (full target detail of the selected action). Centre: Trigger Header (each trigger + a ▶ count of the actions it fires) and Trigger Details, with a Condensed / Extended toggle. Right: the start of the Event / Action Filters.
Scrolled right: the rest of the Event / Action Filters (target side, teal) plus the Notify flags, and the Event / Trigger Filters (trigger side, red).
* * *
Variables
Variables
This is an on-demand Power BI report, so there are no subscription variables to set up front. Instead you explore and filter the data inside the report using the slicers on the right of the Workflows Explorer page (scroll right to reach them all). Leaving a slicer on All includes everything; selecting a value narrows the header lists and the detail cards to matching workflows. The filters are grouped into two sets.
Event / Action Filters (teal - the action / target side of each step)
- Action Proc Name - the stored procedure that performs the action.
- Action Proc Description - plain-language description of the action.
- Target Action - the resolved action name (e.g. Create service call).
- Note Type - the note type an action adds.
- Target Bill Code / Target Call Type - the bill code / call type an action sets.
- Target Item - the inventory item an action references.
- Target Branch Names - the branch(es) an action applies to.
- Target Table - the e-automate table the action writes to.
- Target SH Attribute - the service-history attribute an action sets.
- Target From / To SO Status - the sales-order status change an action makes.
- Target From / To PO Status - the purchase-order status change an action makes.
- Target From / To On-Hold Code - the hold code an action places or releases.
- Notify Creator / Rep / Rep Mgr / Tech / Tech Mgr - whether the action notifies each party.
Event / Trigger Filters (red - the trigger / condition side that starts a step)
- Trig Proc Name - the stored procedure that detects the trigger event.
- SO Order Status / SO Detail Status - the sales-order statuses that fire the trigger.
- PO OrderType / PO Status / PO DetailStatus - the purchase-order conditions that fire the trigger.
- Order Type - the sales-order type(s) that fire the trigger.
- Branch Name - the branch(es) the trigger is limited to.
- Item - the inventory item the trigger is limited to.
- Call Type Description - the service-call type(s) that fire the trigger.
* * *
Alert Functionality
Alert Functionality
-See here for getting Power BI in place.
-Click here to download the file
For ECi Hosted clients: We are working with ECi to open up our access so we can set an ODBC connection for you. If you are interested, then please provide us the public static IP address for your company network so that ECi can whitelist it to allow us access.
* * *
Power BI Reporting
Power BI Reporting
The report opens on the Workflows Explorer page. Pick a workflow from the Select a workflow drop-down at the top (or leave it on All to see everything). The revision shown in the title (e.g. rev. 2026.09.30) tells you when the configuration was last captured. An (i) info button beside the selector opens an on-page copy of the guidance below.
How best to read the page
1. Pick a workflow. Use the Select a workflow drop-down at the top (or leave it on All). Everything below reacts to it.
2. Scan the two header lists. Left = the actions in scope; centre = the triggers in scope. Read the pills to spot the important ones (see “What the header pills mean” below). Each trigger card also shows its “Scan for…” comment, so you can read what fires it without clicking.
3. Pick a direction and click to trace. The two panels cross-filter each other. Trigger-first (“what does this trigger do?”): click a trigger and the Action list collapses to just the actions it fires. Action-first (“what fires this action?”): click an action and the Trigger list collapses to just the triggers that call it. Click again to clear.
4. Read the detail cards. Action Details (bottom-left) shows the fully resolved event action - action text, comment, target table, SO/PO status changes, call type, bill code, hold codes, note type and branches. Trigger Details (bottom-centre) shows the firing conditions; flip Condensed → Extended when you need the full lists of order types, statuses and branches instead of the truncated summary.
5. Narrow with the filters. Scroll right for the Event/Action (teal) and Event/Trigger (red) filter panels (see Variables). They narrow both the header lists and the detail cards, so you can answer questions like “which triggers fire for a given branch or call type?” or “which actions set a particular hold code?”
A good mental model: triggers are the “when,” actions are the “what.” Start from whichever you know, use the pill to see how far it reaches, click to trace the connection, then read the detail card for the specifics.
What the header pills mean
Both pills are relationship counters - they show the fan-out of the trigger↔action relationship, and the icon tells you which direction is being counted:
- Action Headers - the ⚡ (bolt) pill = how many triggers call this action. A high number flags a shared, central action that many triggers depend on.
- Trigger Header - the ▶ (play) pill = how many actions this trigger fires. A high number flags a trigger that does a lot.
The number is a preview of what will light up when you click - an action showing ⚡ 17 will surface 17 triggers when selected.
The same guidance is built into the report - click the (i) button next to the workflow selector to open it on-page.
* * *
Related Alerts
Related Alerts
ID815 - Automated Equipment Order Workflow Process "If This Then That (IFTTT)"
See full list of all Power BI reports that we currently have available
https://support.ceojuice.com/hc/en-us/sections/360011259132-Power-BI-Reports
* * *
Webinar
Webinar
**COMING SOON**
0 Comments