When phasing out other ERP systems, we are in a hybrid situation where the singe point of truth is ensured in a view in Thinkwise. Sometimes our views contain so much business logic that we base any upgrade scripts on them. This sometimes causes some occasional problems with upgrades. If a view depends on a field change in the generated upgrade script, the view may break and the upgrade may fail on our manual upgrade script.
We would like to see a new code group 'after_deploy' or 'after_creation', which is executed only after all other generated objects have been deployed on the database. We can use the 'manual' code group, but it is only generated in case of a full upgrade, which we prefer not to do for performance reasons.
