Process owners
- Workflows started by any business event
- Approvals routed to the right people
- On and off switches per workflow
Start a workflow from any business event, ask the right person to approve and hand off to the next step without chasing anyone.
Triggers, logic and approvals in one builder, on the same data and permissions.
The people who design processes and the people who act on them use the same engine.
Real screens from Fynd ERP, shown with demo data for a fictional manufacturer.
Each workflow is a set of steps on a canvas. This one reads a purchase order, checks if it is above 5 lakh and writes a review note for the finance head.
Follow one large supplier invoice through an approval workflow. Each step happens in Fynd ERP.
A supplier invoice above a set amount is captured and a business event is published.
The event starts a workflow, with the full invoice payload available to every step.
A condition checks the amount and the cost centre and picks the approval path.
The finance controller approves it from the approvals inbox.
An email step tells the buyer and the requester that the invoice is cleared.
The invoice moves to its next state and is ready for the payment run.
The parts of automation teams ask about most.
Lay out steps on a canvas with conditions, switches, loops, delays and data mapping. Reuse common steps as sub-workflows and switch each workflow on or off.
Route approvals to people inside a workflow, and let them act from one approvals inbox. Every decision stays on the run's history.
Any business event in the catalogue can start a workflow, and so can a schedule or an outside system calling a webhook. The trigger's data is available to every step.
Define the states a record type can be in and the moves between them. Sensitive moves can require approval before they happen.
Workflows start from events in any module and act on records anywhere in the ERP.
Any business event in the catalogue, a schedule, or an outside system calling a webhook.
Yes. Approval steps send work to people, who act on it from the approvals inbox.
Yes. Each execution keeps a step by step history with the inputs and outputs of every step.
They define the states a record type can be in and the moves between them. Sensitive moves can require approval.
Yes. Scripts run on the edge client at automatic stations, talk to machines over industrial protocols and keep working through short network drops.