...
In XTM Workbench, you might sometimes come across the following message displayed in the metadata of 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.
...
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 this happened, XTM Cloud indicated that the previous TM match has been marked with the aforementioned message, as XTM indicated that it is not longer usedcannot be returned anymore, since a newer TM match with the same source and target has been found for this segment.
Generally, this is what it looks like from the mechanism perspective:
...
Each TM match that was populated into the target segment during the project analysis (the target segment was filled with the translation from the TM match) should be kept on the list in the Matches tab of the docked panel even if its score, status, target or context has been changed.
Two matches with matching source and target are viewed as duplicates, therefore only the newer match can 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
...
.
You do not use Not Approved Memory
...