Difference between revisions of "HowTo:Transfer Meta Data between Environments"
| Line 8: | Line 8: | ||
Before transporting a data model, or meta data, between {{UBIK}} Environments, it is important to consider the following: | Before transporting a data model, or meta data, between {{UBIK}} Environments, it is important to consider the following: | ||
* Transporting meta data using SmartStudio is best done in {{UBIK}} 4 and newer, to avoid problems with the Sandbox/Live mode. | * Transporting meta data using SmartStudio is best done in {{UBIK}} 4 and newer, to avoid problems with the Sandbox/Live mode. | ||
| − | * If you don't just transport only once, but continue developing and want to transfer your changes incrementally, you need a development strategy. | + | * If you don't just transport only once, but continue developing and want to transfer your changes incrementally, you need a development strategy. See also: [[HowTo:Organize_UBIK_Development]]. |
* While SmartStudio is capable of merging two different situations, it cannot work out the differences between two situations (at least not in version 4). {{UBIK}} also is no version control system (VCS) like Git or SVN and does not support several development branches inherently. | * While SmartStudio is capable of merging two different situations, it cannot work out the differences between two situations (at least not in version 4). {{UBIK}} also is no version control system (VCS) like Git or SVN and does not support several development branches inherently. | ||
* It is recommended to use a VCS like Git to develop new features for your customizing, and to use SmartStudio projects to transport them between staging environments. | * It is recommended to use a VCS like Git to develop new features for your customizing, and to use SmartStudio projects to transport them between staging environments. | ||
= Development strategy = | = Development strategy = | ||
| + | See also: [[HowTo:Organize_UBIK_Development]]. | ||
In any case, a project management or issue tracking system is recommended to organize your project. Further, staging is a best practice for QA. To manage your customizing optimally for collaboration and staging, a version control system (VCS) like Git is strongly recommended. The transport of meta data between staging environments can be done with SmartStudio. | In any case, a project management or issue tracking system is recommended to organize your project. Further, staging is a best practice for QA. To manage your customizing optimally for collaboration and staging, a version control system (VCS) like Git is strongly recommended. The transport of meta data between staging environments can be done with SmartStudio. | ||
| Line 32: | Line 33: | ||
==See also== | ==See also== | ||
<!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --> | <!-- DO NOT MODIFY THE NAME OF THIS SECTION, BUT REMOVE IT IF NOT REQUIRED --> | ||
| + | * [[HowTo:Organize_UBIK_Development]] | ||
* [[Smart_Studio]] | * [[Smart_Studio]] | ||
* [[HowTo:Import_Meta_Data_from_Comos]] | * [[HowTo:Import_Meta_Data_from_Comos]] | ||
Latest revision as of 21:46, 24 July 2023
Using Smart Studio, meta data from one UBIK® Environment can be transported into another one. This includes Meta Classes and their Meta Properties, Meta Proxies, Selective Lists and Units.
This is useful when a staging strategy is applied in a project, where every feature is quality assured by first being implemented in a Development (DEV) Environment then integrated with other systems in the Integration (INT) Environment and finally, after testing and acceptance, released to the Productive (PROD) Environment.
