Migrate Delivery of Framework Contracts to RTAs

Migration is enabled by the internalMode switch in the generator that triggers the transformation of framework-specific contracts to RTAs. This process ensures that all framework-specific contracts are packaged and deployed within the framework. Don’t maintain the contracts in Modeler. If a contract is created with the same name as a Framework contract, a warning is thrown in logs.

The Framework contracts are localized by using the Framework labels. These labels are a part of the installed Modeller Update Packages. If the Implementation Backend Environment isn’t updated, default labels are used. The values can be edited in the Framework section of the locale files. If the IBE and the locales are updated, and a new deployment is built, the localized values are used.

Examples for such contracts are PrintPreview, About, and PrinterSettings.

The internalMode switch asks the generator to build framework RTAs instead of application RTAs. It also modifies the name of the resulting rtas.json file to fwrtas.json. The fwrtas.json file consists of all the generated framework RTAs.

The existing ui.js and engine.js files are replaced by the newly created fwrtas.json file when the switch is set to native builds. After it’s created, the RTAs are saved in a folder that is a part of framework codebase and are maintained by Consumer Goods Cloud Mobile App Framework.