Released: Apr 2, 2019

Updates in 2019 Release 3

Funktionen

• Full support for high resolution monitors - MapForce 2019r3 has had an extensive UI revamp to provide a beautiful, sharp display on today’s modern, high-PPI (pixel per inch) screens, including 4K, UHD, and Retina monitors. The redesigned MapForce UI takes full advantage of the higher resolution offered by high pixel density displays to render all graphics with more precision and detail, making complex data mapping projects more vivid and easier to read.
• Database output logging (tracing) - New support for database tracing makes it easy to log all the changes made by a data mapping project to the database when the mapping runs. When tracing is on, events such as database insert or update actions, or errors, are logged in an XML file that you can later analyze or process further in an automated way. Database tracing can be enabled at the database component, table, stored procedure, or database field level. You can choose to trace all messages or only errors, or you can disable tracing completely. Once you have selected the desired tracing level, the affected database component in the mapping project is extended with an XML tree showing the log structure. If you prefer the log file to be in a format other than XML, you can map data from it to some other data format supported by MapForce (for example, a text file or even another database). When clicking the Output button to preview the result of the mapping, the developer can also see an example of what the trace log will look like when the mapping is executed. This new functionality provides even more control for mapping designers working with databases to refine data processing definitions and/or report issues to stakeholders managing the source of the mapping data.
• Transaction roll-back for database error handling - In addition to tracing errors that occur during the execution of a mapping to a target database, MapForce now includes database transaction handling to roll back the affected part of the database data when an error is thrown and optionally proceed with the rest of the mapping. Sometimes an error occurs that doesn’t prevent the rest of a mapping from continuing, such as when certain database constraints prevent the mapping from inserting or updating invalid data. Enabling database transaction handling will enclose all changes done by the database component inside a transaction that will be rolled back in case of error, and you can opt to either proceed with rest of the mapping or stop further execution of the mapping. You can enable transactions at database component level and at table action level. This is very useful when the mapping designer wants to capture valid incoming data and simply ignore invalid data.
• New functions: charset-encode and charset-decode - Certain data mapping components such as Web services, database BLOBs, and so forth, send or receive data in binary format. These new functions allow that data to be processed as a string in a data mapping project, with charset-encode encoding string data as Base-64 text and charset-decode doing the opposite.
• Support for additional database versions - MapForce supports mapping data in any of the most popular databases, and in this release support is added for new versions of:
  • PostgreSQL 11
  • IBM DB2 for iSeries® 7.2, 7.3
• Updated OpenJDK support - In this release, Open JDK support has been updated to allow developers to manually point to an Open JDK installation on the computer if it cannot be found automatically.
• Support for Windows Server 2019.
• Support for Eclipse 4.9 and 4.10.