Reviewing Mapping Results and Applying Changes
After you run a match, you review the match results and accept, reject, or skip the matches for the request items. Then, you apply the changes to update the request items with the parent information of the accepted match candidates.
Searching and Filtering Match Results
Searching Match Results
Click the Search icon (
) and enter text to search for a match result.
Note:
The system searches the current page of match results only. For very large result sets, you may have to page down to load more results in order to search them.Filtering Match Results
Use the Match Status drop down menu to filter the match results by match status:
- All
- Accepted
- Rejected
- Skipped
- Pending
- No Matches
Tip:
Click Refresh ResultsAccepting, Rejecting, or Skipping Match Results
Select a row in the match results table, and perform an action:
| Action | Results |
|---|---|
| Accept ( |
The request item is updated with the accepted match candidate as
the parent node.
The match results table is updated as follows when you accept a match:
|
| Reject ( |
The Status column for the match item that you selected is updated to Rejected. |
| Skip ( |
The request item is skipped for the current request so that you can re-evaluate it at a later time. The Status column for the match item that you selected is updated to Skipped. Tip: Use Skip to override a previous Accept or Reject action before applying changes. For example, if you initially reject a match candidate and then decide that you want keep that candidate for later evaluation, clicking Skip will undo the reject action. The next time matching is run for the current request, that candidate is presented as a potential match. |
Applying Changes from Match Results
After you have accepted at least one match result, click the Apply Changes button to map the request items for all Accepted match results. Applying the changes modifies the request items for the matches that you accepted by updating the Parent in the request item to the selected target node.
After you click Apply Changes, the match candidates that have been accepted or rejected are removed from the match results table.
Considerations
- Applying changes from the match process updates the request items in a request, but no changes are committed until the request itself is completed and closed. You can continue to modify the request items (see Inspecting Request Items) before submitting the request.
- The status of the accepted matches are retained for the node type and data
source after the request is completed and closed. The next time you bring in a
node that has the same name from the same viewpoint, node types, and data
source, the node is automatically mapped to the node that you previously
accepted.
Caution:
After a request with a matched and mapped item has been completed and closed, you cannot undo that map operation to the existing node. Before the request is competed and closed, you can undo the match to an existing node in the following ways:- Before applying changes (by clicking Reject or Skip in the matching workbench)
- After applying changes but before the request is completed (by deleting the request item and recreating it separately)
However, after the request has been completed and closed you can no longer undo that match. You must delete and re-add the existing target node to delete the stored match information.
Rerunning Matches
In the match result set, click Actions
and select Rerun Match to rerun the matching process
for these node types and data source. This can be helpful if you have updated your
matching rules or you have made changes to the request items that were already
matched.
Discarding Match Results
Click the Discard button on the match results screen to discard all match results that haven't been applied yet. This action removes the match result set from the Match Request Items page and deletes all accepted, rejected, and pending matches for the selected node type and data source. However, match results that have already been applied are not discarded. You can review and delete those request items from the request itself (see Inspecting Request Items).