From request to recorded decision
NgageFlow prepares each approval, waits for a yes, then writes it back.
Before and after
The same piece of work, as it waits today and once NgageFlow has run it.
Re: Re: Requisition 7710, can you OK?
- From
- Planner, site 100
- Asks
- 4 mechanical seals for P-114
- Budget
- Not attached
Waiting Day 3, no reply
Approval flow
- 1Read the requisitionIFS
- 2Check the cost centre budgetSAP
- 3Ask the maintenance managerTeams
- 4Release the requisitionIFS
Requisition 7710 is approved and released in IFS.
- Asked for
- 4 mechanical seals, 1,600.00 EUR
- Budget
- Cost centre 4100, 62% used in SAP
- Decided by
- Maintenance manager, in Teams
Logged Who decided, when, and what they saw
Illustrative, on a test landscape. Names, numbers and amounts are samples.
What runs between request and decision
Every requisition over your limit starts a run like this.
New in IFS: requisition 7710, 4 mechanical seals
- 1 Read the requisition7710, 4 seals, 1,600.00 EUR IFS
- 2 Check the cost centre budgetCost centre 4100, 62% used SAP
- 3 Ask the maintenance managerApproved in Teams Teams
- 4 Release the requisition7710 released, decision logged IFS
- 1
Read the requisition
IFS, purchase requisitions
The flow starts when a requisition over your limit needs a yes.
- 2
Check the cost centre budget
SAP, budgets
The agent adds what the approver would look up: the budget and the asset.
- 3
Ask the maintenance manager
Teams, approvals
One message to decide on. No reply by the deadline, and it goes to the delegate.
- 4
Release the requisition
IFS and the audit trail
The decision is written back to IFS and onto the audit trail.
Runs on IBM Maximo, IFS and SAP
Requisitions, exceptions and changes, wherever they wait.
| System | What it holds | What NgageFlow does |
|---|---|---|
| IBM Maximo | Purchase requisitions, work order costs | Prepares the approval, applies the decision |
| IFS | Requisitions, invoices, master data | The same, on IFS |
| SAP | Requisitions, cost centre budgets | The same, and reads budgets for the approver |
| Teams, Slack or email | The approver | Asks, waits, reminds, then delegates |
IBM Maximo, IFS and SAP are ready today. For any other application, including a homegrown one, we teach Ngage how it works in weeks.
You set who decides
Each flow carries its own limit, approver and deadline.
- What needs a yesRequisitions over 1,000.00 EUR
- Who decidesThe maintenance manager
- No reply in 2 daysA reminder, then the delegate
- Below the limitReleased without waiting, and logged
Questions about approvals
Can people approve in Teams, Slack or email?
Yes. The approval goes where the approver works, with the request and its context in one message, and the decision is written back to the ERP.
What if the approver never answers?
You set a deadline. When it passes, the flow reminds them, then routes to their delegate. Every step goes on the audit trail.
Can an agent approve on its own?
Below a limit you set, yes. Above it, the run waits for a person, and you can change the limit for each flow.
Describe an approval that stalls
Name the request, who decides and how long it may wait.
Or write to hello@ngagesuite.com
An approver can question the record in NgageChat before deciding. See NgageChat on projects and finance