We do not update EasyMorph that frequently because it impacts several users.
It is not so easy to assess the impact of breaking changes when there have been several releases since our current version.
Is it possible to make a central table of breaking changes (not in the PDFs) and indicate if the breaking change requires manual intervention ? Is it possible to always provide a morph project for each breaking change so that we can easily find all impacted morph files ?
I have noticed that the concatenate action replaced the aggregate action with concatenate option. Does this have impact on existing flows ? I have noticed that in 1 morph file the action was disabled but after upgrade, the action is enabled.
In the morph file (XML, it says it is disabled). So that’s weird.