Upgrade to OTRS 4 Processes, Generic Agents, ACL etc

[aph]

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

[reneeb]

http://otrs.github.io/doc/manual/develo ... ng-33-to-4

[aph]

Thanks reneeb. That certainly answers a part of my question about custom modules, widgets

[aph]

What about Generic Agents and ACLs, are they migrated to the new version or do they have to be created afresh?

[RStraub]

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.

[aph]

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