I have created a generic agent job, whereby a process can be selected on the ticket creation screen. On submitting the ticket, the ticket overview appears as the next screen.
Ticket creation screen:
View on submitting the ticket:
The agent would have to click on the 'Erfassung' button to start adding the data. Is there a way to configure OTRS such that on clicking the submit button, the agent is shown the first AD of the process, instead of the ticket overview?
Desired view on submitting the ticket:
Show first activity dialog on ticket create
Moderator: crythias
Show first activity dialog on ticket create
You do not have the required permissions to view the files attached to this post.
OTRS 3.3.x (private/testing) on Windows Server 2008 with MSSQL database.
OTRS 3.3.x (private/testing) on CentOS with MySQL database and apache
OTRS 3.3.x (private/testing) on CentOS with MySQL database and apache
Re: Show first activity dialog on ticket create
no.
But why he is not starting the process directly instead of using a phone ticket?
But why he is not starting the process directly instead of using a phone ticket?
"Production": OTRS™ 8, OTRS™ 7, STORM powered by OTRS
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
"Testing": ((OTRS Community Edition)) and git Master
Never change Defaults.pm! :: Blog
Professional Services:: http://www.otrs.com :: enjoy@otrs.com
Re: Show first activity dialog on ticket create
Thanks for your reply.
I have created a dummy variable, which is a drop-down list of with process names and restricted the access to the values using ACL based on roles, effectively restricting access to processes not relevant to an agent. That way, agents theoretically have access to all processes and can handle tickets from other processes, yet cannot start processes not relevant to them.
A workaround, until processes are clearly defined.
I have created a dummy variable, which is a drop-down list of with process names and restricted the access to the values using ACL based on roles, effectively restricting access to processes not relevant to an agent. That way, agents theoretically have access to all processes and can handle tickets from other processes, yet cannot start processes not relevant to them.
A workaround, until processes are clearly defined.
OTRS 3.3.x (private/testing) on Windows Server 2008 with MSSQL database.
OTRS 3.3.x (private/testing) on CentOS with MySQL database and apache
OTRS 3.3.x (private/testing) on CentOS with MySQL database and apache