IFS Cloud 25R1 Development and Customization Enhancements: What North American Manufacturers Should Pay Attention To

After reviewing the 25R1 enhancement material, my view is simple: this release is less about flashy features and more about making IFS safer, cleaner, and faster to extend. That matters a lot for companies with complex workflows, multiple environments, and ongoing reporting, integration, or application-configuration work.

Why 25R1 Matters

Most IFS customers do not struggle because the core ERP is weak. They struggle because:

• customizations become hard to manage over time
• admin teams need better tools to configure pages and lobbies efficiently
• deployments across environments are too manual
• small development mistakes create avoidable rework during testing or upgrades

IFS Cloud 25R1 addresses several of these pain points directly.

1. Better Lobby Usability with Enhanced Links List Layouts

The Links List element in lobbies is now more flexible. Instead of a plain, compact list only, teams can create a richer tile-style presentation with icons, colors, and descriptions.

For power users, supervisors, and department leads, lobby design matters. A cluttered landing page slows adoption. A clearer one improves navigation and reduces training overhead. With the new layout options, companies can make key actions easier to spot, visually separate high-priority links from low-priority ones, add descriptions so users understand where each link takes them, and apply conditional formatting to highlight important items.

This is especially useful for manufacturing environments where different roles need fast access to different functions — planners jumping into shortages or order exceptions, buyers monitoring supplier issues, service teams tracking urgent work queues, and finance teams watching approval backlogs. A small enhancement with a very practical impact on usability.

2. Page Designer Is Becoming More Valuable for Functional Teams

Page Designer continues to move IFS in the right direction: more control from the configuration layer, with less need for heavier technical intervention.

Conditional formatting on list pages. Admins can now configure conditional formatting directly on list pages through Page Designer. That means teams can highlight records based on business rules without building a custom page for every visibility requirement — overdue customer orders shown more prominently, late purchase orders flagged for buyers, critical maintenance work orders highlighted for planners, exceptions in approvals or inventory transactions surfaced faster.

Smart Editor controls. IFS also adds more control over AI-assisted writing support in Details and Notes fields. Organizations can decide whether to enable it, restrict certain commands, or relabel the function to fit internal terminology.

For companies trying to keep their system closer to standard, this is the right direction. More configuration capability means fewer unnecessary customizations, faster response to user feedback, better user experience without code-heavy changes, and lower long-term support cost.

3. Multi-ACP Delivery Simplifies Configuration Deployment

One of the more practical improvements in 25R1 is support for delivering multiple Application Configuration Packages in a single delivery. If you manage several configuration packages across environments, you already know the pain: separate packaging, extra coordination, more room for inconsistency, and more deployment overhead.

Being able to deliver multiple ACPs together helps teams reduce packaging effort, improve deployment consistency between environments, simplify release coordination, and lower the chance of missing related configuration items.

For customers with active enhancement roadmaps, multiple sites, or structured test and production promotion processes, this can save real administrative time. It also makes controlled releases cleaner, which is exactly what mature IFS environments need.

4. Outbound Messages Now Handle Custom Attributes More Cleanly

IFS Cloud 25R1 improves support for custom attributes in outbound messages by adding a dedicated option to expose those attributes when needed.

This matters because outbound integrations often become messy when business-specific data must travel outside IFS. Many organizations add custom attributes for operational reasons, but then discover that downstream integrations, reporting layers, or connected applications do not automatically receive that data the way they expect.

25R1 gives teams more explicit control over whether a custom attribute is exposed in outbound messaging. That is important for customer-specific integrations, supplier communications, downstream reporting platforms, and data synchronization across external systems.

It also reduces ambiguity. Instead of hoping custom data appears where it is needed, teams can configure exposure intentionally. That leads to more reliable integrations and fewer surprises during testing.

5. SCA Improvements Raise the Quality Bar for Developers

This is one of the strongest parts of the release. IFS has introduced several Software Component Assembly improvements aimed at catching bad patterns earlier. That is exactly what mature development teams want: fail early, fix early, avoid expensive cleanup later.

