1.7.7
From: 2026-08-31
- Default merge values are now derived from the change request's activity log instead of treating every difference between the change request and the master record equally. Fields the change request never touched default to keeping the master value, so differences caused by independent edits to the master record are no longer applied by accident. Fields changed in the change request whose initial value still matches the current master value default to applying the change request value. Fields changed in the change request whose initial value no longer matches the master value are reported as a conflict with no default, and the user must choose explicitly before the merge can be completed. If a field was changed several times within the change request, only the earliest entry is used to determine its initial value, and a field whose current value already equals the master value is treated as having no conflict. The same logic applies to attribute values.
- Added support for versioning of files.
1.7.5
From: 2026-07-20
- Fixed minor bug
1.7.4
From: 2026-06-11
- Two new notification events are available — CR Created (triggered when a change request is created for a master record) and CR Merged (triggered when a change request is merged into a master record). Active notification rules are shipped for these events out of the box.
- A new Version panel has been added to the right sidebar. It lists versions with the newest at the top, showing each version's title, creation date and author, and provides quick actions to delete or compare versions.
- Fixed minor bug
1.7.3
From: 2026-05-20
- Adapted to the Core 2.3.5
- Updated Owner/Assigned User/Teams assignment on Change Requests
1.7.0
From: 2026-05-06
- Adapted to Core 2.3
1.6.3
From: 2026-02-27
- Increased loading speed
- Fixed bug with displaying attributes of type Link and Multiple Link in Change History
1.6.1
From: 2026-01-06
- Updated version and change request relation comparison
- Added many minor improvements
1.5.3
From: 2025-11-21
- A new action type — Create Version — has been added. When the versioning system is enabled, a corresponding action is automatically created for each entity. Customers can define a Twig-based mask for generating version names. On the record page, the Create Version action appears in the dynamic actions section.
- Fixed minor bug
1.5.2
From: 2025-11-06
- Added minor improvement
1.5.1
From: 2025-10-14
- A new Versioning feature is added to Entity Management. For version-enabled entities, a new "Create Version" action is available in the record view under "More", opening a modal to name and save a version. A "Compare Versions" action allows comparing the current record with a selected version, switching between versions, and merging fields.
1.4.2
From: 2025-07-30
- Fixed bug with lists view on restore modal dialog
1.4.1
From: 2025-06-16
- Fixed minor bugs
1.4.0
From: 2025-04-23
- Adapted to the new Core
1.3.11
From: 2025-04-04
- Added Left Sidebar to List Pages
- Improved icon placement on the left sidebar
1.3.10
From: 2025-03-28
- Improved Item Filtering in Activities
1.3.9
From: 2025-03-13
- Fixed bug with showing IDs instead of list options in the change history
1.3.8
From: 2025-01-23
- Refactored status icon display
1.3.7
From: 2024-12-16
- Fixed minor bug
1.3.5
From: 2024-11-08
- Fixed bug with inability to restore attribute values for non admin users
1.3.3
From: 2024-09-18
- Added option "Restore all" to restore all changes that have been done at the same moment
1.3.2
From: 2024-09-09
- Updated module functionality
1.3.1
From: 2024-09-03
- Converted Note in stream to markdown
- Fixed bug with restoring attribute values
1.3.0
From: 2024-05-07
- Adapted to Core 1.10.0
1.1.10
From: 2023-11-23
- Restored attribute values are now displayed immediately
1.1.9
From: 2023-10-31
- Adapted to Core 1.7.0
1.1.8
From: 2023-09-14
- Fixed bug with restoring attribute values from stream
1.1.7
From: 2023-09-13
- Fixed bug with displaying attribute values of type list in changing history