I'm of planning an update from OTRS 3.3.8 to OTRS 4. I would like to know which of the settings do not survive an update.
Custom modules, widgets: I know that custom .dtl files will need to be 'transformed' to the .tt format. What about the custom .pm files and custom .xml files for dashboard widgets, themes etc. Are any changes required in these files because of an update? I'm using a custom .pm file for a dashboard widget which displays tickets in a particular state. Simillarly, I'm using a custom skin. Do I need to change the xml, pm and css files due to an update?
Processes: The process ID in otrs 4 are unique IDs. Are the old process ids converted to new IDs or do I have to create the processes all over again?
Generic Agents: This question is related to the previous one. Are all generic agents carried over during an update? I have generic agents that trigger a process on ticket create event. Are the values in Generic Agent ticket action part changed automatically (let's say from P2 to the unique id of the process?
ACLs: Are all ACLs carried over during an update or do I have to create them all over again?
I would appreciate any other input you might have on possible issues during migration
Upgrade to OTRS 4 Processes, Generic Agents, ACL etc
Moderator: crythias
Upgrade to OTRS 4 Processes, Generic Agents, ACL etc
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
-
- Znuny guru
- Posts: 5018
- Joined: 13 Mar 2011, 09:54
- Znuny Version: 6.0.x
- Real Name: Renée Bäcker
- Company: Perl-Services.de
- Contact:
Re: Upgrade to OTRS 4 Processes, Generic Agents, ACL etc
Perl / Znuny development: http://perl-services.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Free Znuny add ons from the community: http://opar.perl-services.de
Commercial add ons: http://feature-addons.de
Re: Upgrade to OTRS 4 Processes, Generic Agents, ACL etc
Thanks reneeb. That certainly answers a part of my question about custom modules, widgets
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: Upgrade to OTRS 4 Processes, Generic Agents, ACL etc
What about Generic Agents and ACLs, are they migrated to the new version or do they have to be created afresh?
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
-
- Znuny guru
- Posts: 2210
- Joined: 13 Mar 2014, 09:16
- Znuny Version: 6.0.14
- Real Name: Rolf Straub
Re: Upgrade to OTRS 4 Processes, Generic Agents, ACL etc
They are migrated.
From my experience what doesn't always work however is the rewrite of Process (and Activity) IDs.
So if you have an ACL or Generic Agent that uses hardcoded values of process IDs, you have to rewrite them after the upgrade.
From my experience what doesn't always work however is the rewrite of Process (and Activity) IDs.
So if you have an ACL or Generic Agent that uses hardcoded values of process IDs, you have to rewrite them after the upgrade.
Currently using: OTRS 6.0.14 -- MariaDB -- Ubuntu 16 LTS
Re: Upgrade to OTRS 4 Processes, Generic Agents, ACL etc
Thanks. I was sure about the process and activity id thing, but not with others. Now, I can better asses timeframe required for a migration
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