Comparing changes

Comparing changes in application elements allows you to quickly check differences between two versions of the same component or between two exported items. This makes it possible to:

• analyze changes introduced by the team,

• verify dependency consistency,

• prepare components for migration or deployment.

These features are available in the tabs Difference and Compare artifacts, located in the module Overview in Eximee Designer.

---

Tab Difference – comparison of versions of the same element

It 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 they select two versions: the “left” and the “right”.

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

Figure 1. Artifact comparison in versions 1.5 and 1.9

Supported element types:

• forms

• composite components

• business components

• scripts

• script validators

• script tasks

This feature allows for a detailed review of changes before saving a new version, during historical review, or in team collaboration.

---

Tab Compare artifacts – comparison of two exported elements

It enables comparison of two files .xml or .json with exported application elements – focusing on their dependencies.

How does it work?

The user drags two files into the field drag & drop.

Figure 2. Artifact comparison window

The system analyzes dependencies and presents a list of differences.

Figure 3. Comparison of two exported artifacts

Types of differences detected:

• ➕ New dependency – appears only in the second file.

• ➖ Removed dependency – appeared only in the first file.

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

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

When to use comparison?

• Before publishing a new version of a component – 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 make sure dependencies match expectations.