im_corp_detect_automated_rehire and im_corp_detect_rehire
Purpose:
These scenario components enable the product to detect whether a newly onboarded user is in fact a returning user with an existing profile. This is done by comparing identity attributes in onboarding requests with attributes of existing users and determining the likelihood that the new user already has a profile in the system. In case of manual requests, the requester will get a warning on the request page when a potential rehire is detected. Automated requests encountering a potential rehire will be routed to a human implementer for fulfillment. The automated rehire detection component (im_corp_detect_automated_rehire) depends on im_corp_detect_rehire; the reverse is not true.
Configuration:
Both of these scenarios rely on configuration data located in the following external data store (extdb) tables:
hid_global_configuration: Adds configuration parameters for these scenarios under the "im_policy_detect_rehire" namespace to control things like detection threshold values, PDRs in scope for this feature or the attribute which flags whether the user is even allowed to be rehired.
im_policy_authorization: Adds an authorization rule to allow
idtrack(automation) requests to be auto-approved so they can be fulfilled immediately, without requiring additional authorization.im_policy_implementers, hid_policy_request_chain: Only relevant for automated requests, these tables contain rules for routing and assigning human implementers to onboarding requests when the system detects a potential rehire.
im_policy_detect_rehire: Contains the list of attributes to be used for rehire detection along with their individual scores used to compute the recipient’s "rehire likelihood" score.