**

Thanks for that.

1. The workflow being used is an Active Link.
2. ARS 5.1 ; oracle 9i ; HP-UX

Regards,
Steve


On 4/21/06, Michiel Beijen <[EMAIL PROTECTED]> wrote:
**
Hi Steve,
 
it depends; if you use it in an active link it will use the time on the client. If you use it in a filter or escalation it will use the time on the server.
You did not specify your Remedy version but there is also a keyword $SERVERTIMESTAMP$ available since V6 (or V63?) which will always use the time on the server, even in active links.
 
Regards,
Michiel

 
On 4/21/06, Steve <[EMAIL PROTECTED]> wrote:
**

Hi all, some doubts:

1. Is $TIMESTAMP$ value taken from the client end or from the server?
2. We have a validation of the following sort:

('Diagnosed Time' > $TIMESTAMP$)

and if this is true, we flash an error to the user.

The problem is that they are getting in error one-too-many times and this is happening to a small pocket of users in a location different from that of the server.

Thanks,
Steve

__20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___

__20060125_______________________This posting was submitted with HTML in it___

Reply via email to