26R1 - Impact Assessment and Release Update Assessment

Question

Hello all,

This is Chikako Yoshimura who is working as CSM in Japan Region.

I am raising queries on behalf of customer. I would appreciate it if you could answer as soonas you can.

The below is customer message.

---------------------

We are planning to conduct an assessment for the release update to the latest version (26R1).
In June, we are planning to perform not only the Impact Assessment but also the Release Update Assessment.

My understanding is that executing RequestReleaseUpdate will create a new version repository (?) in Build Place, and I would like to confirm the following two points:

Is it correct to understand that the current version environment (24R2) will not be affected until CreateDelivery is executed?
Is it possible to change the target update version after completing the Release Update Assessment?

---------------------

Thank you.
Chikako Yoshimura

ashen_malaka_ranasinghe · Answer

Hi ​@Chikako Yoshimura,Here are clear answers to both of the customer's questions, based on the IFS Cloud Release Update Studio documentation.Q1: Will the current 24R2 environment be affected before CreateDelivery is executed?✅ Correct understanding -the current production environment is NOT affected.When the Release Update process is initiated, the system creates parallel branches for both the customer baseline and customer solution repositories. It updates the customer baseline branch to the selected release update version - this happens in the Build Place/Release Update Studio only, not in the live environment.Customers can deploy the delivery to the Use Place/Production environment and continue development on Release Update Studio and do the Build Place cut-over only when they are ready to do so.So, the 24R2 Use Place (production and non-production) environments remain completely untouched until the customer deliberately creates a delivery from the new branch and deploys it. The RequestReleaseUpdate action only triggers the parallel branch creation and generates a sales quotation internally -it does not touch any running environment.Refer to the following documentation:https://docs.ifs.com/techdocs/ale/020_lifecycle/080_release_update_studio/040_after_applying_release_update_to_baseline/020_release_update_without_customization/Q2: Is it possible to change the target update version after completing the Release Update Assessment?⚠️ Yes, technically possible -but with an important note.If the target service update is changed after the assessment, a warning message will be shown recommending running the Impact Assessment again prior to proceeding with the newly selected version.Also, from the documentation: if customizations are done after conducting an Impact Assessment, the analysis needs to be conducted again to identify the impact accurately, as changes done in the master branch would need to be re-done in the release-update branch.In practical terms:Changing the target version (e.g. from an earlier 26R1 service update to a later one) is possibleBut the Impact Assessment must be re-run against the new target to ensure accuracyAny customization uplift work already done may need to be revisitedRefer to the following documentation:https://docs.ifs.com/techdocs/21r2/020_lifecycle/090_release_update_studio/030_apply_release_update_to_baseline/010_fetch_to_baseline/

Did you find what you're looking for? If not:

Sign up

Login to the community

Scanning file for viruses.

This file cannot be downloaded