We are trying to create an incident from an email that only has the userid (samaccount) available to us. We have not been able to create the incident, since we cannot determine the customer display name associated with the userid. If we log the incident from the desktop client, we can enter the userid in the requester field and the name populates. The customer internal table has the userid and customer display name in it. How can I pull the customer display name for use in the email monitor to create the incident or use the userid to create the incident? We are on version 8.3.2.
Normally your Incident.CustomerName and/or Incident.CustomerID are validated against the Customer table and then trigger all your auto-populated Customer fields. I would try this, which will not require you to alter anything, such as validating the Incident.UserID field and then triggering auto-populations from that.
This assumes you can easily parse the UserID from your incoming email, which I will call Email.ParsedUserID.
This should populate your Customer Display Name with the Full Name from your Customer record based on matching the UserID to the SAMAccountName. If you have duplicate SAMAccountNames it will use the first match.
I got this working in my test system. Thanks.
This has been working great unless we try to process the emails quickly. We found on the metric, that the local cache value can only be set to a minimum of 1 minute. So if we process emails back to back, it uses the same customer name. Are you aware of any way to clear this local cache value of a metric?