Comparing changes

Comparing changes in application artifacts allows you to quickly check differences between two versions of the same component or between two exported artifacts. This lets you:

• analyze changes made by the team,

• verify dependency compliance,

• prepare components for migration or deployment.

These features are available in the Difference and Compare artifactstabs located in the Overview module in Eximee Designer.

---

The Difference – comparing versions of the same artifact

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

How does it work?

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

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

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

Illustration 1. Comparing an artifact in versions 1.5 and 1.9

Supported artifact 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 browsing history, or in team collaboration.

---

The Compare artifacts – comparing two exported artifacts

Enables comparison of two files .xml or .json with exported application artifacts – 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. Comparing two exported artifacts

Types of detected differences:

• ➕ 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 artifact 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 component version – to make sure what has changed.

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

• During migration – to compare exports between environments.

• During integration – to ensure that dependencies match expectations.