Close IFS gaps without core modifications
Build beside IFS through its APIs, and keep upgrades clean.
The short answer
Change what sits beside IFS, not IFS itself.
What you can build beside IFS
Every change buried in the core is tested again and applied again at each upgrade. The better pattern closes the gap from outside, through the projections IFS publishes.
-
Capture forms
Focused forms that write back to IFS.
-
Reports and dashboards
Views on live IFS records for one team.
-
Integrations
IFS and the systems around it, joined through OData.
-
Approval apps
Inboxes that call IFS actions such as approve.
Core modification compared with an app beside IFS
NgageCode builds the app beside IFS. A person reviews it.
| Compared on | Core modification | App beside IFS |
|---|---|---|
| At each upgrade | Retested and reapplied | Checked against the new projections |
| Installed in IFS | Yes, in the core | Nothing |
| Business rules | Can change with the code | IFS rules still fire on every write |
Questions IFS teams ask
Why avoid core modifications in IFS Cloud?
Core modifications have to be tested again and applied again at every upgrade, which slows and complicates the upgrade path. Building beside IFS on its OData projections keeps the core standard while still closing the gap.
Will users find an outside app second-class?
Not when it is built for the task. A focused app on a phone or at a desk can fit the job better than a broad standard page, while IFS keeps its data, its rules and its permissions.
Does an outside app get around IFS security?
No. Every call runs under the signed-in user’s own IFS permissions, never a shared service account, so people can do in the app what IFS already lets them do, and no more.
Describe the gap you want closed
One sentence is enough to start. We build the app with you on your IFS test environment.