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;
+----+----------+
| id | name     |
+----+----------+
|  1 | unlock   |
|  2 | lock     |
|  3 | tmp_lock |
+----+----------+

Op 2 dec. 2012 22:05 schreef "Flavio Mattos" <flaviomattos86@gmail.com> het volgende:
Hi Michiel! Thanks.. but actually I am using LockID! 

thanks again!


On Sun, Dec 2, 2012 at 12:35 PM, Michiel Beijen <michiel.beijen@otrs.com> wrote:

Hi Flavio:

You should use the TicketUpdate operation; the structure looks a bit like this:

<UserLogin>user</UserLogin>
<Password>pass</Password>
<TicketNumber>20121130123456</TicketNumber>
<Ticket>
    <Lock>lock</Lock>
</Ticket>

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 ... OTRS Feature Add-Ons:  Choose up to 10 OTRS Feature Add-Ons for free and get direct support from the creators of OTRS  –  
Become a Subscription customer now ! - http://j.mp/OBoPuj

On Fri, Nov 30, 2012 at 9:58 PM, Flavio Mattos <flaviomattos86@gmail.com> wrote:
Hi guys!

is it possible to lock a ticket using generic interface? If it is how do I do it?


Thanks

_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev


_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev


_______________________________________________
OTRS mailing list: dev - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/dev
To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/dev