Solved

Baseline Status is set to "Behind" after a Release Update

  • 29 July 2022
  • 2 replies
  • 408 views

Userlevel 1
Badge +2

Hello,

We recently updated our internal IFS Cloud solution from 21R1 to 22R1. 

After applying the update in all our use place environments, we have noticed that some of the existing page configurations are set to Baseline Status = "Behind". 
 

 

When we go inside the Application Configuration Package for these configurations, we noticed that all these configurations are not synced. As per the IFS documentation, we should click on "Publish” button to get these configurations synced, but clicking on the "Publish” button does not change anything. 
 


Does anyone know how to get these configurations back to “Up-to-date” state? 

Thanks in advance, 
Ashan De Costa. 

icon

Best answer by wahelk 23 August 2022, 06:25

View original

2 replies

Userlevel 3
Badge +8

when you unpublish/delete configuration and redo everything again makes it up-to-date.

But not a proper solution as it needs to do for all behind ones.

better if we can get  more information from technology teams .

 

/Wasana

Userlevel 1
Badge +2

We are facing the same issue again with 22R2 update (now the rebase warning sign is visible in the page designer itself) and I finally found an article in the documentation which describes a rebase process. 

https://docs.ifs.com/techdocs/22r2/040_tailoring/225_configuration/200_client_configurations/400_rebase_configurations/
 

Hope this would help someone who gets the same issue. 😀

Reply