With Updates becoming main vehicle for delivery of fixes and new functionality for IFS Applications there is a greater need for our Customers and Partners to be able to validate impact of merged Update on configurations they have developed. This has been made possible from Update 6 for Application 9 and RTM release of Applications 10. However up to very recently it involved help from IFS Global Update Team who could include export of configurations developed by Customer and/or Partner during Update Analysis and provide list of impacted areas.
From second half of 2019 we have even better solution for dealing with Update impact analysis on developed configuration. IFS Product Development made it possible with IFS Configuration Analyzer. Now Customers and Partners can perform impact analysis at any point in time – before, during or after delivery of Update delivery. Tool will present impacted configuration in a list that shows type of impact and allows to export that information to Excel. I would like to share in few steps how to go about running analysis so deployment of Update can be better controlled, and impact is known at early stage. I will not be able to tell you how to adjust files however as it depends on type of change introduced in the new Update and how it impacts on the configuration that has been developed. It is best to have person developing configurations review them if possible but that is not essential.
There are 3 main steps when working with the tool
- Installation (including obtaining latest Interface Report file)
- Loading of information and analysis
- Amendments to configuration source code
Configuration Analyzer requires installation on a PC before it can be used. It is rather straightforward process that is clearly documented by instruction provided with the software. Currently latest version of the tool will have to be requested from IFS, however we will try to make it available in central repository in the future. Please make sure to reach to us once you would like to analyse impact with new Update as tool needs to be supplied with latest version of Interface Report – I hope this will become clear in the next paragraph.
Once Analyzer is installed it works based on 2 sources of information together with selection of base and target Update level
- Interface Report: a file (InterfaceReports.ifr) that stores information about changes introduced in every Update released to date. Most recent version needs to be obtained from IFS Support (through Update case for instance) before analysis is started
- Configuration Export: a folder containing export of all developed configuration that should be included in the analysis. Export can be done from Solution Manager\User Interface\Custom Objects\Configuration Extractor.
Configuration Analyzer documentation describes how to install and load these 2 files into the tool.
Next step is to load interface report details and configuration export into the tool using Load button and then start analysis. Again, these simple steps are listed in tool documentation. Please note that this stage may take a moment depending on number of configurations included in your analysis.
When analysis is completed you will be presented with results. These can be viewed in 2 different views:
- File View: it displays a list of configuration files with interface impacts associated and other information for each file in a grid
- Issue View: an alternative view at the impact that groups files based on type of issue encountered
Everyone has their preference how they would like to tackle adjustments so please explore these 2 options and select one that works best for you.
In this last step the action happens. You will need to go over any impacted configuration and work out if you need to perform any adjustments to configuration source code to make it work without any problems once new Update is installed.
Configuration Analyzer classifies impact into following areas based on severity of impact
- No Impact (by default hidden in the impact list)
You will have to go through all the files with impact highlighted and review if there is need to adjust source code. If you try to do it in single seating, you can use detailed view screen functionality to highlight all tackled configurations
It is possible that majority of impact presented by the tool are safe to ignore but please make sure to spend time to go over the list as you may have runtime errors once Update is deployed in Production environment and affected configurations are not amended or not tested.
If you have any comments or questions, please post them here in this topic and we can work through them collectively making sure you get through configuration adjustment for any new Update as quickly and effortlessly as possible.