Hi
I would like to limit the values in the dropdown when tickets are created. I added the code below to /use/share/otrs/Kernel/config.pm, but it did not have any effect.
$Self->{TicketAcl}->{'ACL-Name-1'} = {
Properties => {
Ticket => {
Queue = ['NOC'],
},
},
Possible => {
Ticket => {
Service = ['Notification'],
},
},
};
Some questions:
· My config.pm file has 3 sections (I am not a perl expert, just started learning) one that starts with “BEGIN”, one that starts with “sub Load” and a bit that starts with use strict; In which part should the ACLs go?
· Should ACLs be enabled in the SysConfig somehow?
Louis
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.
I would like to limit the values in the dropdown when tickets are created. I added the code below to /use/share/otrs/Kernel/config.pm, but it did not have any effect.$Self->{TicketAcl}->{'ACL-Name-1'} = {Properties => {Ticket => {Queue = ['NOC'],},},Possible => {Ticket => {Service = ['Notification'],},},};Some questions:· My config.pm file has 3 sections (I am not a perl expert, just started learning) one that starts with “BEGIN”, one that starts with “sub Load” and a bit that starts with use strict; In which part should the ACLs go?· Should ACLs be enabled in the SysConfig somehow?
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
I would like the ACL to only make service “Notification” available when a customer or agent selects Queue “NOC” for new tickets.
I have put my code just below the comment you mentioned. This is my code:
$Self->{TicketAcl}->{'ACL-Name-1'} = {
Properties => {
Ticket => {
Queue = ['NOC'],
},
},
Possible => {
Ticket => {
Service = ['Notification'],
},
},
PossibleNot => {
Ticket => {
Service = ['Emergency Maintenance', 'Routine Maintenance', 'Scheduled Maintenance'],
},
},
};
At the moment I have not been able to get any ACL to work, so I would really appreciate your help.
Louis
DISCLAIMER
Hi Nils1. 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 SystemCore NetworkNOCRadio NetworkVAS ElementsMy Service list has the following services:Emergency ResponseNotificationRoutine MaintenanceSchedules Maintenance
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-b...@otrs.org [mailto:otrs-b...@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,
DISCLAIMER
Is it a version issue perhaps? I’m running 2.3.4
---------------------------------------------------------------------
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
NEW! ENTERPRISE SUBSCRIPTION - Get more information NOW!
http://www.otrs.com/en/support/enterprise-subscription/
Any ideas??
2010/6/1 Nils Leideck - ITSM <nils.l...@leidex.net<mailto:nils.l...@leidex.net>>
Hi,
On 01.06.2010, at 13:10, Louis Becker wrote:
Is it a version issue perhaps? I’m running 2.3.4
Yes, you need to run at least OTRS 2.4.6 to have ACLs working with considered AJAX reloads.
Freundliche Grüße / Kind regards
Nils Leideck
--
Nils Leideck
Senior Consultant
nils.l...@leidex.net<mailto:nils.l...@leidex.net>
nils.l...@otrs.com<mailto:nils.l...@otrs.com>
Hi Nils
Updated to OTRS 2.4.7. I am able to run ACL that trigger on Queue change to ‘Raw’. Is it possible to trigger ACLs from TicketFreeText fields. Below please find some of my code that is NOT working on TicketFreeText field.
$Self->{TicketAcl}->{'ACL-Limit-SiteList'} = {
Properties => {
Frontend => {
Action => ['CustomerTicketMessage'],
},
Ticket => {
TicketFreeText1 => ['Khomas'],
},
},
Possible => {
Ticket => {
TicketFreeText2 => ['KMS0004'],
},
},
};
Louis
Louis Becker
Project Control Manager
T +264 855 550 000
C +264 855 510 136
F +264 855 202 010
Louis....@leo.na
http://www.leo.na
From:
otrs-b...@otrs.org [mailto:otrs-b...@otrs.org] On Behalf Of Nils
Leideck - ITSM
Sent: 01 June 2010 12:31
To: User questions and discussions about OTRS.
Subject: Re: [otrs] ACL
Hi,
DISCLAIMER
Updated to OTRS 2.4.7. I am able to run ACL that trigger on Queue change to ‘Raw’. Is it possible to trigger ACLs from TicketFreeText fields. Below please find some of my code that is NOT working on TicketFreeText field.$Self->{TicketAcl}->{'ACL-Limit-SiteList'} = {Properties => {Frontend => {Action => ['CustomerTicketMessage'],},Ticket => {TicketFreeText1 => ['Khomas'],},},Possible => {Ticket => {TicketFreeText2 => ['KMS0004'],},},};
That is really sad!
$me->{disappointed}->{‘Bid-sigh’}
Any current plans on this?
Louis
Nils wrote:
That is not working in the current version of OTRS as a FreeTextField change does not reload any other field yet.
DISCLAIMER
That is really sad!$me->{disappointed}->{‘Bid-sigh’}Any current plans on this?
Nils wrote:That is not working in the current version of OTRS as a FreeTextField change does not reload any other field yet.