Update-Safe IFS Cloud Extensions: Ensuring Business Continuity
How to build modifications that don't block system updates and significantly reduce TCO?
For an IT Director, transitioning to IFS Cloud is a paradigm shift. Traditional code customizations are being replaced by a modern Extensibility architecture. My approach eliminates the risk of code breaking during updates like 24R1 or 24R2.
Full Isolation
Changes are implemented in dedicated layers without touching the IFS Core system.
Low TCO
Reduction of regression testing costs by at least 60% with every bi-annual update.
API Compliance
Leveraging stable OData and REST API endpoints instead of direct SQL queries.
Comparison: Legacy vs. Update-Safe Approach
| Feature | Legacy Modifications | My Update-Safe Approach |
|---|---|---|
| System Release/Update | Long and costly fix-up process | Automatic compatibility |
| Technical Risk | High (code conflicts) | Zero (layered isolation) |
| Evergreening Compliance | None - blocks the system | Full - supports IFS strategy |
Frequently Asked Questions (FAQ)
Will my extensions work in IFS Cloud 24R2?
Yes. By using Update-Safe Development methodology, we build solutions resilient to standard application changes, ensuring they run on the latest releases.