...
Select File → Change status on the top left-hand side of the screen.
Change the status for Completed segments to Incomplete or Draft. Keep in mind that only the filtered segments that we applied in step 1 will have their status changed. The status will also be changed for “approved 100% matches”. Do not forget to apply the changes.
...
...
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.
...
The message above appears only if specific requirements are met in XTM Cloud:
Once a project has 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 been used in the initial project, and according to the global TM settings of your XTM instance, a new TM entry has been created (Configuration → Settings → Translation → TM → Matches - general:
Modify the existing TM record if the project segment has the same: Source, Inlines, Context, Tags;
Modify the existing TM record if the project segment with Segment ID has the same: Source, Inlines, Segment ID, Context, Tags).
...
EXAMPLE: Both the initial and further TM matches were created from the segment that contained Segment ID. As the tags and segment IDs for those 2 segments were different, instead of updating an existing TM match, a new TM entry has been created.
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, the previous TM match has been marked with the aforementioned message, as XTM indicated that it is not longer used, since a newer TM match 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.
If such a TM match has been modified and returning it in the same form to the Matches tab is not possible, the match should be maintained but marked with a warning (by hovering the cursor over the warning icon, as an explanation of why such a marking is used in the first place).
The idea is to ALWAYS keep such TM match that was populated during analysis of the initial project with such a warning even if it no longer meets the criteria. In this case, the information in the warning might be a little bit misleading. The match was not changed in anyway, but, as was already mentioned, it no longer meets the criteria. The criteria in this case means that a new TM match appeared that is more recent and has the same source and text. Therefore, the older match is filtered out as a duplicate match