For the complete documentation index, see llms.txt. This page is also available as Markdown.

Documentation

Overview

Purpose

The IFS API Change Impact Analyzer is a service designed to track and compare changes in Projections and their components across different versions of IFS Cloud using OData. It helps users identify structural and functional differences between versions, enabling better impact analysis, validation, and upgrade planning.


Scope & Audience

Primary Users

  • Developers

  • Solution Architects

  • System Administrators

Secondary Users

  • Integration Specialists

  • Technical Consultants


Core Use Cases

  • Version Comparison – Compare projections between two IFS versions

  • Upgrade Impact Analysis – Identify breaking or impactful changes before upgrades

  • Regression Validation – Verify consistency across environments

  • Integration Review – Analyze API changes affecting external systems


Accessing the Application

The IFS API Change Impact Analyzer is hosted as a service in Novacura and available through the Marketplace Hub.

  • Portal Page: Flow Extensions

  • Access Link: Here

Users can access the service directly without any installations through the Marketplace Hub portal.

If you are unable to access the Marketplace Hub portal page, please reach out to your account manager.


How to Compare IFS Versions


Step 1: Select Organization

Users begin by selecting the organization for comparison.

Actions

  • Next – Proceed to application package selection


Step 2: Select Application Package

Choose the application package that contains the projections.

Actions

  • Next – Proceed to application selection


Step 3: Select Version Range

Define the comparison range.

Fields

  • From Version – Default lowest available version

  • To Version – Default latest available version

Users can adjust both values using dropdown selections.

Step 4: Select Applications

Users can select one or multiple applications to analyze.

While the application supports selecting multiple applications for analysis, processing a large number of applications simultaneously may increase execution time and, in some cases, lead to timeouts. For optimal performance and reliability, it is recommended to analyze larger or complex applications individually.

Actions

  • Next – Start comparison


Step 5: Run Comparison

The system scans selected applications and their components.

Process Includes

  • Projection metadata analysis

  • Component-level comparison


Step 6: View Results

Results are displayed in a structured table format.

Features

  • Full list of records

  • Highlighted differences between versions


Filtering Options

Show Changes Only

Filters the results to display only modified records.


Export Results

Users can export the comparison results.

Export Options

  • File format: CSV

Tip: For better visualization of the exported .csv file, it is recommended to import the file into Microsoft Excel using semicolon (;) as the delimiter. During the import process, ensure that the first row is set as column headers to properly structure and display the data.


Exit Application

Users can exit the tool at any point.

Action

  • Exit – Close the application

Last updated

Was this helpful?