Service Studio 5.1 Help
Merge eSpaces
In a multi-developer environment, developers have different copies (versions) of the same eSpace (An application or a part of an application that implements a set of services, gathered in a single project. Each service can be presented in a different flow.). These are obtained through download, save as ..., clone or simply by duplicating the oml (Stands for: OutSystems Markup Language) file. In Service Studio, the Merge operation will allow them to integrate their work.
You can also use the merge operation to copy specific data and logic that is implemented in a different eSpace. The Merge operation will copy elements from one eSpace to another, creating them in the destination eSpace.
|
How to Merge eSpaces: |
|
|
|
|
|
|
|
If you want to use
another eSpace functionality without
copying it into your eSpace, consider adding it as an eSpace reference (Is an element exposed by a Producer eSpace or extension that, when
referenced by a Consumer eSpace, is called an eSpace reference in its
context. Once an eSpace reference, e.g. an action or entity, is added,
you can use it anywhere in the Consumer eSpace but you cannot change its
definition.).
See Also
Differences to Merge Window | Add an eSpace Reference | About Multilingual eSpaces