Hello Isaac,
I believe the best approach to what you are looking for is the Customer <->
Group Config in the Admin Interface, unless you have multiple queues to one
group and then your customer shouldn't access all the queues from that
group. This is slow to be done the first time, but then is becomes just a
maintenance thing.
Regards
2012/11/14 Isaac Gonzalez
Hi I am using the Ticket ACL here: http://doc.otrs.org/3.1/en/html/ch18s03.html to limit which queues certain customers can see by checking their customer id. This works nicely, but now I want to add a lot more customer id values….****
** **
Does the *UserCustomerID *Parameter below have any limitation in the values you can pass to it? I was hoping to list around 50-100 customer id’s without hindering performance. These customerid’s are pulled from Active Directory by the way. See below example of my config.****
** **
Example of my config:****
** **
$Self->{TicketAcl}->{'Limit queue selection for customers'} = {****
** **
# match properties****
** **
Properties => {****
** **
# current action match properties****
** **
CustomerUser => {****
** **
UserCustomerID => ['value1','value2','value3'….’valuen’],****
** **
},****
** **
},****
** **
# return possible options (white list)****
** **
Possible => {****
** **
# possible ticket options (white list)****
** **
Ticket => {****
** **
Queue => [‘queue1',’queue2 '],****
** **
},****
** **
},****
** **
};****
** **
** **
** **
Thanks,****
Isaac****
--------------------------------------------------------------------- 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
-- ___________________________ Alvaro Cordero Retana Consultor de Tecnologias Gridshield Monitoreo de Redes e Infraestructura. 2258-5757 ext 123 alvaro@gridshield.net www.gridshield.net