Visual workflow builder
Change a business process in days, point and click
Your operation runs on more than work orders. The processes that surround them can now be designed by the people who own them, without writing code.
The challenge
Every process change is a new project
When the process does not fit the software, the business waits. Most of what keeps an operation running is not a field intervention, but the administrative closure of a contract that needs approvals from three different offices. A new connection request moving through technical review, commercial validation, and regulatory sign-off. A permit that has to be cleared before anyone touches an asset. A complaint that has to be tracked, escalated, and resolved.
Each of these is a real process, with its own steps, its own people, and its own rules. None of them is a work order.
For years, supporting a process like this meant building it. A specification, a budget, a development cycle, a release date and so on. The process itself, once built, existed only in code that a small number of people understood.
What that costs, quarter after quarter:
- A change to a business process becomes an IT project, with a lead time measured in release cycles rather than days
- Custom code has to be revalidated every time the platform is upgraded, so yesterday’s customization becomes tomorrow’s upgrade risk
- What is built for one process cannot be reused for the next, so the same investment is made again
- The operation adapts at the speed of the development backlog, not at the speed of regulator, the market, or the network
The consequence is quiet but expensive. When a regulator revises a protocol, when a new asset class enters the network, when an approval chain needs one more step, the business knows exactly what it needs. Getting it is the slow part.
The solution
One tool for every process to come
The Visual workflow builder lets a business process be designed, run, and changed without writing code. No development, no release cycle, nothing to maintain forward.
The reason this is now possible is a single change beneath the surface. The workflow engine was rebuilt so that it no longer depends on the type of process it is running. Once that dependency was removed, everything above it could be designed visually instead of built: the steps, the screens people work in, and the connections to other systems.
In practice, a process owner lays out the steps the process has to move through. Each step is assigned to a role rather than a named person. So the responsibility follows the organization rather than an individual. Where the process branches, a decision point sends it down the right path based on the data itself. Where an approval can be rejected, the process returns to the earlier step. The screen each person sees is designed, not developed, and works on both desktop and mobile. Where the process needs information from another system, it is connected without code. Then it goes live.
What makes it work:
- Steps, people, and rules you define yourself
A process change no longer starts with a specification and a development estimate - Responsibility assigned by the role and hierarchy
Not named individuals, so processes survive reorganization without rework - Branches, conditions, and paths back to earlier steps
Real approval chains are not linear and rejection is a normal outcome - Screens generated from the same design
On desktop and mobile, with no front-end development - Connections to OverIT NextGen FSM and to your other systems
Setup visually rather than through integration code - Every process aware of its own state
At any moment you know where it stands, who owns it, and what happens next, with a complete audit trail behind it
No starting over. No repeated criteria. Just continuous, intelligent exchange that gets more precise with every message.
What makes it work:
- Free-text input embedded directly in the Schedulable Activities panel, replacing the filters panel entirely
- Cross-references multiple variables including work order, type, status, address, and assets in a single natural language support
- Activity list updates immediately based on the semantic criteria expressed
- Full conversation memory across sequential queries: every refinement narrows the previous results, not the entire database
Purpose-built for the scale and complexity of linear asset industries
Electric utilities
A connection request for a distributed generation customer passes through technical, commercial, and regulatory approval, several of them at the same time. Any rejection returns it for revision. Each reviewer sees only their step, and the request carries its status from submission to energization without anyone chasing it.
Gas & water distribution utilities
Closing a complex contract requires approvals across several offices, with conditions that decide which path the closure takes. Where this once meant custom development, the steps, the approvers, and the rules are now designed directly, and the process can be adjusted when the policy changes.
Telecommunication
An access or right-of-way authorization has to complete before construction can begin, involving external parties and documents that arrive at different times. The process pulls the property record from the system that already holds it, so nothing is retyped and nothing is missed.
Transportation
Before work can start on a live network, safety approval, competency verification, and possession authorization all have to be in place. The process holds its own state, so no step can be skipped and the full authorization can be evidenced end to end.
Benefits
What changes for the business
Faster response to change
A revised regulation or a new business requirement becomes a design change, not a development project
Lower upgrade risk and lower cost of ownership
Removing custom code from these processes removes the work of revalidating it at every platform upgrade
Development capacity released
Process changes stop consuming a development backlog that is needed elsewhere
Reuse across the organization
A process designed once becomes a pattern the next team can start from, rather than a build that starts at zero
Accountability and auditability by default
Every step has an owner, every decision is recorded, and the full history of a process is available for internal governance and external scrutiny