[SOLVED] Process behaving different when transition is triggered by postmaster filter

[nedmaj]

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?

[nedmaj]

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!

[RStraub]

That's weird. I would have expcted that "activating" a changed process should take care of all caching...

[nedmaj]

I would have expected that too. But that was not the case. Maybe some bug worth reporting?

[jojo]

I would have expected that too. But that was not the case. Maybe some bug worth reporting?

yes, please