Apps on IFS Cloud, nothing installed
NgageCode reads your IFS metadata, then builds through official OData services.
How the 16 IFS tools build one app
An illustrative run on a test landscape: a purchase requisition app on IFS Cloud.
Build an app to create purchase requisitions in IFS.
- 1 Find the projection and its required fieldssearch_ifs_pages found PurchaseRequisition Discovery
- 2 Read server defaults and the lists of valuesifs_get_defaults, ifs_search_lov Records
- 3 Check how IFS documents requisitionssearch_ifs_docs Docs
- 4 Generate the app, then a person reviews itSecret scan and static analysis passed Review
- 1
Find the data, read-only
Seven tools find the right IFS pages, projections and fields before anything is built.
search_ifs_pagesget_ifs_entity_api_specget_ifs_enum_valuesget_ifs_lov_detailsget_ifs_required_fieldssearch_ifs_by_componentget_ifs_page_details
- 2
Read and write live records
Eight tools read, create, update and delete through OData, and run business actions.
ifs_read_dataifs_create_recordifs_update_recordifs_delete_recordifs_execute_actionifs_get_defaultsifs_search_lovifs_get_server_time
- 3
Check the IFS documentation
One tool searches the official IFS Cloud documentation.
search_ifs_docs
- 4
A person reviews the code
Secret scanning and static analysis run on every commit, and a finding blocks the merge. No coding tool holds production IFS credentials.
OData details a generated app handles
The parts of IFS Cloud OData that slow a build by hand, and what a generated app does with each.
| In IFS Cloud | What a generated app does |
|---|---|
| Queries | $select, $filter, $expand, $orderby, $top, $skip and $count. |
| Enumerations and lookups | Valid enum values and list-of-values dropdowns, from metadata. |
| Creates | Server defaults through _Default() before a record is created. |
| Updates and deletes | ETag checks, so an edit on stale data is rejected. |
| Business actions | Bound actions such as release, approve and cancel. |
IFS rules still apply to every app
An app built by NgageCode gets no more access than the person using it, and IFS checks every write.
- The signed-in user
- Every call runs under the user’s own IFS grants, never a shared service account.
- Business rules
- Mandatory fields, validations and state machines still apply.
- Tested against IFS
- IFS rejects invalid values, invalid sites and unauthorised operations from an app.
- Nothing installed in IFS
- No schema changes, no customisation. Reads use projections, writes call official actions.
Questions from IFS teams
How does NgageCode connect to IFS Cloud?
Through the IFS Cloud OData REST APIs, the same interface IFS Aurena and integrations use. NgageCode reads your IFS metadata to find the projections an app needs. Generated apps read through projections and write through official actions. Nothing is installed in IFS.
What do the 16 tools do?
Seven find what to build against: pages, projections, API specs, enum values, lists of values and required fields. Eight read and write live records and run business actions. One searches the official IFS Cloud documentation.
Does it handle ETags and enum filters?
Yes. Updates and deletes carry ETag checks, creates fetch server defaults through _Default(), and filters use valid enum values read from metadata.
Can an app run read-only?
Yes. An app can only read, for reports and dashboards, or it can create, update and run actions such as release and approve. Either way it stays within the signed-in user’s IFS permissions.
Does NgageCode work with ERPs other than IFS?
Yes. IBM Maximo, IFS and SAP work out of the box, and one app can work across two of them, for example the asset in IFS and the stock in SAP. For any other application, including a homegrown one, we teach Ngage how it works in weeks.
Describe the app your team needs
One sentence is enough to start: what the app does and who uses it.
We build it with you, live, in a safe test setup.
NgageCode also builds on IBM Maximo and SAP, and one app can read two ERPs.
On Maximo and SAP, apps go through each ERP’s official interfaces, under each user’s own permissions. For any other application, including a homegrown one, we teach Ngage how it works in weeks.