user_id, contact_email etc.

XML identifiers: Requires two keys: One named WHBCFK01-10 with the label user_id, and the matching WHBCFV01-10 with string value of your users’s id, contact email, phone number and so on. Purpose: Enables user identification etc. via the heartbeat. Caution: None. Status: Currently in use. Category: Heartbeat keys (labels and value). Usage: Provide both WHBCFKnn and WHBCFVnn with label user_id, email_id, phone_number or similar, and actual value(-s), respectively. This may be done via imports and scripting, or manually, using your EMM/MDM/MAM/UEM system of choice. Note that both labels and values are up to your choosing, and the ones suggested here are based on customer input. Default: Defaults to none. Development status: Stable. No immediate plans to add this as a standard feature to heartbeat information, but will be considered for version 3 (scheduled for release in 2022) which will be able to collect such information from Microsoft AD and possibly LDAP and other major catalog systems. Example: Choosing to use the WAL HeartBeat ConFiguration Key 02 and 03, and Value 09 and 10 to give heartbeats informing about a user’s ID and email address: … <key>WHBCFK02</key> <string>user_id</string> <key>WHBCFK03</key> <string>email_address</string> … <key>WBCFV02</key> <string>johndd41</string> <key>WBCFV02</key> <string>john.doe@MyCompany2u.co.uk</string>