The Automations Platform Shift
The single biggest leap in MinuteView's history
For years, MinuteView was a stable and capable platform - but underneath, it was configuration-heavy and script-heavy. Version 2.0 changed the foundation entirely, moving every part of the product onto a single, modern Automations engine and turning automation into something any user can build.
Automations - A New Foundation for the Whole Platform
The centrepiece of 2.0 was Automations: a workflow-style automation builder that replaced the legacy Creator environment and became the engine every other module runs on.
From Creator to Automations
Platform ShiftCreator was a configuration-heavy, script-heavy environment - non-intuitive to work with and restrictive in what could actually be built. Automations replaces it with a workflow-style, drag-and-drop node builder.
- Compose custom automation visually by connecting nodes - no scripting required
- Build practically anything, from simple tasks to complex multi-step processes
- An intuitive experience that puts automation in the hands of the user, not just the configurator
- A single, consistent way to define automation across the entire platform
Automation moved from a specialist, configuration-heavy discipline to something any user can build for themselves.
Everything Runs on Automations
Unified Engine2.0 was not about new features - it was a new foundation. Every piece of functionality was moved onto the Automations engine.
- Search (agentic RAG) now processes through Automations
- The Configurator backend now executes through Automations rather than standalone PowerShell scripts
- The viewer backend runs on Automations, alongside its own 2.0 refinements
- A single execution engine underpinning the whole platform, replacing scattered scripts and config-heavy setup
The underlying architecture shifted from a configuration-heavy, script-heavy platform to a simple, unified, easy-to-use one.
Built for Scale and Reliability
Moving onto the Automations engine unlocked a fundamentally more efficient and resilient way of running work across the platform.
Parallel Processing
The legacy model ran serialized automation queues - one server processing one task at a time, which was highly inefficient.
- Process dozens of tasks in parallel on a single server
- Dramatically higher throughput without additional infrastructure
- Far better use of available server resources
Automation throughput scaled from one-task-at-a-time to dozens of concurrent tasks per server.
Background-Service Architecture
The Automations engine now runs as a service in the background of the server, removing the need for constantly-open user sessions.
- No user sessions that have to stay open for automation to run
- Reliable, always-on execution independent of any logged-in user
- A cleaner operational model for deployment and maintenance
Automation became a resilient background service rather than something tied to an open session.
Summary
MinuteView 2.0 was a foundational release - a complete shift in how the platform is built and run:
2.0 set the foundation that every release since has built upon - starting with the architectural leap in 2.1.