Hi Juan, as far as I know the RegExp is just for matching. In Ticket.pm's TicketACL subroutine you can see multiple points where RegExp is used to match values. If stored, the $1 variable would be available just in that scope, not further. The part where "Possible" values are collected is way further below, so $1 wouldn't be available there any more... Sorry for not having better news, kind regards, Johannes Hoerburger -- Custom Engineering OTRS AG Europaring 4 D-94315 Straubing Am 30.10.2012 um 10:45 schrieb Juan Manuel Clavero Almirón:
Hi all, I have a question about RegExp in ACL's We have several mail accounts, each one going to a different Raw queue (let's say a.otrs@xxx goes to a.raw, b.otrs@xxx goes to b.raw) there is a first level for each of these raw accounts (queues a.first_level and b.first_level) and then a second level, common to all of them (queue second_level).
Is it possible, using RegExp in ACL, to capture the first part of the Raw queue so we can set "Possible actions" to its first level queue?
In perl, I would do something like Properties => { Queue => { Name => ['[RegExp]^(.*)\.Raw'], } }, Possible => { # possible ticket options Ticket => { Queue => ['$1.first_level'], }, }
Kind regards, Juan Clavero
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs