Skip to main content
Solved

Different framework versions in DEV (build place) and TEST


Forum|alt.badge.img+1

One of our customers upgraded to 24R2 recently. The release upgrade started on 1/22/2025 and build place was updated on  3/7/2025.

Now, in their Build place (DEV) environment, the application version and framework version are different.

However, in the relevant TEST (useplace) environment both application and framework versions are the same.

 

Could you please clarify,

  1. How something like this could have happened
  2. What is the impact this will have on future deliveries/fixes.
  3. What can be done to get the useplace and prod environments to the same framework version as dev.

Best answer by Dihan Perera

Hi ​@Mamarasinghe ,

From IFS Cloud 23R2 SU4 onwards the Middle tier and Database application tier in IFS Cloud were decoupled.

The below explanation is from one of the service bulletins released regarding this change:

When applying a delivery, that delivery will contain the latest middle tier that has been released on the most recent service update of the track. It can be applied to an environment where the database code will not be in the latest service pack level. For example, if the feature track is 24R1 and the most recent service update level is SU1, when a delivery happens to such an environment, the middle tier will be updated to SU1 while the database application can still be on 24R1 GA level.

This change was made to deliver mission critical changes to the middle tier without having to patch the database application. 

So, this means that when a delivery is applied, the latest ifsinstaller components will be fetched, meaning that you will have a newer framework version compared to the application service version.

View original
Did this topic help you find an answer to your question?

2 replies

Forum|alt.badge.img+6
  • Sidekick (Employee)
  • 11 replies
  • Answer
  • March 19, 2025

Hi ​@Mamarasinghe ,

From IFS Cloud 23R2 SU4 onwards the Middle tier and Database application tier in IFS Cloud were decoupled.

The below explanation is from one of the service bulletins released regarding this change:

When applying a delivery, that delivery will contain the latest middle tier that has been released on the most recent service update of the track. It can be applied to an environment where the database code will not be in the latest service pack level. For example, if the feature track is 24R1 and the most recent service update level is SU1, when a delivery happens to such an environment, the middle tier will be updated to SU1 while the database application can still be on 24R1 GA level.

This change was made to deliver mission critical changes to the middle tier without having to patch the database application. 

So, this means that when a delivery is applied, the latest ifsinstaller components will be fetched, meaning that you will have a newer framework version compared to the application service version.


Forum|alt.badge.img+1
  • Author
  • Do Gooder (Partner)
  • 1 reply
  • March 19, 2025

Thanks Dihan.
This helped.


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings