...

When Match At Registry is used with Organizational Identity Sources, the Match Reference Identifier will be available in the Org Identity Source Record (Org Identity > View Organizational Identity Source Record), but not in the Org Identity itself. It will also be available in the CO Person Record. When Match At Registry is used with Enrollment Flows, the Match Reference Identifier will be available in the Petition record and the CO Person Record.

System of Record Labels

Anchor
sorlabel sorlabel

The Match API operates with the concept of a System of Record Label, which is used to identify the calling system making the request to the ID Match server. System of Record Labels should be short and alphanumeric with no special characters, such as sis or hris.

...

1. Configure the Enrollment Flow with Identity Matching set to External. Select the appropriate Match Server from the list provided.
2. Make sure the Enrollment Attributes collected include CO Person attributes with the same configuration (including types, if appropriate) as the Match Server Attributes.
3. Set Duplicate Enrollment Mode to an appropriate configuration.
4. For Registry v4.1.0 and later, define the System of Record Label.

Handling Fuzzy Matches

If the match request is inconclusive, a list of potential candidates will be displayed as part of the Enrollment Flow. To link to an existing record, select the appropriate Reference Identifier. To create a new Reference Identifier, select "New".

...

When a Match Resolution Notification is received, Registry will attempt to map the SOR Label and SOR ID to an Organizational Identity Source using the System of Record Label configured on the OIS. If a matching configuration is found, a Sync Job will be queued to reprocess the SOR ID within the OIS, the Job will be processed the next time Job Shell processes the queue. (The record is not processed synchronously on receipt of the notification.)

...

1. Create a new API User via Configuration > API Users > Add API User.
   1. The API User should not be Privileged.
   2. After creating the API User, generate an API Key.
   3. An existing API User can be reused if appropriate.
2. Enable the Core API via Configuration > Core APIs > Add Core API.
   1. Select the Match Callback API.
   2. Set the API User created in the previous step.
3. The full callback URL is available in the Match Server configuration.

Match Resolution Notification does not currently support Match Requests generated by Enrollment Flows.

...