[otrs] Customer Portal - next state visibility

2015-09-09 Thread Nick Bright
What SysConfig variable would need to be adjusted to control what next-state options are selectable by the customer? I want to restrict it to simply "open" or "closed", while internally we use numerous other close reasons. -- --- - Nick Bright

Re: [otrs] Customer Portal - next state visibility

2015-09-09 Thread Leonardo Certuche
Hello Nick You can accomplish that using ACLs El 9/09/2015 7:44 p. m., "Nick Bright" escribió: > What SysConfig variable would need to be adjusted to control what > next-state options are selectable by the customer? > > I want to restrict it to simply "open" or "closed", while internally we > us

Re: [otrs] Customer Portal - next state visibility

2015-09-09 Thread Nick Bright
On 9/9/2015 7:42 PM, Nick Bright wrote: What SysConfig variable would need to be adjusted to control what next-state options are selectable by the customer? I want to restrict it to simply "open" or "closed", while internally we use numerous other close reasons. I used this to restrict queu

Re: [otrs] Customer Portal - next state visibility

2015-09-09 Thread Nick Bright
On 9/9/2015 7:45 PM, Leonardo Certuche wrote: Hello Nick You can accomplish that using ACLs Everything is easy when you know how. I'm reviewing the documentation now, but really have no idea how to accomplish this. I think that this adapted example from http://otrs.biz/3.0/en/html/acl.h

Re: [otrs] Customer Portal - next state visibility

2015-09-09 Thread Leonardo Certuche
Yes you can. Instead of Queue use State. Do it in CustomerTicketZoom as well El 9/09/2015 7:48 p. m., "Nick Bright" escribió: > On 9/9/2015 7:42 PM, Nick Bright wrote: > >> What SysConfig variable would need to be adjusted to control what >> next-state options are selectable by the customer? >>

Re: [otrs] Customer Portal - next state visibility

2015-09-09 Thread Nick Bright
On 9/9/2015 7:51 PM, Leonardo Certuche wrote: Yes you can. Instead of Queue use State. Do it in CustomerTicketZoom as well $Self->{TicketAcl}->{'ACL-Customer-States'} = { # match properties Properties => {Frontend => {Action => ['CustomerTicketMessage'] }}, # retu

Re: [otrs] Customer Portal - next state visibility

2015-09-09 Thread Nick Bright
On 9/9/2015 7:55 PM, Nick Bright wrote: I don't understand what "Do it in CustomerTicketZoom" means. I see, it should be the Action target. This worked as desired: $Self->{TicketAcl}->{'ACL-Customer-States'} = { # match properties Properties => {Frontend => {Action => ['C

Re: [otrs] Customer Portal - next state visibility

2015-09-09 Thread LQ Marshall
-Original Message- On 9/9/2015 7:55 PM, Nick Bright wrote: > I don't understand what "Do it in CustomerTicketZoom" means. Running a search in Sysconfig using CustomerTicketZoom and following the bouncing ball... I would guess that it was intended to point you to the Admin|Sysconfig|Ticket: