You'll have to do two different processes for the Web and also for the
Client on Win 2000 (use $CLIENT-TYPE$ and $OS$ to differentiate in the Run
If condition of your active link).
 
The process statement, as given, will yield a list on Win 2000, instead of a
particular value. Try using just:
 
$PROCESS$ reg query
HKLM\System\CurrentControlSet\Control\TimeZoneInformation\Bias
 
This should yield a line like: "REG_DWORD     Bias    420". A quick
REPLACE() to ditch the leading tokens, and you're in business.
 
For the Web, you could run a JAVASCRIPT process, then pick up a temp field
value for use in your query. It will be in a slightly different format
(number of seconds from GMT rather than "420", for example) but you should
be able to use it. Try this:
 
$JAVASCRIPT$ var oDate = new
Date();window.TheForm.setFieldValue(tempFieldId, oDate.getTimezoneOffset())
 
Then, use the value from the field you set in your lookup.
 
Anyway, hope this points you in the right direction.
 
Cheers!
 
Chris Woyton 
 
-ps yes Dan, I'm still alive and kickin' :)

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] Behalf Of Saravanan Palaniappan
Sent: Thursday, November 09, 2006 4:22 AM
To: [email protected]
Subject: user offset


** 

When I posted a question regarding the user offset , I got this particular
information but this is not actually working in the windows 2000 and it is
also not working in the web. Can any one help me.

 

Eic cleermen  gave me this solution.

 

 

If your clients are using the Windows User Tool under NT, 2000, XP, or 2003,
you can accomplish this by using a set fields from an active link.  The
value would be:

$PROCESS$ for /f "skip=2 tokens=3" %f in ('reg query
HKLM\System\CurrentControlSet\Control\TimeZoneInformation /v Bias') do @echo
%f

This will set a field to a value similar to either of the following:

0x12c

0xfffffed4

0x12c would be GMT-5:00.  0xfffffed4 would be GMT+5:00.  Windows stores the
value as a hex offset, but Remedy can easily convert this using a lookup
table.

 

One way to make this more useful is by setting a global field using from an
Init Form.  This allows other workflow to quickly access it, with only a
need to call a single run process on the client

 

 

With Regards

PL.Saravanan

BTGS EXPEDIO FM | Team Virtusa (Chennai ATC) | Ph: +44-42002700 Extn: 3279 |
Mobile : 99404-08691 .Email: [EMAIL PROTECTED]

 

__20060125_______________________This posting was submitted with HTML in
it___ 


_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Reply via email to