VNCworkflow

VNCworkflow is the approval engine of the suite. Its central idea is that an approval process should be modelled once and then executed, not re-negotiated for every case. A template defines the route; every request created from it travels that route automatically.

A request carries text and attachments and moves through stations. Each station is a person or a role that acts: it reviews and forwards, or it decides. The outcome is approved or rejected, and every step is recorded in an unalterable trail.

The second design principle: the process owner models the route, not the platform team. Domain experts are granted author rights so that a department can change its own approval route without waiting for an IT ticket.

What it delivers

Consistent approvals. The same kind of request always reaches the right approvers in the right order — nobody has to remember the chain.
Route logic that matches reality. Stations can run in parallel, depend on other stations, or apply only under a condition over the request’s own fields.
Delegation and representation. Work continues when a responsible person is absent.
An immutable audit trail. Every status, comment, attachment and decision is recorded, which is what makes an approval defensible.
Self-service for departments. Authors model and maintain their own templates.

Main capabilities

Modelling a template

Capability	What it gives you
Stations	The ordered route; drag to reorder.
Station types	Review and Statement collect and forward; Approval and Release decide.
Responsibility	Bind a station to an organizational unit and role, or to a single person.
Task of the station	A precise instruction for the responsible person.
Conditions	Run a station only when a rule over the request’s form fields holds — all match (AND) or any matches (OR).
Parallel and dependent stations	A station can wait for another station instead of running in sequence.
Form fields	The facts asked at submission; they are what conditions read.
Authors	Grant template-modelling rights to domain experts without admin rights.

Running a request

Capability	What it gives you
Create from a template	A guided wizard turns a template into a submitted request.
Request ID	A stable identifier such as `V-2026-021`.
My tasks	The stations currently waiting for you.
Requests list	Every request with its current station and state, with filters and search.
States	Draft, running, approved, rejected and completed.
Comments and attachments	Notes and documents travel with the request.
Per-request permissions	Decide who can see and act on a request, and add someone explicitly.
Timeline	A person’s cross-suite activity for context.
Assistant	Ask the assistant about VNCworkflow or about a specific request, under the organization’s AI policy.

Typical use

Staff request. A hiring manager starts a request from the Staff request template; the unit lead reviews, controlling is engaged only when the request is for a positive headcount, and the final approval closes it.
Software introduction. A new tool passes a review, a security statement and a final approval, with the vendor’s documents attached.
Investment or spend approval. A conditional station adds a finance step only above a threshold defined in the form fields.
Absence. During a holiday, the delegation keeps a station actionable instead of blocking the process.

How it fits the suite

VNCdirectory provides organizational units, roles and access.
VNCtask and VNCproject can start a request from a task; approvals can be attached to project work.
VNCfiles holds the attachments.
VNCmail and VNCchat announce and discuss a request.
VNClagoon AI provides the assistant and the timeline briefs.
VNCfluid shows My tasks as a portlet.

Roles

Role	What they do
Requester	Start a request from a template and track it.
Approver	Act at a station: review, state, approve or release.
Author	Model and maintain templates for a domain.
Administrator	Grant author rights, set access and supervise the trail.