I believe it should have worked as you describe. The impersonated user name should have appeared in the Last Modified By & Submitter. Also the $USER$ should have been evaluated to the impersonated user. I ran a simple test run of the C driver program and also a small C# .NET API code snippet - both worked as I expected. As for me, I ran the 7.1 bits (currently in Beta, are some of you guys checking it out??) of server as well as driver/API/.NET API. So, as to your situation, I can think of user error (did you really go to right server? did you really impersonate? Are you verifying the right entry data?); Or, there indeed may be a bug in pre-7.1 version. If at all this is the case, it most likely is a defect in the underlying C API (failed impersonation does not surface an error status) OR the Server (impersonated user does not quite work as it suppose to). You may want to let me know what your server version is, we can check that out.
Appajee ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Heider, Stephen Sent: Friday, May 18, 2007 4:36 AM To: [email protected] Subject: Re: "Impersonating" a requester using .net Remedy API Appajee, Is the value of $USER $ in a form supposed to be the user specified in the ImpersonateUser() call? Here is a snippet that submits a new record to a form. After submitting, the values of Submitter and Last Modified By are "Demo", not the ImpersonateUser value. __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
