Service Graph Connectors can find a User (sys_user) table record and populate the ‘Assigned To’ field if the source API is reporting the user information. A user record can be found based on ‘User ID’ (user_name) or ‘Email’ (email).
Integration Commons for CMDB (minimum version 2.6.0) has ‘User Lookup’ operation. This operation accepts username and email as input parameters and returns sys_id of the Users (sys_user) table record if it finds a match. The output of this operation will be mapped to ‘Assigned To’ field on Hardware CIs.
Example:
Customers can customize the behavior of the lookup operation by using the ‘glide.discovery.assigned_user_match_field’ property. By default, the user lookup operation matches the first parameter (User Name) with the ‘User ID’ (user_name) field on sys_user table. If the customer want to match the first input(User Name) with some other field on the sys_user table, they can set the corresponding field name to ‘glide.discovery.assigned_user_match_field’ system property.
Steps to debug:
- Make sure the source is reporting user information by checking the API response or based on records in the import set table.
- Make sure the corresponding user record exists in the sys_user table.
- Make sure the User ID or Email fields match with a record on Users table.
Known Errors:
- SG-SCCM is not able to process the User information when it contains / in the User ID.
- The legacy SCCM plugins have the same issues as SG-SCCM. Since legacy plugins have no planned future releases, customers need to switch to SG-SCCM version with a fix.
