Hi guys,
I got a problem with a process behaving differently when transition is triggered by postmaster filter.
I've got an activity with three transitions. Each one moves (transition action) the ticket to a specific queue. Both transitions are triggered by ticket approval and depending on some other field value the ticket is moved to a certain queue.
I can approval the ticket using the Decision option using agent interface and all the transitions are working just fine.
But the ticket could also be approved by mail, so I've configured a postmaster filter for that. When the approval message is processed the ticket is aproved. But for some reason I can't explain a differente transition is being triggered, although the values are the same.
After several tests my conclusion is OTRS process management engine behaves differently when invoked by PostMaster. But I don't know why this happen neither how to fix it.
Any ideas?
[SOLVED] Process behaving different when transition is triggered by postmaster filter
Moderator: crythias
-
- Znuny expert
- Posts: 167
- Joined: 26 Nov 2014, 20:34
- Znuny Version: 6.3.4
- Real Name: Samuel Casimiro
- Company: Câmara dos Deputados
- Contact:
[SOLVED] Process behaving different when transition is triggered by postmaster filter
You do not have the required permissions to view the files attached to this post.
Last edited by nedmaj on 26 May 2017, 20:43, edited 1 time in total.
Samuel
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
-
- Znuny expert
- Posts: 167
- Joined: 26 Nov 2014, 20:34
- Znuny Version: 6.3.4
- Real Name: Samuel Casimiro
- Company: Câmara dos Deputados
- Contact:
Re: Process behaving different when transition is triggered by postmaster filter
Hi guys,
I've just found out what was going on. Postmaster is handled by the Daemon, who creates a in memory copy of the process (maybe it does a copy of other definitions as well). So we need to restart Daemon everytime process definition is changed. That solved the problem.
Best regards!
I've just found out what was going on. Postmaster is handled by the Daemon, who creates a in memory copy of the process (maybe it does a copy of other definitions as well). So we need to restart Daemon everytime process definition is changed. That solved the problem.
Best regards!
Samuel
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: [SOLVED] Process behaving different when transition is triggered by postmaster filter
That's weird. I would have expcted that "activating" a changed process should take care of all caching...
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
-
- Znuny expert
- Posts: 167
- Joined: 26 Nov 2014, 20:34
- Znuny Version: 6.3.4
- Real Name: Samuel Casimiro
- Company: Câmara dos Deputados
- Contact:
Re: [SOLVED] Process behaving different when transition is triggered by postmaster filter
I would have expected that too. But that was not the case. Maybe some bug worth reporting?
Samuel
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
Znuny 6.3.4 | OTRS 5.0.17
OS: Debian 11 | CentOS 6.5
Database: Postgres | Oracle 12.1
Number of agents: 450 | Number of customers: 20000 | Number of CIs: 30000
Re: [SOLVED] Process behaving different when transition is triggered by postmaster filter
yes, pleasenedmaj wrote:I would have expected that too. But that was not the case. Maybe some bug worth reporting?
"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