Nils
Code below is still not working for either customers or agents
Any ideas?
$Self->{TicketAcl}->{'Allowed-Services-for-NOC'} = {
Properties => {
Frontend => {
Action
=> ['AgentTicketPhone', 'AgentTicketMail', 'CustomerTicketMessage'],
},
Queue => {
Name
=> ['NOC'],
},
},
Possible => {
Ticket => {
Service =>
['Notification'],
},
},
};
Is it a version issue perhaps? I’m running 2.3.4
Louis
From:
otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Nils
Leideck - ITSM
Sent: 01 June 2010 10:40
To: User questions and discussions about OTRS.
Subject: Re: [otrs] ACL
Hi,
On 01.06.2010, at 10:59, Louis Becker wrote:
Hi Nils
1. Does the system pickup the
new ACLs automatically or must one register the ACLs, or force it to be read? I
can’t get mine to work.
2. Can the ACL have any name, or
should the names be specific?
My Queues are:
Billing System
Core Network
NOC
Radio Network
VAS Elements
My Service list has the following services:
Emergency Response
Notification
Routine Maintenance
Schedules Maintenance
This is a bit more complicated.
1. You do not need to force them or enable them, just save
them in Kernel/Config.pm
2. Instead of “=“ you need to use
“=>” ;-))
3. The ACL for AgentTicketPhone, AgentTicketEmail and
CustomerTicketMessage need to look a bit different in the Properties section.
see this bug for
details: http://bugs.otrs.org/show_bug.cgi?id=4205
This should be a working ACL for your Idea:
$Self->{TicketAcl}->{'00100 -
allowed Services for Queue NOC'} = {
Properties => {
Frontend => {
Action => ['AgentTicketPhone',
'AgentTicketEmail', 'CustomerTicketMessage'],
},
Queue
=> {
Name => ['NOC'],
},
},
Possible => {
Ticket
=> {
Service => ['Notification'],
},
},
};
Freundliche Grüße / Kind regards
Nils Leideck
--
Nils Leideck
Senior Consultant
nils.leideck@leidex.net
nils.leideck@otrs.com
http://webint.cryptonode.de / a Fractal project
DISCLAIMER
This message is intended solely for the individual(s) and entity(s) to which it is addressed. It is confidential and may contain legally privileged information. Any unauthorized review, use, copying, storage, disclosure or distribution of this e-mail and any attachments is strictly prohibited. If you are not the named recipient or have otherwise received this communication in error, please destroy this message from your system and kindly notify the sender by e-mail.