Jump to: navigation, search

Transfer Meta Data between Environments


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.


[edit]

Considerations

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.
  • 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: 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.
  • 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.

See also