How NgageChat connects to IFS Cloud
27 native IFS tools over OData, and nothing installed in IFS.
27 IFS tools in five groups
It looks up the IFS data model before it touches a record.
| Group | Tools | What it does | For example |
|---|---|---|---|
| Metadata discovery | 6 | Find the right place in IFS first. | search_ifs_pages |
| API schema | 3 | Learn the exact payload before writing. | fetch_api_endpoints |
| Execution | 11 | Read, write and run IFS actions. | ifs_read_data |
| Field operations | 4 | Common field tasks, with no round trip. | ifs_report_hse_incident |
| Knowledge and recall | 3 | Explain IFS, and remember the thread. | search_ifs_docs |
The IFS rules a write depends on
Get one wrong and the write fails. NgageChat follows each of them.
_Default() resolution
New records start from IFS’s own defaults.
ETag concurrency
A parallel change is caught, never overwritten.
Bound actions and action imports
Release and approve on the record; wizards on the projection.
Enumeration, then list of values
Real options from your system, never invented ones.
Queries checked against real fields
Filters only name columns that exist.
Site aware server time
Dates land on the right day for each site.
How NgageChat reaches each ERP
IBM Maximo, IFS and SAP work out of the box, and one request can work across two of them. For any other application, including a homegrown one, we teach Ngage how it works in weeks.
| ERP | Connects through | Runs within |
|---|---|---|
| IBM Maximo | Maximo’s official interfaces | Each user’s own security groups |
| IFS | OData projections and official IFS actions | Each user’s own IFS permissions |
| SAP | SAP’s official interfaces | Each user’s own SAP authorisations |
| Any other application | Homegrown or specialist software. We teach Ngage how it works in weeks. | |
Nothing is installed in IFS
So there is nothing to reapply after an IFS release update.
- No database connection
- No custom code in IFS
- No credentials minted by us
- No replica or nightly extract
- No screen scraping
Questions integration teams ask
Custom fields, upgrades, sign-in and related writes.
How does NgageChat integrate with IFS Cloud?
Through IFS’s OData REST APIs. 27 native tools discover metadata, read endpoint schemas, read and write records, run IFS actions, handle common field tasks and search the official IFS documentation. There is no database access and no core modification.
Will it work with our custom fields?
Yes. NgageChat reads custom fields live from your environment’s IFS Solution Manager metadata APIs (EntityConfigHandling and ProjectionConfigHandling) and caches them per server. They then behave like any other field.
Will an IFS upgrade break it?
Nothing is installed in IFS, so there is nothing to reapply. We maintain the data model index as IFS releases ship, and your custom fields are read again live. Tell us your IFS version and we will confirm what is supported.
How does it sign in to IFS?
Each person signs in with their own IFS account over OpenID Connect, using the authorisation code flow with PKCE. Token exchange and refresh go through stateless server side proxies, and every request runs under that person’s own IFS permissions.
Can related writes succeed or fail together?
Yes. Related writes can go in one OData changeset, so they succeed or fail as one. For unattended, scheduled processing, NgageFlow is the Ngage product built for it.
See it work on your IFS test system
Send us a task. We run it with you, live, step by step.