There are some old tooling module’s files (transaction and xui) are created by old version of BTT tooling. There maybe some module changed impact for those old module files. If the new tooling module can not compatible the old module file, BTT tooling lab team can help to fix these module files manually to be compatible to new tooling.
For the “import” issue, take reference as below:
It is not necessary for customer to adjust the "import". If customer does some adjustments, they can get so much the better user experience, like locating the "imported files (under source folder other than bin folder) accurately", otherwise they have same experience as BTT v710 at least. For the locating mult-level "import" and nested "import", it was limitation in v710. We devoted much energy to overcome the limitation in v801 and we can say we support it no matter the v801 style import or v710 style currently.
For WS Wizard, not only common-services.xml but common-services.transaction file will be generated in BTTv801. In self-definedOp.transaction, the previous delivery (on 28th March) shows 'import file="common-service/abc.xml"'. In order to be consistent with other relative import, in the coming delivery (on 20th April) , it will change to 'import file="common-service/abc.transaction". BTTv801 is capable of downward compatibility for this point, no migration required.