Guides to building apps on IFS Cloud
Custom apps, the OData API and clean upgrades, explained in plain words.
Five short guides on IFS Cloud
These guides cover IFS. NgageCode itself builds on IBM Maximo, IFS and SAP. For any other application, we teach Ngage how it works in weeks.
-
AI app builders for IFS, explained
What one builds on IFS Cloud, and what keeps it safe.
-
Build, buy or generate on IFS Cloud
Three ways to close a gap in IFS, and how to choose.
-
How the IFS Cloud OData API works
Projections, queries, ETags and actions, and where integrations go wrong.
-
Close IFS gaps without core modifications
Build beside IFS through its APIs, and keep upgrades clean.
-
Build industry accelerators on IFS Cloud
The apps that fit standard IFS to one sector, built faster.
Six IFS terms the guides use
One line each, so the guides read quickly.
- Projection
- A published OData service over part of the IFS model.
- Entity set
- The records a projection serves, such as customer orders.
- Enumeration
- Fixed values. Filters take the value, not the label.
- ETag
- A record’s version stamp, sent back with every update.
- Bound action
- An operation such as release, called on a record.
- Server defaults
- Values IFS proposes for a new record.
How NgageCode works on IFS
Four rules every app keeps on IFS Cloud.
- Official interfaces
- OData projections and official IFS actions, never the database.
- The user’s own permissions
- Every call runs as the signed-in user.
- Nothing installed in IFS
- No packages, no schema changes, no core changes.
- A person reads the code
- All AI-written code is reviewed before it merges.
Describe the app your team needs
One sentence is enough to start: what the app does and who uses it.
Describe your app
We build it with you, live, in a safe test setup.