The SQL Identifier Assignment Plugin generates Identifiers based on a table of identifiers provided in a SQL table or view, keyed on an existing Identifier associated with the subject entity.
Supported Contexts
- Department
- Group
- Person
Configuration
- The Format Identifier Assigner is part of the CoreAssigner Registry Plugin, which is activated by default.
- When adding a new Identifier Assignment, the Plugin is
CoreAssigner.SqlAssigners. - Plugin configuration options are described below.
There may be considerations in Identifier Assignment ordering, see Key Identifier Type, below.
Server
The SQL Server to connect to.
Source Table Name
The source table to query. This table is currently expected to have a very simple structure, consisting of two columns:
| Column | Type | Description |
|---|---|---|
key | varchar | Key Identifier (existing Identifier found on the Person record) |
identifier | varchar | Assigned identifier (value to add to the Person record) |
key is expected to be unique, multiple Identifiers per key are not supported.
Key Identifier Type
In order to find the correct row in the Source Table, a Key Identifier is used. This Identifier must already exist on the Person record, and be of the Type configured for the Key Identifier Type.
This implies the Key Identifier must be assigned before the SQL Assigner that uses it can run. Different types of business processes could satisfy this requirement, including:
- Use of an Identifier originally provided by an External Identity Source and propagated to the Person record via a Pipeline.
- Generation of the Key Identifier earlier in the Identifier Assignment order and provisioning that Identifier to another system, that then assigns a new Identifier that is loaded in via the SQL Assigner. There may be timing issues with this approach.
See Also
Changes From Earlier Versions
As of Registry v5.0.0
- Initial implementation.