Comparing changes

Comparing changes in application elements allows you to quickly check differences between two versions of the same component or between two exported elements. Thanks to this you can:

  • analyze changes introduced by the team,

  • verify dependency consistency,

  • prepare components for migration or deployment.

These functionalities are available in the Difference and Compare artifacts, located in the Overview in Eximee Designer.


Tab Difference – comparison of versions of the same element

Allows you to compare two versions of the same application element, e.g. a form, script, or composite component.

How does it work?

  • The user selects an element (e.g. a form) from the list.

  • Then selects two versions: the “left” and the “right.”

  • The system presents the differences between versions – these can be changes in content, code, structure or properties.

Illustration 1. Artifact comparison between version 1.5 and 1.9

Supported element types:

  • forms

  • composite components

  • business components

  • scripts

  • script validators

  • script tasks

This functionality allows a detailed review of changes before saving a new version, when reviewing history or working in a team.


Tab Compare artifacts – comparison of two exported elements

Allows you to compare two files .xml or .json with exported application elements – focusing on their dependencies.

How does it work?

The user drags two files into the drag & drop.

Illustration 2. Artifact comparison window

The system analyzes dependencies and presents a list of differences.

Illustration 3. Comparison of two exported artifacts

Types of detected differences:

  • New dependency – occurs only in the second file.

  • Removed dependency – occurred only in the first file.

  • 🔁 Dependency version difference – the dependency concerns the same element, but with a different version.

If no differences are detected, the following message appears: “No data to display”.

When to use comparison?

  • Before publishing a new component version – to make sure what has changed.

  • During code review – to assess changes introduced by the team.

  • During migration – to compare exports between environments.

  • During integration – to ensure that dependencies match expectations.

Last updated

Was this helpful?