Altova MapForce 2023 Enterprise Edition

Version 2019 Release 3


Major parts of the graphical user interface are now optimized for monitors with high pixel density (HiDPI)

Support for Database Tracing and Error Logging

Better support for database transaction handling in generated program code and server execution. If an error occurs when a mapping updates a database, it is possible to continue the mapping execution even if some operations failed, see Handling Database Exceptions.

Web service enhancements, including the following:

oAbility to map the HTTP status code returned by the Web service (applicable for RESTful Web services)

oAbility to supply the username, password, and URL of the Web service from the mapping (applies both to WSDL-style and RESTful Web services), see Web Service Call Settings

oAbility to create the raw body (MIME entity) of the Web service from the mapping, or map the raw body returned by the Web service call, with the help of new mime functions. Applicable for RESTful Web services.

oAbility to handle the Web service response conditionally, depending on the HTTP status code and content type (for RESTful Web services), see Handling the HTTP Response Conditionally.

A mapping can encode or decode Base64 data with the help of the new charset-encode and charset-decode functions.

Support for UN/EDIFACT D.18B Directory, see EDI.

New database versions are supported: PostgreSQL 11, Db2 for i 7.2 and 7.3

Support for Eclipse 4.7 - 4.10, see MapForce Plug-in for Eclipse

Support for explicitly setting the Java Virtual Machine path from MapForce, see Java Settings

Internal updates and optimizations


Version 2019


MapForce (and MapForce Server) can now map data to or from binary files in Protocol Buffers format, see Protocol Buffers.

New database versions are supported: Firebird 3.0, Informix 12.10, MariaDB 10.2, MySQL 8.0, PostgreSQL 10, SQL Server 2017, SQL Server for Linux (adds to support for previous versions)

You can selectively apply a default value or node function to specific nodes that meet your custom-defined criteria. For example, you can apply a node function only to nodes of specific type whose name matches a regular expression, see Applying Node Functions and Defaults Conditionally.

When creating node functions, you can process data conditionally based on metadata such as node name or node annotation, see Supplying Node Metadata to Node Functions.

Mappings that contain grouping functions run much faster in generated C#, C++, or Java code

Internal updates and optimizations


© 2017-2023 Altova GmbH