IFS Impact Analyzer¶

To facilitate a seamless upgrade of IFS Cloud from one version to another, the IFS Impact Analyzer pre-analyzes and identifies potential obstacles in your customized code within the applications. If the tool finds a suspect issue, an impact warning is raised and categorized.

To produce the impact analysis report, execute an impact analysis utilizing the Release Update Studio. For further details, refer the Release update studio/Impact Analyzer documentation

Developer Studio Support for Impact Analysis¶

Overview¶

Developer Studio offers features to work with impact analysis reports efficiently. These functionalities provide easy access to the source files and the comparison of the impacted code snippets of each analysis record. The following steps provide more details about features.

Import Impact Analyzer Report to the Customization Project¶

First, the user needs to download the Impact Analyzer Report file - either the JSON file or the source zip file. Impact analyzer report can be imported only to a customization project. Using an RMB option of the customization project 'Impact Analysis', you can initiate the import of the report file. This RMB option is only available for customization projects.

Import analysis report to DS tool rmb option

The above step opens the following panel.

Import analysis report to DS tool import panel

Click the 'Browse' button.
Locate the report file (JSON or source zip format).
Add the file to be imported.

The source zip file contains the JSON file, the baseline file, and the core file of the base and target versions. These files are required to display the source diff on the tool. If you specify the source zip file, the following panel will open the path to unzip the report file.

Panel to specify the path for unzipping the report file

Impact Analysis Report View on Developer Studio¶

The imported report from the above step will be displayed as a table in Developer studio.

Import analysis report to DS tool view

If you import the JSON file, you can double-click on the record to view the customization file.

If you import source zip file, the following RMB options are available for each record in Impact Analysis Window.

Open Custom file in workspace: Open the customization file in the customization project.
View Target file: Open the core source file of the target version.
View Base file: Open the core source file of the base version.
Snippet Diff:
- Diff Custom with Target: Compares the customization source snippet (procedure, function etc.) with the target core version source snippet.
- Diff Custom with Base: Compares the customization source snippet (procedure, function etc.) with the base core version source snippet.
- Diff Target with Base: Compares the target core version source snippet (procedure, function etc.) with the base core version source snippet.
- 3-way diff in external tool: Compares the customization source snippet (procedure, function etc.), base core version source snippet, and target core version source snippet.
File Diff:
- Diff Custom with Target: Compares the customization source file with the target core version source file.
- Diff Custom with Base: Compares the customization source file with the base core version source file.
- Diff Target with Base: Compares the target core version source file with the base core version source file.
- 3-way diff in external tool: Compares the customization source file, base core version source file, and target core version source file.

Diff View¶

Snippet Diff View¶

In the Snippet Diff view, tab name displays the name of the file and source type(Base, Target, Cust) with codesnippet indication. That will allow you to easily identify the source file and the source type with view option.

Note: Snippet diff view is read-only.

Impact analyzer tool snippet diff

File Diff View¶

In the File Diff view, tab name displays only the name of the file and source type(Base, Target, Cust). Customization files can be edited and other source files are read-only. You can use arrow functions to merge changes from Core Base or Target to the Customization file.

Impact analyzer tool file diff

3-way Diff View¶

Developer studio does not support 3-way comparison of source files, so you can configure the external tool to view the 3-way comparison. In the same way, you can configure the external tool to all the source comparison options. Here, the WinMerge tool is used as the external tool of comparison.

To open the configuration panel, navigate to Tools → Options → IFS Options → Impact Analysis and configure said external tool.

Impact analyzer tool config options

Impact Analysis Window Report Filters¶

In the Impact analysis window you can use the filter option by clicking drop down arrow on the column header. You can filter by Component names, File extension, Layer type and Criticality of the impact. You can clear filter by clicking on the icon on each filter.

impact analyzer tool component filter impact analyzer tool file extension filter impact analyzer tool layer filter impact analyzer tool criticality filter

Other Analyzer Tools¶

Upon completing a configuration analysis, it would be required to conduct an impact analysis on configuration items not covered by this tool. Users are expected to run all analyzer tools in order to complete the impact analysis.

Tool	Description
Configuration Analyzer	Analyze impact on configuration items is done with the Configuration Analyzer
Lobby Analyzer	Analyze impact on lobbies is done with the Lobby Analyzer
Page Rebase Designer	For page configurations, the Page Configurations overview page is used to identify the artifacts that are impacted by the upgrade. Affected Client Configurations, then the Page Rebase Designer is used to analyze details and rebase configurations to the new application release.