Stambia versions 2.x, 3.x, S17, S18, S19 and S20 are reaching End of Support January, 15th, 2024. Please consider upgrading to the supported Semarchy xDI versions. See Global Policy Support and the Semarchy Documentation.
The Stambia User Community is moving to Semarchy! All the applicable resources have already been moved or are currently being moved to their new location. Read more…
Mapping editor includes a utility called "Mapper" which helps to quickly define expressions in a special window where every source is listed for a given target.
All the objects can be accessed easily in this window and added in expression with a drag and drop or double click.
This article gives an overview of how to use it and the possibilities offered.
If you have accidentally deleted objects from the Project Explorer, you can try to restore them. You can rely on the versioning system functionalities you are using - such as GIT or SVN - but if you can't there is an other option :
When working on Projects, all the Metadata, Mappings, Processes and Templates might not be located at the same place.
Most of the time, users choose to structure developments in multiple projects, centralize all Metadata, etc.
This means that a Mapping, for instance, might depend on multiple Projects to work correctly.
The Designer offers the possibility, for a given item (Project, Folder, Mapping, ...) to list all its required dependencies, and the missing ones.
This can help users to find what is required, what is missing, and the potential place where it can be found.
Read more: Impact Analysis - displaying the required and missing dependencies for an item
The internal structure of Mappings evolves silently between the versions to support the new Mapping features, to improve its cache indexation, and to make it more efficient.
The Designer updates the model version of existing Mappings through different ways, which are explained in this article.
A package is an archive containing all the needed files and folders to generate a delivery.
Most of the time, a package is generated by the development team when they have finished working on a Mapping / Process.
The package can then be used to generate the delivery that will be executed by the Runtimes.
