Workflow in the other apps
A VNCworkflow request is often about something — a document, a task, a channel topic. Instead of switching to VNCworkflow and re-typing it, you Start workflow from where the item lives, and the request is linked back to it.
From each app
Section titled “From each app”| App | Where | What it becomes |
|---|---|---|
| VNCfiles | A file → Start workflow (below the preview) | A request linked to that file. |
| VNCtask+ | A task’s Workflow chip (on its row) | A request linked to that task. |
| VNCchannels+ | A topic → Start workflow in the header (Actions) | A request linked to that topic. |
Each opens the same create wizard — type, text & attachments, station route, summary — so the approval rules are the same wherever you start.
What comes back
Section titled “What comes back”The source item then carries a Workflow chip showing the request’s Kennung and current state (submitted, forwarded, approved, rejected, commented). Select it to open the request in VNCworkflow.
If a request is already running for the item, you are asked “A workflow is already running for this topic/file/task (…). Open it instead?” — select Open rather than starting a second one.
One system of record
Section titled “One system of record”Whatever the starting point, the request lives in VNCworkflow: the stations, the decisions, the history and the Audit trail PDF are all there. The other apps only hold the link and the status chip.
→ Start a workflow from any item · How approvals route