Hi,
we have problem with customer ACL in CustomerTicketZoom. When ticket is in the open state (already), we have in drop down menu two state "'closed','cancelled'" (regarding ACL 1112-CustomerACL). This is OK. But if we choose the "cancelled" state, then it is possible to select other states (regarding ACL 1113-CustomerACL) such as "open", "reopen". This is not ok, because our customers are able to choose any state regardless of the ACL without clicking submit button. This behavior is not ok in my opinion. This states transitions is working in AgentTicketZoom. Why ACL in CustomerTicketZoom is not working correct? Is this a bug? Thank you for your help!
###############
# Customer ACL
###############
$Self->{TicketAcl}->{'1111-CustomerACL'} = {
Properties => {
Frontend => {
Action => ['CustomerTicketZoom'],
},
Ticket => {
State => ['new'],
}
},
Possible => {
Ticket => {
State => ['open'],
},
},
'PropertiesDatabase' => {},
'StopAfterMatch' => '1'
};
$Self->{TicketAcl}->{'1112-CustomerACL'} = {
Properties => {
Frontend => {
Action => ['CustomerTicketZoom'],
},
Ticket => {
State => ['open'],
}
},
Possible => {
Ticket => {
State => ['closed','cancelled'],
},
},
'PropertiesDatabase' => {},
'StopAfterMatch' => '1'
};
$Self->{TicketAcl}->{'1113-CustomerACL'} = {
Properties => {
Frontend => {
Action => ['CustomerTicketZoom'],
},
Ticket => {
State => ['cancelled'],
}
},
Possible => {
Ticket => {
State => ['open','reopen'],
},
},
'PropertiesDatabase' => {},
'StopAfterMatch' => '1'
};
..... etc...
[SOLVED] Customer ACL is not working (states transitions)
Moderator: crythias
[SOLVED] Customer ACL is not working (states transitions)
Last edited by majo053 on 06 May 2015, 09:49, edited 2 times in total.
OTRS and ITSM 4.0.6 (production), MariaDB Ver 15.1 Distrib 5.5.40-MariaDB, CentOS 7.0.1406 (Core)
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: Customer ACL is not working (states transitions)
Since your first ACL is working and the second is not, did you try setting the "PropertyDatabase" to "Property" ? As this is the major difference I can see.
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
Re: Customer ACL is not working (states transitions)
Hello RStraub,RStraub wrote:Since your first ACL is working and the second is not, did you try setting the "PropertyDatabase" to "Property" ? As this is the major difference I can see.
thank you for you response! All ACL is working and I have in every ACL StopAfterMatch. Problem is that customers are able to choose any state regardless of the ACL without clicking submit button. Did you mean this?
$Self->{TicketAcl}->{'1111-CustomerACL'} = {
Properties => {
Frontend => {
Action => ['CustomerTicketZoom'],
},
Ticket => {
State => ['new'],
}
},
Possible => {
Ticket => {
State => ['open'],
},
},
'PropertyDatabase' => {},
'StopAfterMatch' => '1'
};
OTRS and ITSM 4.0.6 (production), MariaDB Ver 15.1 Distrib 5.5.40-MariaDB, CentOS 7.0.1406 (Core)
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: Customer ACL is not working (states transitions)
Ah, now I think I understood.
As soon as you select "closed", the next ACL will activate and enable the re-open state.
To fix this, edit "Property" (which means as much as "current setting") to "PropertyDatabase" (which means as much as "currently saved in the database").
This should solve your problem with cascading ACLs, but sadly you cannot select the frontend-action when you use "PropertyDatabase".
As soon as you select "closed", the next ACL will activate and enable the re-open state.
To fix this, edit "Property" (which means as much as "current setting") to "PropertyDatabase" (which means as much as "currently saved in the database").
This should solve your problem with cascading ACLs, but sadly you cannot select the frontend-action when you use "PropertyDatabase".
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
Re: Customer ACL is not working (states transitions)
Thanks!RStraub wrote:Ah, now I think I understood.
As soon as you select "closed", the next ACL will activate and enable the re-open state.
To fix this, edit "Property" (which means as much as "current setting") to "PropertyDatabase" (which means as much as "currently saved in the database").
This should solve your problem with cascading ACLs, but sadly you cannot select the frontend-action when you use "PropertyDatabase".
OTRS and ITSM 4.0.6 (production), MariaDB Ver 15.1 Distrib 5.5.40-MariaDB, CentOS 7.0.1406 (Core)