@cap-js/change-tracking 1.1.3 → 2.0.0-beta.1

package/CHANGELOG.md

@@ -4,7 +4,7 @@ All notable changes to this project will be documented in this file.
 This project adheres to [Semantic Versioning](http://semver.org/).
 The format is based on [Keep a Changelog](http://keepachangelog.com/).
 
-## Version 1.1.4 - TBD
+## Version 2.0.0 - TBD
 
 ### Added
 
@@ -12,6 +12,41 @@ The format is based on [Keep a Changelog](http://keepachangelog.com/).
 
 ### Changed
 
+## Version 2.0.0-beta - 27.02.26
+
+### Added
+- Trigger generation for SQLite, HANA, Postgres and H2 to perform change tracking on a database level
+- Allow grouping of changes via new `transactionID` column
+- Added `valueChangedFromLabel` and `valueChangedToLabel` to `sap.changelog.Changes` for localized labels
+- Allow change tracking skip via session variables for entire transactions, entities, elements (`ct.skip`)
+
+### Fixed
+- Performance issues when working with entities that include a large number of fields and children
+- Creation of changelogs at bulk operations
+- Fixed search and sort functionality on the `ChangeView`
+- `LargeString` are truncated and don't lead to failing insert
+- Supports change tracking with every kind of update operation 
+
+### Changed
+- Switch from event handler registration to native database triggers for change capture mechanism
+- Removed table entity `sap.changelog.ChangeLog` and flattened into `sap.changelog.Changes`
+- Display changes with a Tree Table
+- Modifications on `sap.changelog.Changes`
+    - Removed `serviceEntityPath`, `keys` and foreign key `changeLog`
+    - Renamed `entityID` to `objectID`
+    - Renamed `parentEntityID` to `rootObjectID` and `parentKey` to `rootEntityKey`
+    - Added `entityKey`, `createdAt` and `createdBy` from deleted entity `sap.changelog.ChangeLog`
+    - Added `rootEntity` field 
+- Localization is performed on database level and therefore the table `sap.changelog.i18nKeys` that stores localized labels was added
+- Expose localized label fields on `sap.changelog.ChangeView`
+
+## Version 1.1.4 - 03.12.25
+
+### Fixed
+- Server no longer crashes when after a DB migration the service name or attribute name change
+- Fix crash when applications uses feature toogles or extensibility
+
+
 ## Version 1.1.3 - 27.10.25
 
 ### Changed

package/README.md

@@ -5,23 +5,7 @@ a [CDS plugin](https://cap.cloud.sap/docs/node.js/cds-plugins#cds-plugin-package
 [![REUSE status](https://api.reuse.software/badge/github.com/cap-js/change-tracking)](https://api.reuse.software/info/github.com/cap-js/change-tracking)
 
 > [!IMPORTANT]
-> Following the CAP best practices, the new release now requires CDS8 or CDS9 as minimum versions. If you want to use the plugin with an older version of CAP (CDS7), you will need to manually update the peer dependency in `package.json`. Please be aware that there will be no support for this version of the plugin with a CDS version below 8!
-
-> [!IMPORTANT]
-> This release establishes support for multi-tenant deployments using MTX and extensibility.
-> 
-> To achieve this, the code was modified significantly. While we tested extensively, there still may be glitches or unexpected situations which we did not cover. So please **test this release extensively before applying it to productive** scenarios. Please also report any bugs or glitches, ideally by contributing a test-case for us to incorporate.
-> 
-> See the changelog for a full list of changes
-
-> [!Warning]
->
-> Please note that if your project is multi-tenant, then the CDS version must be higher than 8.6 and the mtx version higher than 2.5 for change-tracking to work.
-
-> [!Warning]
->
-> When using multi-tenancy with MTX, the generated facets and associations have to be created by the model provider of the MTX component. Therefore, the plugin also must be added to the `package.json` of the MTX sidecar. 
->Although we tested this scenario extensively, there still might be cases where the automatic generation will not work as expected. If this happends in your scenario, we suggest using the `@changelog.disable_assoc` ([see here](#disable-association-to-changes-generation)) for all tracked entities and to add the association and facet manually to the service entity.
+> With version 2.0 we completely refactored how changes are tracked. Previously the logic was completely on the application layer, which limited the types of queries trackable and came with major performance penalties in larger projects. With v2.0 the changes are now fully tracked on the database layer via database triggers. Furthermore with v2.0 the table definition for changes was cleaned up. This means any upgrade involves a schema change.
 
 
 ### Table of Contents
@@ -46,61 +30,37 @@ a [CDS plugin](https://cap.cloud.sap/docs/node.js/cds-plugins#cds-plugin-package
 
 ## Try it Locally
 
-In this guide, we use the [Incidents Management reference sample app](https://github.com/cap-js/incidents-app) as the base to add change tracking to.
-
-1. [Prerequisites](#1-prerequisites)
-2. [Setup](#2-setup)
-3. [Annotations](#3-annotations)
-4. [Testing](#4-testing)
-
-### 1. Prerequisites
-
-Clone the repository and apply the step-by-step instructions:
-
-```sh
-git clone https://github.com/cap-js/incidents-app
-cd incidents-app
-npm i
-```
-
-**Alternatively**, you can clone the incidents app including the prepared enhancements for change-tracking:
-
-```sh
-git clone https://github.com/cap-js/calesi --recursive
-cd calesi
-npm i
-```
-
-```sh
-cds w samples/change-tracking
-```
-
-### 2. Setup
-
 To enable change tracking, simply add this self-configuring plugin package to your project:
 
 ```sh
 npm add @cap-js/change-tracking
 ```
-If you use multi-tenancy, please add the plugin also to the MTX poroject(The mtx version must be higher than 2.5).
 
-### 3. Annotations
+> [!Warning]
+>
+> Please note that if your project is multi-tenant, then the CDS version must be higher than 8.6 and the mtx version higher than 2.5 for change-tracking to work.
+
+> [!Warning]
+>
+> When using multi-tenancy with MTX, the generated database triggers, facets and associations have to be created by the model provider of the MTX component. Therefore, the plugin also must be added to the `package.json` of the MTX sidecar. 
+
+### Annotations
 
 > [!WARNING]
 > Please be aware that [**sensitive** or **personal** data](https://cap.cloud.sap/docs/guides/data-privacy/annotations#annotating-personal-data) (annotated with `@PersonalData`) is not change tracked, since viewing the log allows users to circumvent [audit-logging](https://cap.cloud.sap/docs/guides/data-privacy/audit-logging#setup).
 
-All we need to do is to identify what should be change-tracked by annotating respective entities and elements in our model with the `@changelog` annotation. Following the [best practice of separation of concerns](https://cap.cloud.sap/docs/guides/domain-modeling#separation-of-concerns), we do so in a separate file _srv/change-tracking.cds_:
+All you need to do is to identify what should be change-tracked by annotating respective entities and elements in our model with the `@changelog` annotation. Following the [best practice of separation of concerns](https://cap.cloud.sap/docs/guides/domain-modeling#separation-of-concerns), we do so in a separate file _db/change-tracking.cds_:
 
 ```cds
-using { ProcessorService } from './processor-service';
+using { sap.capire.Incidents, sap.capire.Conversations } from './schema.cds';
 
-annotate ProcessorService.Incidents {
+annotate Incidents {
   customer @changelog: [customer.name];
   title    @changelog;
   status   @changelog;
 }
 
-annotate ProcessorService.Conversations with @changelog: [author, timestamp] {
+annotate Conversations with @changelog: [author, timestamp] {
   message  @changelog @Common.Label: 'Message';
 }
 ```
@@ -109,7 +69,7 @@ The minimal annotation we require for change tracking is `@changelog` on element
 
 Additional identifiers or labels can be added to obtain more *human-readable* change records as described below.
 
-### 4. Testing
+### Testing
 
 With the steps above, we have successfully set up change tracking for our reference application. Let's see that in action.
 
@@ -119,7 +79,7 @@ With the steps above, we have successfully set up change tracking for our refere
 cds watch
 ```
 
-2. **Make a change** on your change-tracked elements. This change will automatically be persisted in the database table (`sap.changelog.ChangeLog`) and made available in a pre-defined view, namely the [Change History view](#change-history-view) for your convenience.
+2. **Make a change** on your change-tracked elements. This change will automatically be persisted in the database table (`sap.changelog.Changes`) and made available in a pre-defined view, namely the [Change History view](#change-history-view) for your convenience.
 
 #### Change History View
 
@@ -239,7 +199,24 @@ The system now uses the SAPUI5 default setting `![@UI.PartOfPreview]: true`, suc
 
 ### Disable UI Facet generation
 
-If you do not want the UI facet added to a specific UI, you can annotate the service entity with `@changelog.disable_facet`. This will disable the automatic addition of the UI faced to this specific entity, but also all views or further projections up the chain.
+If you do not want the auto-provided UI facet for viewing changes, you can provide your own facet for the `changes` association in the `@UI.Facets` annotation and the plugin won't override it.
+
+Furthermore if you annotate the association as not readable, the facet is also not added. You can achive this, like 
+
+```cds
+@Capabilities.NavigationRestrictions.RestrictedProperties : [
+  {
+    NavigationProperty : changes,
+    ReadRestrictions : {
+      Readable : false,
+    },
+  },
+]
+entity SalesOrders {
+  key ID : Int16;
+      title  : String @changelog;
+}
+```
 
 ### Disable Association to Changes Generation
 
@@ -337,7 +314,6 @@ This section describes modelling cases for further reference, from simple to com
 - [Don'ts](#donts)
   - [Use Case 1: Don't trace changes for field(s) with `Association to many`](#use-case-1-dont-trace-changes-for-fields-with-association-to-many)
   - [Use Case 2: Don't trace changes for field(s) with *Unmanaged Association*](#use-case-2-dont-trace-changes-for-fields-with-unmanaged-association)
-  - [Use Case 3: Don't trace changes for CUD on DB entity](#use-case-3-dont-trace-changes-for-cud-on-db-entity)
 
 ### Specify Object ID
 
@@ -622,25 +598,23 @@ entity AggregatedBusinessTransactionData @(cds.autoexpose) : cuid {
 }
 ```
 
-The reason is that: When deploying to relational databases, Associations are mapped to foreign keys. Yet, when mapped to non-relational databases they're just references. More details could be found in [Prefer Managed Associations](https://cap.cloud.sap/docs/guides/domain-models#managed-associations). In the above sample, there is no column for FootprintInventory in the table AggregatedBusinessTransactionData, but there is a navigation property FootprintInventoryof in OData entity metadata.
+The reason is that: When deploying to relational databases, Associations are mapped to foreign keys. Yet, when mapped to non-relational databases they're just references. More details could be found in [Prefer Managed Associations](https://cap.cloud.sap/docs/guides/domain-models#managed-associations). In the above sample, there is no column for FootprintInventory in the table AggregatedBusinessTransactionData, but there is a navigation property FootprintInventory of in OData entity metadata.
 
-#### Use Case 3: Don't trace changes for CUD on DB entity
 
-```cds
-this.on("UpdateActivationStatus", async (req) =>
-    // PaymentAgreementsOutgoingDb is the DB entity
-    await UPDATE.entity(PaymentAgreementsOutgoingDb)
-        .where({ ID: paymentAgreement.ID })
-        .set({ ActivationStatus_code: ActivationCodes.ACTIVE });
-);
-```
+## Contributing
 
-The reason is that: Application level services are by design the only place where business logic is enforced. This by extension means, that it also is the only point where e.g. change-tracking would be enabled. The underlying method used to do change tracking is `req.diff` which is responsible to read the necessary before-image from the database, and this method is not available on DB level.
+This project is open to feature requests/suggestions, bug reports etc. via [GitHub issues](https://github.com/cap-js/change-tracking/issues). Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our [Contribution Guidelines](CONTRIBUTING.md).
 
+### Testing changes locally
 
-## Contributing
+In the `tests/bookshop` folder a full sample application is provided, against which you can test your changes:
 
-This project is open to feature requests/suggestions, bug reports etc. via [GitHub issues](https://github.com/cap-js/change-tracking/issues). Contribution and feedback are encouraged and always welcome. For more information about how to contribute, the project structure, as well as additional contribution information, see our [Contribution Guidelines](CONTRIBUTING.md).
+```sh
+git clone https://github.com/cap-js/change-tracking
+npm i
+cd tests/bookshop
+cds watch
+```
 
 ## Code of Conduct
 

package/_i18n/i18n.properties

@@ -3,11 +3,7 @@
 #XTIT: Field Name
 Changes.ID=Changes ID
 #XTIT: Field Name
-Changes.entityID=Object ID
-#XTIT: Field Name
-Changes.parentEntityID=Parent Object ID
-#XTIT: Field Name
-Changes.parentKey=Parent Key
+Changes.objectID=Object ID
 #XTIT: Field Name
 Changes.serviceEntityPath=Service Entity Path
 #XTIT: Field Name
@@ -23,32 +19,28 @@ Changes.valueChangedTo=New Value
 #XTIT: Field Name
 Changes.entity=Object Type
 #XTIT: Field Name
-Changes.serviceEntity=Service Object Type
-#XTIT: Field Name
 Changes.valueDataType=Value Data Type
-
-## Change Log Table Fields Description##
-########################################
-#XTIT: Field Name
-ChangeLog.entity=Entity
+#XFLD: Field label
+Changes.createdAt=Changed at
+#XFLD: Field label
+Changes.createdBy=Changed by
 #XTIT: Field Name
-ChangeLog.entityKey=Entity Key
+Changes.transactionID=Transaction ID
 #XTIT: Field Name
-ChangeLog.serviceEntity=Service Entity
-
+Changes.entityKey=Entity Key
 
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Create
+Changes.modification.create=Create
 #XFLD: Field label
-ChangeLog.modification.update=Update
+Changes.modification.update=Update
 #XFLD: Field label
-ChangeLog.modification.delete=Delete
+Changes.modification.delete=Delete
 #XFLD: Field label
-ChangeLog.createdAt=Changed at
+Changes.createdAt=Changed On
 #XFLD: Field label
-ChangeLog.createdBy=Changed by
+Changes.createdBy=Changed By
 
 ## Change History Table##
 ########################################

package/_i18n/i18n_ar.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=\u0643\u064A\u0627\u0646 \u0627\u0644\u062E\u062F\u0645\
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=\u0625\u0646\u0634\u0627\u0621
+Changes.modification.create=\u0625\u0646\u0634\u0627\u0621
 #XFLD: Field label
-ChangeLog.modification.update=\u062A\u062D\u062F\u064A\u062B
+Changes.modification.update=\u062A\u062D\u062F\u064A\u062B
 #XFLD: Field label
-ChangeLog.modification.delete=\u062D\u0630\u0641
+Changes.modification.delete=\u062D\u0630\u0641
 #XFLD: Field label
 ChangeLog.createdAt=\u0648\u0642\u062A \u0627\u0644\u062A\u063A\u064A\u064A\u0631
 #XFLD: Field label

package/_i18n/i18n_bg.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=\u0415\u0434\u0438\u043D\u0438\u0446\u0430 \u0437\u0430
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=\u0421\u044A\u0437\u0434\u0430\u0432\u0430\u043D\u0435
+Changes.modification.create=\u0421\u044A\u0437\u0434\u0430\u0432\u0430\u043D\u0435
 #XFLD: Field label
-ChangeLog.modification.update=\u0410\u043A\u0442\u0443\u0430\u043B\u0438\u0437\u0430\u0446\u0438\u044F
+Changes.modification.update=\u0410\u043A\u0442\u0443\u0430\u043B\u0438\u0437\u0430\u0446\u0438\u044F
 #XFLD: Field label
-ChangeLog.modification.delete=\u0418\u0437\u0442\u0440\u0438\u0432\u0430\u043D\u0435
+Changes.modification.delete=\u0418\u0437\u0442\u0440\u0438\u0432\u0430\u043D\u0435
 #XFLD: Field label
 ChangeLog.createdAt=\u041F\u0440\u043E\u043C\u0435\u043D\u0435\u043D\u043E \u0432
 #XFLD: Field label

package/_i18n/i18n_cs.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Entita slu\u017Eby
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Vytvo\u0159it
+Changes.modification.create=Vytvo\u0159it
 #XFLD: Field label
-ChangeLog.modification.update=Aktualizovat
+Changes.modification.update=Aktualizovat
 #XFLD: Field label
-ChangeLog.modification.delete=Odstranit
+Changes.modification.delete=Odstranit
 #XFLD: Field label
 ChangeLog.createdAt=Zm\u011Bn\u011Bno v
 #XFLD: Field label

package/_i18n/i18n_da.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Serviceentitet
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Opret
+Changes.modification.create=Opret
 #XFLD: Field label
-ChangeLog.modification.update=Opdater
+Changes.modification.update=Opdater
 #XFLD: Field label
-ChangeLog.modification.delete=Slet
+Changes.modification.delete=Slet
 #XFLD: Field label
 ChangeLog.createdAt=\u00C6ndret kl.
 #XFLD: Field label

package/_i18n/i18n_de.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Service-Entit\u00E4t
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Anlegen
+Changes.modification.create=Anlegen
 #XFLD: Field label
-ChangeLog.modification.update=Aktualisieren
+Changes.modification.update=Aktualisieren
 #XFLD: Field label
-ChangeLog.modification.delete=L\u00F6schen
+Changes.modification.delete=L\u00F6schen
 #XFLD: Field label
 ChangeLog.createdAt=Ge\u00E4ndert am
 #XFLD: Field label

package/_i18n/i18n_el.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=\u039F\u03BD\u03C4\u03CC\u03C4\u03B7\u03C4\u03B1 \u03A5\
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=\u0394\u03B7\u03BC\u03B9\u03BF\u03C5\u03C1\u03B3\u03AF\u03B1
+Changes.modification.create=\u0394\u03B7\u03BC\u03B9\u03BF\u03C5\u03C1\u03B3\u03AF\u03B1
 #XFLD: Field label
-ChangeLog.modification.update=\u0395\u03BD\u03B7\u03BC\u03AD\u03C1\u03C9\u03C3\u03B7
+Changes.modification.update=\u0395\u03BD\u03B7\u03BC\u03AD\u03C1\u03C9\u03C3\u03B7
 #XFLD: Field label
-ChangeLog.modification.delete=\u0394\u03B9\u03B1\u03B3\u03C1\u03B1\u03C6\u03AE
+Changes.modification.delete=\u0394\u03B9\u03B1\u03B3\u03C1\u03B1\u03C6\u03AE
 #XFLD: Field label
 ChangeLog.createdAt=\u0386\u03BB\u03BB\u03B1\u03BE\u03B5 \u03C3\u03C4\u03B9\u03C2
 #XFLD: Field label

package/_i18n/i18n_en.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Service Entity
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Create
+Changes.modification.create=Create
 #XFLD: Field label
-ChangeLog.modification.update=Update
+Changes.modification.update=Update
 #XFLD: Field label
-ChangeLog.modification.delete=Delete
+Changes.modification.delete=Delete
 #XFLD: Field label
 ChangeLog.createdAt=Changed at
 #XFLD: Field label

package/_i18n/i18n_en_US_saptrc.properties

@@ -1,55 +1,26 @@
-## Change Table Fields Description##
-####################################
-#XTIT: Field Name
 Changes.ID=VfK41Fkk0DbVUFpSXQ8AqA_Changes ID
-#XTIT: Field Name
 Changes.entityID=ZiKVAYEIaFE0mFC3IeEFbg_Object ID
-#XTIT: Field Name
 Changes.parentEntityID=rnkgCvsaOC/hCPg0vF5EwA_Parent Object ID
-#XTIT: Field Name
 Changes.parentKey=AF/Za63Sqdiz7MXXjEROnA_Parent Key
-#XTIT: Field Name
 Changes.serviceEntityPath=viNxBh1vYxxG3kXw60lQPg_Service Entity Path
-#XTIT: Field Name
 Changes.attribute=cWjA87iS+Cm9tvOovmGGeg_Field
-#XTIT: Field Name
 Changes.keys=yOxQrAVGEhnkFKx3Uu+UQA_Changes Keys
-#XTIT: Field Name
 Changes.modification=uubj6khCgQZXWKOkGbkQgQ_Change Type
-#XTIT: Field Name
 Changes.valueChangedFrom=iohxHdR2acDLGNkvq8miKw_Old Value
-#XTIT: Field Name
 Changes.valueChangedTo=y65Nf+sdmQLjY6WGSnP5Sg_New Value
-#XTIT: Field Name
 Changes.entity=X+l1TGFuUkDEx610r4yjKQ_Object Type
-#XTIT: Field Name
 Changes.serviceEntity=BsNZh4ZOpOzpazhamfXqww_Service Object Type
-#XTIT: Field Name
 Changes.valueDataType=t2TcrxYWauHkEKY0ZWU2sQ_Value Data Type
 
-## Change Log Table Fields Description##
-########################################
-#XTIT: Field Name
 ChangeLog.entity=D240DzaTaZ7FAgpA7cLIiQ_Entity
-#XTIT: Field Name
 ChangeLog.entityKey=xK+ceOtLvrRhC38wITucIg_Entity Key
-#XTIT: Field Name
 ChangeLog.serviceEntity=TWafyw7HrjY/21RcCMxxgQ_Service Entity
 
 
-## Change Log Modifications##
-########################################
-#XFLD: Field label
-ChangeLog.modification.create=HzvJkMkINr79zGGMJxCQhg_Create
-#XFLD: Field label
-ChangeLog.modification.update=Jy7YgwcIfJ78NVdC9GBHXg_Update
-#XFLD: Field label
-ChangeLog.modification.delete=6Vb15r75SwLYaAwPBAAlXA_Delete
-#XFLD: Field label
+Changes.modification.create=HzvJkMkINr79zGGMJxCQhg_Create
+Changes.modification.update=Jy7YgwcIfJ78NVdC9GBHXg_Update
+Changes.modification.delete=6Vb15r75SwLYaAwPBAAlXA_Delete
 ChangeLog.createdAt=It3muKsTssohbqCBz66Waw_Changed at
-#XFLD: Field label
 ChangeLog.createdBy=uceIpGWLWLeh6E5F5GHPdQ_Changed by
 
-## Change History Table##
-########################################
 ChangeHistory=kUlw1/MxgMjeCPEQdQ3gRg_Change History

package/_i18n/i18n_es.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Entidad de servicio
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Crear
+Changes.modification.create=Crear
 #XFLD: Field label
-ChangeLog.modification.update=Actualizar
+Changes.modification.update=Actualizar
 #XFLD: Field label
-ChangeLog.modification.delete=Eliminar
+Changes.modification.delete=Eliminar
 #XFLD: Field label
 ChangeLog.createdAt=Hora de modificaci\u00F3n
 #XFLD: Field label

package/_i18n/i18n_es_MX.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Entidad de servicio
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Crear
+Changes.modification.create=Crear
 #XFLD: Field label
-ChangeLog.modification.update=Actualizar
+Changes.modification.update=Actualizar
 #XFLD: Field label
-ChangeLog.modification.delete=Eliminar
+Changes.modification.delete=Eliminar
 #XFLD: Field label
 ChangeLog.createdAt=Hora de modificaci\u00F3n
 #XFLD: Field label

package/_i18n/i18n_fi.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Palveluentiteetti
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Luo
+Changes.modification.create=Luo
 #XFLD: Field label
-ChangeLog.modification.update=P\u00E4ivit\u00E4
+Changes.modification.update=P\u00E4ivit\u00E4
 #XFLD: Field label
-ChangeLog.modification.delete=Poista
+Changes.modification.delete=Poista
 #XFLD: Field label
 ChangeLog.createdAt=Muutosaika
 #XFLD: Field label

package/_i18n/i18n_fr.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Entit\u00E9 de service
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Cr\u00E9er
+Changes.modification.create=Cr\u00E9er
 #XFLD: Field label
-ChangeLog.modification.update=Mettre \u00E0 jour
+Changes.modification.update=Mettre \u00E0 jour
 #XFLD: Field label
-ChangeLog.modification.delete=Supprimer
+Changes.modification.delete=Supprimer
 #XFLD: Field label
 ChangeLog.createdAt=Date/Heure de modification
 #XFLD: Field label

package/_i18n/i18n_he.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=\u05D9\u05E9\u05D5\u05EA \u05E9\u05D9\u05E8\u05D5\u05EA
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=\u05E6\u05D5\u05E8
+Changes.modification.create=\u05E6\u05D5\u05E8
 #XFLD: Field label
-ChangeLog.modification.update=\u05E2\u05D3\u05DB\u05DF
+Changes.modification.update=\u05E2\u05D3\u05DB\u05DF
 #XFLD: Field label
-ChangeLog.modification.delete=\u05DE\u05D7\u05E7
+Changes.modification.delete=\u05DE\u05D7\u05E7
 #XFLD: Field label
 ChangeLog.createdAt=\u05E9\u05D5\u05E0\u05D4 \u05D1\u05E9\u05E2\u05D4
 #XFLD: Field label

package/_i18n/i18n_hr.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Entitet usluge
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Stvori
+Changes.modification.create=Stvori
 #XFLD: Field label
-ChangeLog.modification.update=A\u017Euriraj
+Changes.modification.update=A\u017Euriraj
 #XFLD: Field label
-ChangeLog.modification.delete=Izbri\u0161i
+Changes.modification.delete=Izbri\u0161i
 #XFLD: Field label
 ChangeLog.createdAt=Promijenjeno
 #XFLD: Field label

package/_i18n/i18n_hu.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Szolg\u00E1ltat\u00E1sentit\u00E1s
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=L\u00E9trehoz\u00E1s
+Changes.modification.create=L\u00E9trehoz\u00E1s
 #XFLD: Field label
-ChangeLog.modification.update=Aktualiz\u00E1l\u00E1s
+Changes.modification.update=Aktualiz\u00E1l\u00E1s
 #XFLD: Field label
-ChangeLog.modification.delete=T\u00F6rl\u00E9s
+Changes.modification.delete=T\u00F6rl\u00E9s
 #XFLD: Field label
 ChangeLog.createdAt=M\u00F3dos\u00EDt\u00E1s id\u0151pontja
 #XFLD: Field label

package/_i18n/i18n_it.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=Entit\u00E0 di servizio
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=Crea
+Changes.modification.create=Crea
 #XFLD: Field label
-ChangeLog.modification.update=Aggiorna
+Changes.modification.update=Aggiorna
 #XFLD: Field label
-ChangeLog.modification.delete=Elimina
+Changes.modification.delete=Elimina
 #XFLD: Field label
 ChangeLog.createdAt=Ora di modifica
 #XFLD: Field label

package/_i18n/i18n_ja.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=\u30B5\u30FC\u30D3\u30B9\u30A8\u30F3\u30C6\u30A3\u30C6\u
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=\u4F5C\u6210
+Changes.modification.create=\u4F5C\u6210
 #XFLD: Field label
-ChangeLog.modification.update=\u66F4\u65B0
+Changes.modification.update=\u66F4\u65B0
 #XFLD: Field label
-ChangeLog.modification.delete=\u524A\u9664
+Changes.modification.delete=\u524A\u9664
 #XFLD: Field label
 ChangeLog.createdAt=\u5909\u66F4\u6642\u523B
 #XFLD: Field label

package/_i18n/i18n_kk.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=\u049A\u044B\u0437\u043C\u0435\u0442 \u043E\u0431\u044A\
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=\u0416\u0430\u0441\u0430\u0443
+Changes.modification.create=\u0416\u0430\u0441\u0430\u0443
 #XFLD: Field label
-ChangeLog.modification.update=\u0416\u0430\u04A3\u0430\u0440\u0442\u0443
+Changes.modification.update=\u0416\u0430\u04A3\u0430\u0440\u0442\u0443
 #XFLD: Field label
-ChangeLog.modification.delete=\u0416\u043E\u044E
+Changes.modification.delete=\u0416\u043E\u044E
 #XFLD: Field label
 ChangeLog.createdAt=\u04E8\u0437\u0433\u0435\u0440\u0442\u0456\u043B\u0433\u0435\u043D \u0443\u0430\u049B\u044B\u0442\u044B
 #XFLD: Field label

package/_i18n/i18n_ko.properties

@@ -40,11 +40,11 @@ ChangeLog.serviceEntity=\uC11C\uBE44\uC2A4 \uC5D4\uD2F0\uD2F0
 ## Change Log Modifications##
 ########################################
 #XFLD: Field label
-ChangeLog.modification.create=\uC0DD\uC131
+Changes.modification.create=\uC0DD\uC131
 #XFLD: Field label
-ChangeLog.modification.update=\uC5C5\uB370\uC774\uD2B8
+Changes.modification.update=\uC5C5\uB370\uC774\uD2B8
 #XFLD: Field label
-ChangeLog.modification.delete=\uC0AD\uC81C
+Changes.modification.delete=\uC0AD\uC81C
 #XFLD: Field label
 ChangeLog.createdAt=\uBCC0\uACBD \uC2DC\uAC04
 #XFLD: Field label