NGB Platform v2.0: Document Actions + Work Center
NGB Platform v2.0 introduces two closely connected capabilities:
- Document Actions
- Work Center
The goal is simple: connect what can happen to a business document with the work users actually need to perform next.
Document Actions
Document operations are now exposed through a single backend-driven action model.
For every document, the backend determines:
- which actions the current user is allowed to see;
- whether an action is currently available;
- why an action may be disabled;
- how the action should be executed.
The frontend no longer needs to duplicate these rules.
Document Actions are also not limited to lifecycle operations such as:
- Post
- Unpost
- Repost
- Mark for Deletion
The same model can represent derivations, navigation actions, and view actions.
For example, a CRM Lead Intake can expose Create Lead Qualification as a normal Document Action.
Work Center
The second part of the release is the new Work Center.
Work Center brings together two different concepts:
- Tasks — business work that still requires action.
- Notifications — information that the user should know about.
They are intentionally separate models, but presented through one attention queue.
The badge in the application header is therefore not simply an unread notification count.
It represents:
open actionable tasks + unread notifications
A task remains actionable even after the user has opened or read it.
From Lead Intake to actionable work
The video uses a CRM flow to demonstrate how these two capabilities work together.
A Lead Intake is posted.
That business event creates a task for the Sales team:
Qualify Lead
The task is available in Work Center and is connected to its source document.
If the task is assigned to a role, an eligible user can claim it.
From Work Center, the user executes Create Lead Qualification.
This is not a special Work Center command. It is the same Document Action infrastructure used by the document itself.
The user completes the Lead Qualification and posts it with a Qualified result.
At that point, the original task is completed automatically.
The important part is that nobody manually checks a box saying that the task is finished.
The underlying business state determines that the work has actually been resolved.
And the next task appears:
Convert Lead
The process continues through the same model.
Tasks represent business state
This distinction is important.
Opening a task does not complete it.
Reading a task does not complete it.
Claiming a task does not complete it.
The task stays active until the business condition behind it is resolved.
That makes Work Center different from a traditional notification list.
It represents actionable business work, not just messages about things that happened.
Keeping the Platform generic
Work Center itself does not know what a Lead Intake, Lead Qualification, or Lead Conversion means.
The CRM vertical owns those business rules.
The Platform provides the reusable infrastructure:
- Document Action definitions and execution;
- permission and availability evaluation;
- user and role task assignment;
- claiming and snoozing;
- tasks and notifications;
- automatic task lifecycle based on business events;
- attention tracking;
- the compact Work Center drawer;
- the full Work Center page;
- in-app notification preferences.
This keeps vertical-specific business behavior outside the Platform while still giving every vertical the same infrastructure to build on.
NGB Platform v2.0
The main idea behind this release can be summarized in two lines:
Document Actions define what the user can do next.
Work Center shows what actually needs attention next.
Together, they connect document operations with actionable business work.
Watch demo:
Source code:
Top comments (0)