Automation Pulse should answer questions that UiPath Orchestrator alone does not: which ideas are stuck, how long approval takes, where evidence is missing, which automations delivered value and which build assumptions repeatedly fail.
With an authorised UiPath connection, Automation Pulse can use selected Orchestrator data as context, but it should not duplicate Orchestrator's operational console. Jobs, processes, queues, machines, schedules and execution status remain Orchestrator concerns. Community availability and permissions vary, so the UI must show the source, last refresh and any unavailable metrics.
Automation Pulse is an additive view, not a replacement for UiPath’s operational console. It joins delivery context from AutoHub to the minimum runtime context needed to explain business progress.
#Data freshness
Every imported metric should show its source, scope and last refresh time. Missing permissions must be visible to the reader.
#Customer value
The view should connect operational results to the ideas and requirements that created them.