Without the platform
Information about Workflow & Document Management lives in separate spreadsheets, and nobody knows which version is current.
With Partiu Formatura
9 modules share the same class, graduate and event records.
Platform and intelligence · Workflow & Document Management
All company processes designed, approved and audited using the same engine
Partiu Fluxo is the corporate process engine: you draw the flow in a diagram, assemble the form that will be filled out, define who approves and in how long, and the system takes the request from start to finish. Purchase, expense, HR request, freelancer redemption and any new process now have the same inbox, the same deadline, the same track and the same indicators, without writing code for each case. Along comes the corporate GED, with versioned document, check-out and approved publication.
The problem and the solution
What changes when Workflow & Document Management works inside the platform
This is connected information about classes, graduates and events across 9 modules, replacing scattered spreadsheets and messages.
Without the platform
A request for a number takes time because someone has to combine data from several places.
With Partiu Formatura
Task and Request Center and Visual Process Designer update together, with figures ready for the next meeting.
Without the platform
The process depends on who is working that day, and its history disappears.
With Partiu Formatura
Everyone follows the same workflow, with recorded actions and role-based permissions.
Without the platform
Connecting with other departments means exporting spreadsheets and entering data again.
With Partiu Formatura
Workflow & Document Management shares information directly with other areas of the platform.
How it works
How information moves through Workflow & Document Management
Each step is a real module in this area. Its output moves to the next step without anyone entering the same information again.
What is available in Workflow & Document Management
- Task and Request CenterA single inbox for everything awaiting your decision.6
- Visual Process DesignerThe flow designed on the screen, published in version and executed as is.6
- Sheets and FormsThe form of each process assembled by dragging, without programming.6
- Scopes, Deadlines and SchedulingWho approves, how much they approve and what happens when the deadline passes.6
- Corporate GEDCompany document with folder, version, check-out and approved publication.7
- Track, Audit and PermitsEach decision recorded with author, date and what changed.6
- Indicators and SLAWhere the process gets stuck, who is overwhelmed and how much time each step takes.6
- Integrations and TriggersThe outside system opens the request, and the workflow notifies the outside system.6
- Coexistence with Existing FlowsThe old process keeps running while the new engine proves itself right.6
Featured
The old process keeps running while the new one proves itself right
Each flow that already existed (expense, purchase requisition, HR request, freelancer rescue) gains a bridge with three modes. Turned off, the behavior is as usual. In shadow, the engine tracks in parallel and the convergence between the two decisions is measured. Activates, the engine decides and writes the outcome back to the source register. Nothing is deleted and the business table remains the source of the record.
See this in action- Version of the drawing frozen by request, republishing does not break what is in progress
- Deadline in business hours with holiday per branch, reminder before expiry and scheduling by authority
- Document controlled with checkout, versioning and flow-approved publishing
- Trigger via API opens request from outside, and webhook notifies the external system of the outcome
Task and Request Center
A single inbox for everything awaiting your decision.
- Inbox with pending tabs, available to take on, delegated and completed
- Pool task that anyone in the group takes on, and releases if they don't touch it
- Bulk approval: multiple requests decided at once
- Delegation by period, for vacations and absences, with a record of who decided for whom
- Return the request one step back when the process design allows
- My requests: tracking what you opened yourself, with the current stage
Visual Process Designer
The flow designed on the screen, published in version and executed as is.
- Canvas with step dragging, curve connections, zoom and pan
- Human task, approval, service, notification, timer, and subprocess steps
- Detours by condition, parallel paths and junction that only releases when all branches arrive
- Validation before publishing: orphan step, dead-end deviation and unreachable end
- Frozen published version: request in progress never changes design midway
- Simulation of the process without recording anything, to test the design before releasing
Sheets and Forms
The form of each process assembled by dragging, without programming.
- Card builder with text, number, currency, date, selection, file and line grid fields
- Domain fields that consult the system itself: class, graduate, cost center, branch, supplier and product
- Conditional field that only appears when another field has a certain value
- Control who edits what: each step only releases the fields that fit it
- Validation on the server, with mandatory mask and rule per field
- Form reused between processes and versioned along with the design
Scopes, Deadlines and Scheduling
Who approves, how much they approve and what happens when the deadline passes.
- Height by value range, with next level triggered automatically
- Quorum for approval: all, majority, anyone or defined quantity
- Assignment by user, role, department, requestor manager, cost center or branch manager
- Deadline in busy or working hours, with calendar and holidays per branch
- Reminders before due date and escalation with reason recorded in track
- Delay panel with what has already expired and who is stuck
Corporate GED
Company document with folder, version, check-out and approved publication.
- Folders with own permission and search by name, tag and content
- Versioning with history: each new version preserves the previous one
- Checkout with exclusive lock, so no two people can edit the same file
- Publication that goes through an approval flow before becoming valid as an official document
- Validity with periodic review: expired document generates review task
- Reading science: whoever needs to read the procedure confirms it, and it is recorded
- Request attachment that points to the controlled document, instead of becoming a loose copy
Track, Audit and Permits
Each decision recorded with author, date and what changed.
- Immutable track of movements, without editing or deleting, with before and after data
- Comments on the request mentioning colleagues, mirrored in Partiu Teams
- Attachments served by authenticated endpoint, revalidating the link with each access
- Permissions per action: view, start, execute task, manage, draw, configure authority and view indicators
- Scope per branch in every consultation, respecting the multi-unit structure
- Those who have no connection with the request do not even see that it exists
Indicators and SLA
Where the process gets stuck, who is overwhelmed and how much time each step takes.
- Summary with in progress, delayed and completed in the period
- Openings and completions per day, to see the queue growing or draining
- Bottlenecks per stage: average time stopped at each point in the flow
- Deadline compliance by process and by approver
- Load per person, with the volume of open tasks for each person
- Indicators calculated from the track itself, without parallel typing
Integrations and Triggers
The outside system opens the request, and the workflow notifies the outside system.
- Input trigger with own key: an external system opens the request via API
- From-to fields, to translate the received payload to the process file
- Key saved only as a hash and limit of calls per minute
- Event-subscribed webhooks: request started, completed, canceled, task created, completed, and delayed
- Service step that calls endpoints from an authorized list, with retries and time limits
- Documented API, with the same engine serving the panel, app and third-party systems
Coexistence with Existing Flows
The old process keeps running while the new engine proves itself right.
- Bridge with three modes per flow: off, in shadow and active
- Shadow mode: the engine tracks in parallel and the convergence between the two is measured
- Active mode: the engine decides and writes the outcome back to the source register
- Expense, purchase requisition, HR request and freelancer redemption already connected
- Request linked to the originating record, opening on both sides
- Nothing is deleted: the business table remains the source of the record
Checklist
Everything included in Workflow & Document Management
All 55 features in this area, grouped by module so you can compare systems item by item.
- Inbox with pending tabs, available to take on, delegated and completed
- Pool task that anyone in the group takes on, and releases if they don't touch it
- Bulk approval: multiple requests decided at once
- Delegation by period, for vacations and absences, with a record of who decided for whom
- Return the request one step back when the process design allows
- My requests: tracking what you opened yourself, with the current stage
- Canvas with step dragging, curve connections, zoom and pan
- Human task, approval, service, notification, timer, and subprocess steps
- Detours by condition, parallel paths and junction that only releases when all branches arrive
- Validation before publishing: orphan step, dead-end deviation and unreachable end
- Frozen published version: request in progress never changes design midway
- Simulation of the process without recording anything, to test the design before releasing
- Card builder with text, number, currency, date, selection, file and line grid fields
- Domain fields that consult the system itself: class, graduate, cost center, branch, supplier and product
- Conditional field that only appears when another field has a certain value
- Control who edits what: each step only releases the fields that fit it
- Validation on the server, with mandatory mask and rule per field
- Form reused between processes and versioned along with the design
- Height by value range, with next level triggered automatically
- Quorum for approval: all, majority, anyone or defined quantity
- Assignment by user, role, department, requestor manager, cost center or branch manager
- Deadline in busy or working hours, with calendar and holidays per branch
- Reminders before due date and escalation with reason recorded in track
- Delay panel with what has already expired and who is stuck
- Folders with own permission and search by name, tag and content
- Versioning with history: each new version preserves the previous one
- Checkout with exclusive lock, so no two people can edit the same file
- Publication that goes through an approval flow before becoming valid as an official document
- Validity with periodic review: expired document generates review task
- Reading science: whoever needs to read the procedure confirms it, and it is recorded
- Request attachment that points to the controlled document, instead of becoming a loose copy
- Immutable track of movements, without editing or deleting, with before and after data
- Comments on the request mentioning colleagues, mirrored in Partiu Teams
- Attachments served by authenticated endpoint, revalidating the link with each access
- Permissions per action: view, start, execute task, manage, draw, configure authority and view indicators
- Scope per branch in every consultation, respecting the multi-unit structure
- Those who have no connection with the request do not even see that it exists
- Summary with in progress, delayed and completed in the period
- Openings and completions per day, to see the queue growing or draining
- Bottlenecks per stage: average time stopped at each point in the flow
- Deadline compliance by process and by approver
- Load per person, with the volume of open tasks for each person
- Indicators calculated from the track itself, without parallel typing
- Input trigger with own key: an external system opens the request via API
- From-to fields, to translate the received payload to the process file
- Key saved only as a hash and limit of calls per minute
- Event-subscribed webhooks: request started, completed, canceled, task created, completed, and delayed
- Service step that calls endpoints from an authorized list, with retries and time limits
- Documented API, with the same engine serving the panel, app and third-party systems
- Bridge with three modes per flow: off, in shadow and active
- Shadow mode: the engine tracks in parallel and the convergence between the two is measured
- Active mode: the engine decides and writes the outcome back to the source register
- Expense, purchase requisition, HR request and freelancer redemption already connected
- Request linked to the originating record, opening on both sides
- Nothing is deleted: the business table remains the source of the record
Want to see Workflow & Document Management in your operation?
See a demonstration using your own numbers, with no obligation. A conversation will help you decide whether the module solves your needs.