Baseline Status is set to "Behind" after a Release Update
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.
Page 1 / 1
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
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.
Hope this would help someone who gets the same issue.
Not required to Delete, but that's a last Option.
Step1 :Go to Page Configuration and Unpublish .
Step2: Click Show details , reverts to other page . or directly Click Page Designer.
Step 3: select the Object and user finds an option Page designer .
Step4 : Review the objects and click the rebase option
Step5 : shows as rebased.
NOTE: Some times its going to end up with Client error , where we cant rebase or click anything on the screen Except Return Home. . Trying to explore Solution .
Not required to Delete, but that's a last Option.
Step1 :Go to Page Configuration and Unpublish .
Step2: Click Show details , reverts to other page . or directly Click Page Designer.
Step 3: select the Object and user finds an option Page designer .
Step4 : Review the objects and click the rebase option
Step5 : shows as rebased.
NOTE: Some times its going to end up with Client error , where we cant rebase or click anything on the screen Except Return Home. . Trying to explore Solution .
When you get that Client Error, what happens at that point? The page we are trying to access that generates that error also errors out when we look at the projection in API Explorer. Is that something we would need to raise a support case for?
. Trying to explore Solution .