Upgrades & Updates

We have reviewed the material in IFS Cloud Customer Enablement Lunch and Learn and understand that IFS Cloud releases may be supported for up to two years.With 26R2 releasing on 15 Oct, can anyone please clarify the following questions:1. What is the official end-of-support date for IFS Cloud 26R1?2. Does 26R1 remain fully supported until completion of its two-year support period, and if so, what is the exact expiry date?3. When would customers on 26R1 be required to mandatory upgrade?4. Can customers remain on 26R1 until:27R2 is released?28R1 is released?Another specific release milestone?

1. Does IFS cloud version work on OCI. We would like to move our current infra from ###### data center to OCI. This includes all databases along with the current VMWare VM's. Please note that on OCI we can use only Oracle VM.2. Since IFS cloud uses Kubernetes for Middle Tier Server will it wok on OCI? Or should we look at a multi-cloud option where the databases are hosted on Oracle Exadata or Exascale within an Azure datacenter and other VMs are under VMware on Azure.3. Is IFS cloud application certified to work with Oracle autonomous databases. 

Hi,We recently completed a clone of a customer environment running IFS Cloud version 25.2.7.Since the clone, users are being prompted to change their password when logging into the cloned environment, and in some cases are unable to log in until the password has been updated.I have noticed that, for the affected users, the IAM User setting Required User Actions is set to:UPDATE_PASSWORDThis appears to be affecting all users in the cloned environment.Does anyone know what could cause this required action to be applied during or after a clone? We would like to understand the cause so that we can avoid the same issue in future environment refreshes.

We are in the process of upgrading IFS Cloud from 24R1 to 25R2 and noticed all of our lobbies (standard or custom) are impacted negatively when zooming the lobby over 100%.  The elements will get “cut off” with no ability to zoom.Has anyone else been experiencing this?   I couldn’t find any posts or knowedgbase articles on it.  

Are there any plans to support IFS Cloud on newer Ubuntu versions?  We’re currently running 24r2.14 on 22.04.5 and are planning to go to 26r2 early next year. is 26r2 planned to be supported on on Ubuntu 22.04.5? Our Linux/Unix security folks are asking if we can move to a newer version of Ubuntu?Canonical appears to be supporting 22.04 until at least 2027 unless extended support is purchased. Would appreciate any comments.

Does anyone know what ‘Microsoft Windows Azure’ section in the Apps 10 supported systems refers to? In terms of which part of our architecture. We don’t want to upgrade something that is not suitable etc.

Version 24.1.22 I saw an older post asking if there was a way to connect multiple documents to an object, which was eventually implemented as a feature.  I was curious if there was a similar feature that allowed users to connect multiple Objects, like Inventory Parts, to a Change Request. If so, was this also implemented in 24R2, or a later version?

Hican someone let me know when UPD31 will be released for app10 please? thanksGary 