25R1 introduces stronger checks around areas such as unnecessary dependency annotations, invalid characters that can break deployment flows, improper access to internal framework methods, invalid CRUD behavior in inheritance scenarios, improper enum usage, time-zone-related attribute validation, and missing translation settings.

Clients may never see these validations directly, but they will feel the benefits: cleaner custom code, fewer avoidable deployment failures, lower regression risk, more predictable extension behavior, and less time burned on preventable technical defects.

If your partner or internal team is developing in IFS regularly, these guardrails are a good thing. They help enforce discipline before issues reach production.

6. Developer Studio Gets More Useful for Real Project Work

IFS also improves Developer Studio with a few features that are easy to overlook but valuable in day-to-day delivery:

• Validate Navigator Entry — helps detect broken or incomplete navigation references when entries are removed or renamed.
• Find Usage for client files — extends a genuinely useful navigation capability into more of the development workflow.
• Required change history support — encourages better documentation discipline and aligns with stronger coding standards.

These improvements support better maintainability. In real projects, that means fewer broken references in deliveries, easier impact analysis before changes, better auditability of what changed and why, and less dependency on tribal knowledge. The kind of boring-but-important improvement that pays off over time.

7. Model Inheritance Support Can Reduce Redundancy

Model inheritance support in code generation is another meaningful enhancement for teams building more structured extensions. At a high level, this helps developers separate shared logic into parent entities while keeping child-specific behavior isolated where it belongs.

For larger solutions, this can improve reusability, consistency, maintainability, and scalability of future enhancements.

Not every customer will need this immediately. But for organizations building more sophisticated extensions, it provides a cleaner pattern than repeating the same logic across multiple entities. That said, it should still be used carefully. Inheritance can make a design cleaner, but it also demands stronger development discipline. A good architecture team will treat this as a tool, not an excuse to overengineer.

8. JSON Viewer Helps with Troubleshooting and Admin Efficiency

IFS Cloud 25R1 also introduces a JSON Viewer that can be embedded in pages for admin-level users, developers, and analysts.

JSON shows up everywhere in modern IFS environments — integrations, payload troubleshooting, assistant and dialog logic, data validation, and support investigations. Having a readable in-app way to inspect JSON can speed up debugging and reduce friction when analyzing system behavior.

This is most valuable for moderate-sized payloads and targeted troubleshooting. It is not a replacement for enterprise-grade tooling on very large structures, but it is still a welcome addition for day-to-day support and development work.

What 25R1 Means for IFS Customers

The common theme across these enhancements is control. IFS is giving customers and delivery teams more control over how pages and lobbies are presented, how configurations are deployed, how custom data is exposed, how development errors are prevented, how extension models are structured, and how technical payloads are inspected.

For clients, that translates into three important outcomes:

• Lower support overhead — better tooling and validation reduce preventable issues.
• Faster enhancement delivery — configuration teams can do more from standard tools, and deployment packaging becomes easier to manage.
• Better long-term upgrade posture — cleaner extensions and stronger guardrails usually lead to fewer problems during future upgrades.

My Recommendation

If you are running IFS Cloud and actively enhancing your environment, 25R1 is worth reviewing closely with both your functional and technical leads. The biggest opportunities are likely to be:

• using Page Designer more aggressively before choosing customization
• cleaning up how you manage ACP deployments
• reviewing outbound message designs where custom attributes matter
• aligning your development team with the new SCA validations
• identifying where improved lobby and page usability can help adoption

This is not a release where one feature changes everything. It is better than that — it strengthens the day-to-day mechanics of building and supporting IFS properly. For serious IFS customers, that is exactly the kind of release that creates long-term value.

Need Help Evaluating 25R1 for Your Environment?

IFS Expert helps North American manufacturers evaluate, design, and implement IFS enhancements that stay practical, supportable, and upgrade-conscious. We can help with IFS Cloud upgrade planning, BPA and configuration-first design, custom fields, custom events, and outbound messaging strategy, Developer Studio and extension architecture reviews, and remediation of fragile legacy customizations.