...
In XTM Workbench, you might sometimes come across the following message displayed in the metadata of a particular TM entry for a particular segment: This TM entry has been changed and no longer meets the criteria to be qualified as a match.
...
Note |
---|
IMPORTANT! The message only applies to the TM matches which were populated during project analysis, and which no longer meet relevant criteria once an XTM Workbench session is triggered. From a business perspective, there are some general rules:
|
The message above appears if specific requirements are met in XTM Cloud.
...
When does the message occur?
...
A newer version of a TM match exists
Once When a project has had been created, the segment in question was populated by a TM match, which is currently marked with the message This TM entry has been changed and no longer qualifies as a match.
Then, after some time, a new project with the exact same segment was created under one of the XTM customers, which TM has had been used in the initial project, and according to the global TM settings of your XTM instance, a new TM entry has been was created (Configuration → Settings → Translation → TM → Matches - general:
...
This TM entry has been applied to the reported project, replacing the previous match and being placed at the first place in the Matches tab of the docked panel. Once When this had happened, XTM Cloud indicated that the previous TM match cannot could not be returned anymore, since a newer TM match with the same source and target has been was found for this segment. Two matches with matching source and target are viewed as duplicates, therefore only the newer match can could appear.
Generally, XTM Cloud does not show duplicates (same source and target in both TM matches). Therefore, when suddenly there are two TM matches in a segment that have the same source + target + score
, one of them has to be filtered out – the older one. If the older TM match was populated during project analysis and a TM match update subsequently occurs in XTM Workbench, then this older TM match gets the warning.
...
In this case, a TM match is returned as Approved during project analysis, but its status has changed to Not approved (due to, for example, while the XTM Workbench session is active.
...
The TM entry has thus become an ICE match, and no longer a Leveraged match, so it no longer qualifies as a valid Leveraged match. Therefore, it must get a proper warning in its metadata in XTM Workbench, and the ICE match must appear instead.
A Leveraged match transforms into an ICE match due to update in another project
...
containing the same source file
Another scenario also revolves around Leveraged and ICE matches. This time you also receive a Leveraged match populated during project analysis. Then, you create a new project with exactly the same source file, and this project also gets the same Leveraged match. You accept the TM match in that second project, which causes a new TM entry to be created with the appropriate context, according to your global TM settings:
...
The message might also be displayed in a TM match that does not come from the project’s main XTM Cloud customer, but from one which was added additionally to the project.
...
The root cause for such a message to appear in the first place is that you must have removed the said customer from the project at one point in time during the project’s life cycle.
A populated TM match has a tag
...