Hello our wonderful IFS Community :)We’re running IFS Cloud 24R1, applying SU20 to a pilot instance for evaluation (going from SU9). We’ve encountered an issue when receiving goods off of a Shop Order, complaining that an Expiration Date is mandatory. I’ve limited things down to something that appears correct in the SU9 version of the API INVENTORY_PART_IN_STOCK_API and a variable check_mandatory_expire_date_ that is referenced in the Check_Insert__ / Check_Common__ procedures.Here’s a sample of the check_mandatory_expire_date_ being set (as opposed to the DEFAULT value for the parameter taking place. Anyone encounter an issue like this when going to SU20? Error message:ORA-20124: Error.NULLVALUE: Field [EXPIRATION_DATE] is mandatory for Inventory Part In Stock and requires a value.INVENTORY_PART_IN_STOCK_API package body snippet:-- Bug SCZ-27258, Start   check_mandatory_expire_date_   BOOLEAN := TRUE;   -- Bug SCZ-27258, EndMany thanks, and feel free to let me know if you’d like addit

After successfully completing the adoption of 25.2.9 into the Build Place, we started the release update process to 26.1.3. All steps completed successfully until the Order Delivery step.During this step, the following errors are reported in:_ERROR_install.log!!!Error deploying file wadaco/DataCaptureSessionLov.edv at 08-SEP-26 13:52:48!!!Error occurred while executing Plsql BlockDECLARE   stmt_ CLOB;   eol_  VARCHAR2(2) := chr(13)||chr(10);   real_table_name_ VARCHAR2(127) := Database_SYS.Get_Or_Generate_Rtb_Name('DATA_CAPTURE_SESSION_LOV_TAB');BEGIN      stmt_ := 'CREATE OR REPLACE EDITIONING VIEW DATA_CAPTURE_SESSION_LOV_TAB AS'||eol_;      stmt_ := stmt_ || 'SELECT'||eol_;      stmt_ := stmt_ || '       capture_session_id,'||eol_;      stmt_ := stmt_ || '       lov_item_value,'||eol_;      stmt_ := stmt_ || '       line_no,'||eol_;      stmt_ := stmt_ || '       lov_item_description,'||eol_;      stmt_ := stmt_ || '       lov_item_description2,'||eol_;      stmt_ := stmt_ || '     

Hello,Our team currently has the 21R2 User Guide for Freight Integration - IFS Cloud. This is Revision A2 updated by KARAUS on 4/7/2022.We are looking for a newer version. At least 24R2 if possible.Thanks

Morning All, Since we have upgraded 25r2 we have lost the text under our bookmarks. Many users have not assigned unique icons to their favourites (just 10 stars) is there a setting to bring this back or is this now just the new UI as this seems like a backwards step. I know I can expand to read the text, but if we have the navigator open it is not very user friendly Thanks Sean  

Hi, We miss the functionality for “search and replace” when updating data in the application.We run IFS Cloud 23R2.6 today

We have requirement from the customer using PSO to allow the Start of the week to be changed to Sunday, in the Calendar opened in the resource gantt.This will be good for customers that wants custom start of the week and not default to Monday.

Hi all,I would like to understand how others are handling customer conversations related to the recently published KB article regarding the Ingress Controller migration and AKS 1.36 upgrade.IFS Product - IFS Cloud (2xRy) – Planned Ingress Controller Migration for IFS Cloud Managed Services One of my customers is running on IFS Managed Cloud and has expressed concerns about the required timeline. They do not believe they can complete the necessary SU upgrades by the deadlines specified in the KBA, particularly the requirement to upgrade UAT, Production, and Build Place environments by 6 November 2026.My understanding from the KBA is that customers who do not meet the migration prerequisites will not be included in the planned November migration and AKS 1.36 upgrade activities. They would instead need to complete the required upgrades by 31 January 2027 and then raise a support ticket to schedule the AKS 1.36 upgrade.I assume we are not the only team facing this situation, so I would app

The community Ingress NGINX controller (kubernetes/ingress-nginx) will retire in March 2026. After that:No new releases No bug fixes or security patches Existing deployments will still run, but without support.What is the impact on current deployments ? Will IFS change ?

Hi All,I am in the middle of Release Update 26R1 SU3 and we’re updating from 25R1 SU13. I am getting some instalation erros related to the ServiceEngApp. We have some customizations there, but it’s the same eventhough I removed all the customization changes in relevant files.I am getting the same errors for the newly customized ServiceEngApp files as well. I just attached the error screen shot below. Please share if you have any idea on this?Error: Thanks & Regards,Asanka. 

The Announcement section on the home page of AssystNet does not show the announcements by default.The workaround is to remove and re-add the announcement section on the home page for the announcements to be visible. And this should be done by each end user individually, which is not feasible. So, this bug should be corrected in successive versions.AssystNet Announcement Visibility IssueAlso, seems the announcements are not visible on the top banned in AssystNet as in AssystWeb. One would guess these would be more useful for the end user business community (AssystNet) than the IT Support people (AssystWeb). So, this feature should be included in AssystNet so that users can see the announcements clearly upfront on the home page rather than going to the ‘Announcement’ section, which hardly anyone does.AssystNet Announcement Visibility Proposal 

We recently deployed the IFS Cloud 25R2 upgrade to our environment. Post-deployment, we noticed that our default mail sender settings in IFS Connect (MAIL_SENDER1) appear to have changed or reset.I want to understand the standard behavior of the 25R2 installer regarding IFS Connect sender templates:Does the 25R2 deployment automatically restore MAIL_SENDER1 back to its default core values?What is the best practice to ensure our custom mail sender parameters are not affected during major release deployments?Any insights from anyone who has experienced this during their 25R2 upgrade would be greatly appreciated.

We are implementing Pagero for e-invoicing in France, we are in version 24R1 and our version does not support the UBL format, we know the new format is available in version 25R2 (which we cannot update at this moment), can we request this structured file in a patch? or how do other IFS customers are handling this issue.  thanks,  

Hello,  We recently received an advisory from IFS relating to a vulnerability in the ‘forgot password’ function (CVE-2026-18963) - https://support.ifs.com/csm?id=kb_article_view&sys_kb_id=0e7c67922bc347507377f6bcf291bf11&table=kb_knowledge&sysparm_article=KB0100589.  I have applied the mitigation script to our test environment without issue - but I have one question before processing further. Does anyone know if the mitigation fix is permanent or is undone every time the IFSIAM pod is recreated (which I believe is done every time the middle tier is restarted with mtctl)?  Thanks, Joe

Please advise if changing the supplier after release of a quotation is possible.  We get an error that says it is not, have to cancel the line and re-enter it to choose an alternate supplier.This should be standard functionality even if it changes to revised status.  We should not be locked into the supplier only because we released the quote.

My customer is currently running IFS Cloud 25R1 SU3, and the business is interested in upgrading directly to 26R1 or 26R2. Is a direct upgrade path supported from 25R1 SU3 to these releases?If we proceed with this approach, what potential technical challenges, risks, prerequisites, and upgrade considerations should we be aware of during the planning and implementation phases? Could you please provide your recommendations and any associated limitations?

We recently completed an upgrade from IFS Applications 10 to IFS Cloud 25R2 and encountered two items that did not appear to migrate as expected.1. Custom RDL Report LayoutsThe custom Report Layout definitions were present after the upgrade, however the associated client-developed RDL binaries were not available in the target IFS Cloud environment. As a result, the layouts existed but the report content itself had to be redeployed.Questions:Is it expected that custom RDL binaries are not migrated as part of the Apps10 to IFS Cloud upgrade process? If so, what is the recommended migration approach for customer-developed RDL binaries? Are there any prerequisites or upgrade steps that would cause the binaries to be excluded during migration?2. Custom Lobby Data SourcesWe also observed that customer-developed Lobby Data Sources from Apps10 were not present after the upgrade to IFS Cloud. Standard functionality appears intact, but the custom data sources had to be recreated manually.Questio

Hi all,We are planning a release update from IFS Cloud 24R2 to 26R1, roughly 16 weeks with Build Place upgrade in Week 3 and Production go-live in Week 14.The business runs 2-week sprints and expects continuous delivery. Once the Build Place is on 26R1, sprint changes cannot go to Production until go-live, and we have no 24R2 line for emergency fixes.Questions:Is running two Build Places in parallel (24R2 for Production support, 26R1 for upgrade work) a supported approach? If yes, how do you re-apply 24R2 emergency fixes into the 26R1 solution so they are not lost at cutover? Have others used a code freeze instead? How long was practical?Any experience would be appreciated.Thanks