migFx – New Release 2018.1
Our great solution for complex data migration continues to get even better with this latest release.
Naming and branding
The release includes new features and a complete rebranding of all four components.
- The mapping application is now called Studio
- The code generator is named Engine
- The execution framework we call Director and
- The tracking portal has bee named Tracker
Together the combined suite is named migFx – our solution for complex data migration.
This latest release includes new features like:
Bags are like rules on steroids. While rules certainly can solve anything you may encounter, it may sometimes be a bit cumbersome due to the fact that rules cannot hold state. Enter Bags – within the processing of a root Business Object bags can hold state. The state is reset at the beginning of each root Business Object. The bag can have as many methods you want and these methods can be called everywhere you can call rules. The methods can store and use state and – even better – state can be exposed to be accessible as a new Value Type Bag Property to be used directly in the mapping.
- Transform Map is gone
The previous, intermediate Transform Map layered between the Source- and Target Maps is out and the Source- and Target Maps are now directly linked. This has led to considerable simplifications – both conceptual and especially in the infrastructure of a migration project. Best of all this is achieved without any loss of functionality.
- Improved Studio Usability
We have lifted the Studio UI to a new level of usability. The changes are indeed many across the whole spectrum from small and nice to big and significant. These changes deserve to be highlighted
- New Value Assignment dialogs make efficient use of screen real estate leading to improved overview and less scrolling
- Open items on the Studio document canvas can now be undocked and placed on your desktop outside the main Studio window allowing you to simultaneously see and work on several items in their entirety. A relay nice thing if you have a large and/or multiple monitors available
- Validation- and Cross Reference lists have been improved to include more valuable information to assist your issue tracing even more. And – best of all – both lists can now be exported to Excel for further processing
- New features in Source Map
We are sure you will like a couple of new features in the Source Map
- Valuesets have always been very versatile. Now we have added the possibility to use Valuesets as Source Objects – just as you today use Source Metadata and Source Views. Especially Translation Valuesets are candidates as Source Objects to build the Translation directly into the Source Map and make it visible in the Source Xml for each Business Object
- Source Views are now recursive, so you can use a Source View from another Source View. The Studio validation will find any circular references and the Director will resolve the View dependencies for you
The additional features make migFx an even better solution for complex data migrations.
With our ambitious roadmap for migFx will continue to evolve based on our users’ input and the challenges we are faced with in real-life data migrations projects.
With the 2018.1 Release, we have completed the rebranding of our Solution (now called migFx) so it consists of four software components called Studio, Engine, Director, and Tracker each with its own logo and identity.
Like to know more about this latest release or migFx in general? Just contact firstname.lastname@example.org.