You should also be able to use LockID '2'; I always prefer to use the named
values because it is more explicit. It makes you to not have to check 'what
was LockID 2 again' if you revisit the code after a while.
--
Mike
mysql> select id, name from ticket_lock_type order by 1;
++--+
| i
Juan Manuel Clavero Almirón wrote:
I remember a package called something like "My Tickets" that added a
dashboard module with exactly that, your tickets... but seems
opar.perl-services.de is down, so I can't search it now... maybe if
you try later...
OPAR is back online, there was a short outag
Hi Michiel! Thanks.. but actually I am using LockID!
thanks again!
On Sun, Dec 2, 2012 at 12:35 PM, Michiel Beijen wrote:
> Hi Flavio:
>
> You should use the TicketUpdate operation; the structure looks a bit like
> this:
>
> user
> pass
> 20121130123456
>
> lock
>
>
> Michiel Beijen
> Sen
Hi Flavio:
You should use the TicketUpdate operation; the structure looks a bit like
this:
user
pass
20121130123456
lock
Michiel Beijen
Senior Consultant
OTRS BV
Schipholweg 103
2316 XC Leiden
The Netherlands
T: +31 71 8200 255
F: +31 71 8200 254
I: http://www.otrs.com
It's raining ...
